Windows 2000 probs

  • Thread starter Thread starter Jesus
  • Start date Start date
J

Jesus

Hello, I'. having a very strange problem I have a W2k
Domain, my DC is windows 2000 server, I have all sorts of
clients, 95,98, XP & 2000, all my clients log on just
fine, but my 2000 clients take about 15 minutes to log in,
why is this hapenning, this is a bvery hot issue, could
some one please help, I would really apreciate it, thanks.



Jesus.
 
Jesus said:
Hello, I'. having a very strange problem I have a W2k
Domain, my DC is windows 2000 server, I have all sorts of
clients, 95,98, XP & 2000, all my clients log on just
fine, but my 2000 clients take about 15 minutes to log in,
why is this hapenning, this is a bvery hot issue, could
some one please help, I would really apreciate it, thanks.

First, check If your windows 2000 stations have proper DNS server
configured in TCP/IP properties - for Win 9x/NT 4.0 workstation this is
not an issue becouse hey are using different way to locate DC's but for
windows 2000 and later misconfigured or broken DNS server is a common
issue when it coms to the slow logon problems. The DNS server should be
configured to point to one f Your DC's.

In my network we have also some specific issue with network connection
speed - when network connection speed is set to Auto in NIC' properties,
and this NIC will not negotiate proper parameters with switch it is
visible for the users in very slow (few minutes) processing of startup
and logon scripts. When I set NIC speed to the fixed value it is working
correct. But this ca be an specific issue in my network with this
network equipment.
 
Jesus said:
Hello, I'. having a very strange problem I have a W2k
Domain, my DC is windows 2000 server, I have all sorts of
clients, 95,98, XP & 2000, all my clients log on just
fine, but my 2000 clients take about 15 minutes to log in,
why is this hapenning, this is a bvery hot issue, could
some one please help, I would really apreciate it, thanks.



Jesus.

If you are 100% sure your DNS settings are OK, try setting your network
cards on the clients to half duplex, if that doesn't work, 10mbps, etc.

The only time I had that problem I fixed it by doing that.. (cards were
getting loads of packet loss all the time so when Windows tried to
locate the D.C it just took forever...)
 
In addition to the other suggestions, have you looked at the event logs on
the workstations and the server?
 
Chris,

I am not sure that this would have any bearing on his problem. You are on
the right track, though. This is most probably a simple DNS issue in that I
would suspect that DHCP is not giving out any internal WIN2000 DNS Server IP
Address. This is not an issue with the legacy clients as they most probably
use WINS to locate services that the WIN2000+ clients need from DNS.

Many many many WINNT 4.0 admins have this problem when they come over to
WIN2000.

Cary
 
Back
Top