Can't Ping or RDP My Computer Anymore

Clarifications

It was probably caused by the new remote desktop update microsoft released.You probably have to reconfigure

I am assuming this is your home PC and most home networking equipment can do odd things. So rebbot everything and see what happens. If Remote Desktop is still enabled (right click on My computer, Properties, Remote tab) and it isn't working go to a command prompt and type "netstat -a -n" and you wil find TCP 0.0.0.0:3389 and it should be listening. TCP 3389 is the port used by Terminal Services. If you don't see this than go to Start then Run and type "services.msc" and click OK. Find the service "Terminal Services" and make sure it is Started and not set to Disabled. If it is not started and it is set to manual you may want to set the service to start automatically. Make sure you check your Windows Firewall as well as you Router Firewall to make sure that 3389 is forwarded/open.

No, I'm on the same network segment. Even when I used to connect from "outside", I was on this segment via a Cisco VPN.

The only "firewall" that's involved here is the Windows firewall on my computer, and it's passing the listening port.

Tracert doesn't go anywhere; I get asterisks right down the line. A tracert to any other address on this segment gets there on the first hop.

Are we running out of options or what?

Computers add so much productivity, yet so much irritation.

I can't rember if you said so, but you can ping the router, other PCs, internet sites, etc, correct? Have you tried a different port on the switch? Or maybe booting into safe mode and uninstalling your NIC driver and let it re-detect it on next boot.

This totally sounds like the firewall is blocking traffic. You stated that the firewall settings looked good, but, do you have another firewall? Maybe symantec Internet Security installed?
to make the computer 'invisable' means that something is either blocking the traffic, there is a physical connetion problem, or the system is not getting an IP address.

I am in the same boat. Perhaps worse.

I've checked my ARP tables and yes it resolves the address from machines pinging my computer on the local network.

No it will not respond to pings.

No I don't have the firewall running - it is disabled.

DHCP is off

There is no firewall between the computers

If I use TCPDUMP from the mac on the network you can see it asking, but this machine never responds.

If I use WireShark on this computer - as far as it is concerned nothing is asking it anything.

I *CAN* use ssh to open a remote shell on the mac from this computer proving that it can indeed talk to the mac, but only in certain ways. It can RDP my win2K machine just fine too.

Nothing on my network can hit the IIS running on this machine anymore.

I've run rootkit revealers, spyware checkers (spybot S&D), virus checkers (AVG always is running).

I've replaced the drivers on my NIC.

I am thoroughly stumped.

As far as I can tell, this is all a windows fault buried inside a core DLL.

As far as I know there is no way to sniff the traffic to the NIC without going through windows.

I tried re-running SP2 with no luck.

At this point I am likely to install a new OS and be done with it. I spent many many hours on this.

QUESTION: what does netstat -a -b say if you run it from a command shell? Mine basically tells me that it is listening for port 80 traffic...to itself and no-one else. I think this is significant although I certainly never told my PC to stop being able to host to other computers. As a developer I *NEED* others to be able to hit this IIS as a test bed. I suspect this is a side-effect of something MS did recently.

I am going to check my windows update history and see if there is anything relevant.

what a pita.

Make sure the router is working fine and the firewalls are open for remote connection the Ethernet cable is plugged into your network adapter (wired networks only), your computer?s wireless switch is turned on (mobile computers on wireless networks only), and your network adapter is working. I assume you are logging on as or using an account in the 'Administrators' group?
Again if you?re trying connect via VPN, can you ping your work PC? Has your company configured VPN at their end to only allow certain applications/ports? Are you running a firewall on your work PC?
Did you recently updated one of the computers, I suggest if nothing works Update both computers and do a system restore for a previous date when things were working. And before that reset the router at your remote destination.

I have the same issue after I installed Windows XP update. I don't really have a fix but i noticed that my problem goes a way if I fire up my VPN (Cisco) client. After I have established a vpn connection for MY PC, I am then able to ping my pc, and also use RDP and VNC. I am able to connect even after I have shutdown my VPN until the next time I re-boot.

I'm tempted to uninstall and reinstall my VPN but then I'm not sure if it will ever work. I'll try it anpther dat when I have more time.

Well, it solved itself when my hard drive crashed and I had to reload everything from scratch. Guess I'll never know...

Open of the Cisco VPN Client connect to the network via VPN and then right click the icon and deslect the stateful firewall always on ICON. Then you can ping while connected via VPN or not connected VPN.

For some reason the Firewall stays on even when the cisco client is not open.

-Tom

.