This isn't a big deal to me. It doesn't affect my job, I'm just curious. 🙂
At some point during the night, one of my co-workers machines cut itself off from the network. His shared drives were gone, he couldn't ping the other workstations, etc. He rebooted, but the problem still exists.
I can't uninstall TCP/IP or the network adapter (no permissions). Here's what I think the wierd part is: The machine cannot ping its non-localhost address. If the IP was 244.244.244.9, the machine cannot ping 244.244.244.9. It can ping localhost just fine though.
It's a win2k machine, no software firewall.
Anyone have any ideas? Hopefully it will be fixed by the time I get back into work tonight, just curious as to what types of things would cause the machine to not be able to ping its own ip address. 🙂
At some point during the night, one of my co-workers machines cut itself off from the network. His shared drives were gone, he couldn't ping the other workstations, etc. He rebooted, but the problem still exists.
I can't uninstall TCP/IP or the network adapter (no permissions). Here's what I think the wierd part is: The machine cannot ping its non-localhost address. If the IP was 244.244.244.9, the machine cannot ping 244.244.244.9. It can ping localhost just fine though.
It's a win2k machine, no software firewall.
Anyone have any ideas? Hopefully it will be fixed by the time I get back into work tonight, just curious as to what types of things would cause the machine to not be able to ping its own ip address. 🙂
