Our network consists of two Win2k DCs, and two Win2k8 DCs were added a few months ago, which will eventually replace the Win2k DCs. All server are in the subnet 172.20.4.X, and all of the client that receive an IP through DHCP are in the subnet 172.20.5.X. We have been experiencing an issue recently where two different Win7 Pro clients have been added to the domain, they can connect to every other host and client on the domain, but one Win2k DC that is also a file server is unreachable. The clients cannot ping the server or access the network shares on the server, and the server cannot ping the clients. If I give the clients a static IP address in the same subnet as the unreachable host, 172.20.4.X, the connectivity issues cease. Any thoughts on what the root of the issue is? In the meantime I am going to try a WinXP Pro client to see if the same issue occurs. Thanks.
-
-
Very interesting issue, so replying to be subscribed.
If you can set the IP to be on the other subnet and ping the systems, that's a very interesting network configuration.
I'm going to throw it over to the Windows Forum to see if there are any compatibility issues you might need to take into account, and if not the Moderator of the Windows forum will kick it back over to me to check out the configuration of the routers, subnets, servers, etc...
Windows guys - any compatibility issues between Win7 and Windows 2000 servers? -
I have confirmed that the issue does not exist with a WinXP Pro client configured with DHCP. It is also worth noting that the Win7 Pro clients that are experiencing this issue are able to ping and access network shares on other Win2K hosts.Comment
-
After removing the Win2K domain controllers with the DCPROMO command, we are no longer experiencing the original issue.Comment
Comment