The only "extra" stuff I have that is in this category is the Cisco VPN client, System Mechanic 8, Advanced System Care, CCleaner, and I did have the software below on at one time but it has been since removed gracefully. VMware Server 2.0, Zone Alarms.
Another strange thing is the default NIC which was an onboard GB nforce adapter just lost it's driver and will not take a new one. I had to install a 3Com NIC I had laying around. It does indeed have the latest drivers. I am familiar with telneting to specific ports and I can tell you that I can't even get to the web management of my wireless access point or other things that use standard HTTP ports like my website that I host internally (on the same LAN). That helped me determine it was just my machine and only HTTP because I can FTP at any time, SSH, etc without any issue.
As for the event viewer, I haven't seen a single mention of anything related or note worthy but I have to admit I check things before I reply and I just found something interesting. The following was logged right when I just lost connectivity and posted after a reboot.
Information 2/21/2009 1:33:23 PM Service Control Manager Eventlog Provider 7036 None
The WinHTTP Web Proxy Auto-Discovery Service service entered the running state.
That looks RIGHT in line with the issue of when it kicked in. It's a manual start service which I just set to disabled. I wonder if that will help me. I could hypothosize that the service things it finds a proxy server and changes my settings dynamically to use it which is what causes the failure. I am going to keep an eye on this for a few days and if this is the reason then I'll give you the points for helping me look around again. :)
Main Topics
Browse All Topics





by: cantorisPosted on 2009-02-21 at 13:49:26ID: 23702011
That's freaky.
com/tools/ autoruns.e xe)? See if that makes the problem go away.
Do you have any third-party networking-related software installed?
Any extra firewall or antivirus software?
If you look at the Network Interface properties, are there any unusual entries in there?
Is there an update for your network card driver?
When it goes wrong, can you telnet to port 80 of a webserver address (you'll have to install the Telnet Client Windows Feature)?
Is the machine fully patched with Microsoft Update?
Any clues in the Event Logs?
If this problem occurs frequently, have you tried disabling as much non-essential stuff from starting up on boot as possible using msconfig or Autoruns (http://live.sysinternals.