Whenever I scan for proxies on my computer, I can't connect to things, go on the web, etc. Even after I turn the scanner off. I have to restart my computer for it to be back to normal.
Would anyone know why this is doing this? I scanned on my other computer and it didn't do those things. So I'm assuming it's my computer. It isn't my bandwidth because I have 1.5mb/s bandwidth.
Anyone got any suggestions?
Quote from: inner. on December 30, 2005, 07:50 PM
Whenever I scan for proxies on my computer, I can't connect to things, go on the web, etc. Even after I turn the scanner off. I have to restart my computer for it to be back to normal.
Would anyone know why this is doing this? I scanned on my other computer and it didn't do those things. So I'm assuming it's my computer. It isn't my bandwidth because I have 1.5mb/s bandwidth.
Anyone got any suggestions?
Is your other computer that you tested this on connected to the same network?
What operating system do you use on each computer?
What scanner are you using?
You really haven't given enough information to get a precise answer to your question.
Quote from: Rule on December 30, 2005, 08:39 PM
Quote from: inner. on December 30, 2005, 07:50 PM
Whenever I scan for proxies on my computer, I can't connect to things, go on the web, etc. Even after I turn the scanner off. I have to restart my computer for it to be back to normal.
Would anyone know why this is doing this? I scanned on my other computer and it didn't do those things. So I'm assuming it's my computer. It isn't my bandwidth because I have 1.5mb/s bandwidth.
Anyone got any suggestions?
Is your other computer that you tested this on connected to the same network?
What operating system do you use on each computer?
What scanner are you using?
You really haven't given enough information to get a precise answer to your question.
Yes, my other computer was on the same network.
On my current computer it's Windows XP Professional. On my other computer it's Windows XP Home.
I'm using TLS (Tiny Little Scanner)
I hope this clears things up.
When you scan on your other computer (where your problem doesn't happen) can you use the Internet normally, while the scanner is running?
On the computer that is causing you problems, run the scan, then stop it, then go to command prompt, and type
netstat -a
The output may give you the answer to your problem.
I remember there was this certain scanner I was using, and it caused the same problem for me. However using a different scanner did not cause any problem at all.
Oh? What scanner?
I wouldn't remember, this was years ago.
Eh, ok. I think I'm just going to stop scanning, this is pissing me off. :p
With SP2, raw sockets are unsupported, hence disabled.
Quote from: Explicit[nK] on January 01, 2006, 04:44 AM
With SP2, raw sockets are unsupported, hence disabled.
Did anyone mention raw sockets?
They're used
very infrequently. Developers need to implement their own network stack to use them. So I doubt that this is the issue.
Quote from: MyndFyre on January 01, 2006, 02:33 PMQuote from: Explicit[nK] on January 01, 2006, 04:44 AMWith SP2, raw sockets are unsupported, hence disabled.
Did anyone mention raw sockets?
They're used very infrequently. Developers need to implement their own network stack to use them. So I doubt that this is the issue.
Raw sockets (http://en.wikipedia.org/wiki/Raw_socket) are the preferred way of doing port scans. Nmap (http://www.insecure.org/nmap/) works
much better if it has permission to open a raw socket, since it can do all sorts of unusual constructs if it writes its own datagrams.
Removing raw sockets in SP2 was a nice gesture, but it came a couple of service packs too late. If they were going to do it, they should've never shipped raw socket support as part of a Windows desktop OS in the first place. Only network cartographers (typically, developers and sysadmins) and malicious software (i.e. programs to send LAND and similar such malformed constructs) need raw socket support. The cartographers would be easily qualified to get a raw socket implementation for Windows if they didn't already have a Unix system from which to send the desired packets. The malicious software can drag along its own network drivers for the purpose, but that makes it larger and more invasive than if it can get the raw socket support direct from the OS.