TheLumberingAdmin
IS-IT--Management
I've been having an issue with a single Win2K client that is unable to browse the network, cannot be browsed from another client or server (computer shows up in network neighborhood, but cannot be accessed), and cannot even be pinged from any other computer on the network (using ip or hostname). It can, however, Log into the domain, ping any other computer on the network, access the internet throught our gateway, and access resources on other computers using the UNC (e.g. \\hostname\sharedfolder) for whatever computer/folder it is, though no computer can access the client in that manner. Its like, as far as the rest of the network is concerned, this computer doesn't exist.
I thought this may have been caused by the client attempting to become a master browser (which, looking at the server's logs, it attempted to do so), but even after the registry edit to keep the client from maintaining a server list, the problems persist.
I've reinstalled all network protocols, removed the machine from the domain and re-registered it, swapped in three different NICs and a two different cables, just in case. The machine is on the same subnet as the rest of the network, all machines have static IPs. The system logs of the client have random interval warnings of the Windows time Service being unable to find a Domain Controller, but nothing else out of the ordinary.
The box in question is running Win2k Pro SP4, all upgrades current. NIC is (now) a NetGear FA311 (was 3Com 905TX. Server running Win2k Server SP4, all updates current as well. We've got a recently installed (last week) SMC-EZ6516TX Switch, and a 3Com OfficeConnect Dual Speed Hub in between the server and this client. Previous to this it was two of the 3Com hubs in line. There are several other clients hooked up, with the same hardware configuration as this one, some running Win2k Pro, some running Win98. This is the only box with a problem.
Any ideas with this one?
I thought this may have been caused by the client attempting to become a master browser (which, looking at the server's logs, it attempted to do so), but even after the registry edit to keep the client from maintaining a server list, the problems persist.
I've reinstalled all network protocols, removed the machine from the domain and re-registered it, swapped in three different NICs and a two different cables, just in case. The machine is on the same subnet as the rest of the network, all machines have static IPs. The system logs of the client have random interval warnings of the Windows time Service being unable to find a Domain Controller, but nothing else out of the ordinary.
The box in question is running Win2k Pro SP4, all upgrades current. NIC is (now) a NetGear FA311 (was 3Com 905TX. Server running Win2k Server SP4, all updates current as well. We've got a recently installed (last week) SMC-EZ6516TX Switch, and a 3Com OfficeConnect Dual Speed Hub in between the server and this client. Previous to this it was two of the 3Com hubs in line. There are several other clients hooked up, with the same hardware configuration as this one, some running Win2k Pro, some running Win98. This is the only box with a problem.
Any ideas with this one?