• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows XP unresponsive to incoming network connections

I

irha

Junior Member
I am totally stumped by this issue and didn't get any help elsewhere, so hoping I would find more luck here.

I have two desktops running Windows XP and both started being totally unresponsive to the incoming network connections lately and I can't figure out what went wrong. I can't connect to any of the services that I was able to connect before (terminal server, cygwin sshd etc.), even though they are running and are accessible from with in the same computer. I can't ping by name (which used to work before) or even by IP address. I tried both from my other PC and laptop as well as from the router's ssh console itself (I use tomato firmware).

I updated both to sp3 and to the latest version of zonealarm and that is the only thing that I have done that is common to both, so I naturally suspected them at first. However, I can't point my finger at either. Here is how I diagnosed so far:
- Made sure windows firewall is not enabled (in fact the service is disabled and even trying to start the corresponding control panel app brings up the dialog that the service is not running and if I want to start it).
- In zonealarm, verified that my LAN is configured to be in trusted zone and that the security for trusted zone is switched off.
- Did a clean uninstall of zonealarm following this link and didn't find any improvement, so at this point, I am not suspecting zonealarm (or I would post this question in their forums).
- Rebooted in safe mode with networking support, still no response to ping or telnet on a

I don't know what else to do or where else to look for further diagnosis. I would appreciate any help.
 
If you suspect the firewall, often the best way to rule that out or in is by using the startup tab of Msconfig to take it off your startup list, reboot, and see if your problem goes away. Not being connected to the internet at the time helps on the safety aspects, and depending on the firewall and its log files, you can get information short of that.

And if you ever had but no longer use symantec, norton, or Mcafee software, you needs special removal tools to get rid of them.
 
Originally posted by: snikt
Seems like a name resolution problem. Are you using DHCP or static IPs?
Click to expand...

thats what i was thinking as well. i accidentally uninstalled "Client for Microsoft Networks" from my protocols list when messing around one time on an old laptop and had similar results. it didnt take me long to figure out tho, there was a similar response when you deleted the NetBIOS protocol back in the 98SE days.

also, are these direct connected? over a router? hardware firewall that could be blocking them?
 
Originally posted by: snikt
Seems like a name resolution problem. Are you using DHCP or static IPs?
Click to expand...
I am using DHCP on the desktop but fix them by means of using static DHCP on the router options. However, the problem is not specific to resolving the name, using the IP doesn't help either. I mentioned name resolution just as another thing that was working before but is broken now.
 
Originally posted by: hanoverphist
Originally posted by: snikt
Seems like a name resolution problem. Are you using DHCP or static IPs?
Click to expand...

thats what i was thinking as well. i accidentally uninstalled "Client for Microsoft Networks" from my protocols list when messing around one time on an old laptop and had similar results. it didnt take me long to figure out tho, there was a similar response when you deleted the NetBIOS protocol back in the 98SE days.

also, are these direct connected? over a router? hardware firewall that could be blocking them?
Click to expand...

These are connected through a router. I tried pinging and telnetting by logging into the router so i doubt if there is a firewall issue on the router itself. I haven't changed the router's firewall settings for quite some time now.
 
Originally posted by: Lemon law
If you suspect the firewall, often the best way to rule that out or in is by using the startup tab of Msconfig to take it off your startup list, reboot, and see if your problem goes away. Not being connected to the internet at the time helps on the safety aspects, and depending on the firewall and its log files, you can get information short of that.

And if you ever had but no longer use symantec, norton, or Mcafee software, you needs special removal tools to get rid of them.
Click to expand...

I have the service itself disabled so when I start msconfig, this service doesn't even show up. Also, I am still using zonealarm, however when I did the experiments, I uninstalled it following special instructions to remove all its remnants from the disk and registry.
 
Try reseting you network to out of box condition by uninstalling network drivers in device manager, reset router using reset button and Tomato using its web interface while disconnected to network. Then with all devices powered off reconnect your modem and wait for drive diagnostics to finish. Then power on router and wait for its diagnostics to finish then power on computer and reinstall network drivers. If you have any special settings for Tomato you can the put them back in.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top