Slow access from subnets

  • Thread starter Thread starter Mike Morgan
  • Start date Start date
M

Mike Morgan

We are currently migrating from and NT4 domain to a Win2k Domain. I have
setup the new network as a separate domain with a trust relationship to the
old one. The new domain currently has a single DC with DNS and DHCP on it.
For the most part everything works fine. However, when I attempt to access
the new domain from a subnet other than the one the new DC is sitting on,
something strange happens. It will authenticate the user, but the logon
takes forever. Even when the machine comes up, its so slow that its
unusable. If I change the IP on the workstation back to one on the same
subnet with the DC, it logs into the domain and operates fine. I can ping,
tracert, and nslookup from separate subnets without any problem both by name
and IP (ie 10.25.4.0 can ping, tracert, and nslookup anything in 10.25.1.0
and vice versa). I can access anything on the workstation from the server
regardless of the IP it uses. I have checked DNS backwards and forwards and
it seems to be operating ok. DHCP will issue an IP (with all the trimmings)
from any of the available subnets without a problem. I'm stumped. What is it
that the new domain doesn't like about the other subnets?
 
In further experimentation, I have found that the problem only occurs if you
login or attempt to login to the domain. If you login to a workstation
locally, you can access everything in both domains. You just have to provide
a valid username and password when you attempt to access a resource and it
works fine. However, if you try to login to a domain, the workstation slows
to a crawl.
 
No, WINS is not installed on this particular server. The old domain uses
WINS. I've setup DNS (in the new domain) with a forward and reverse WINS
lookup using the servers in the old domain. I thought that this might be the
root of the problem so I took the WINS configuration out of DNS, but there
was no joy. The problem persisted. So, I've put it back in so that we'll
have name resolution between the two networks while we migrate.
 
Back
Top