| I have a user that can no longer connect to one of my 4 DC. He is also
| unable to browse the network via Network Places.
|
|
| Please Help
|
Account locked out? Is he attempting to authenticate on the domain or
locally? What does ipconfig /all say? Otherwise: DNS resolution is
critical on any W2K network. And the word *critical* is an
understatement.
Ask the user if he can ping the DC by name. Then ask the user to ping
the DC by ip_address. If ping_by_name fails but ping_by_ip succeeds,
then do one of the following:
a) configure the dhcp server with the appropriate dns server option(if
dhcp is involved). Verify result with ipconfig /renew and ipconfig /all
on client.
b) add ip - dc's name combo to user's hosts file(if static ip) and
configure the client to use the required dns server.
Needless to say, the dns server needs to be routable from the client.
If ping by ip_address fails, you need to correct the network's physical
routing. That is, is the client on a different subnet and is a router
available with the appropriate route to steer the traffic through?
Default Gateways may be relevent here.
If the client can't ping the dns server or if it isn't configured to use
the dns server, and no mechanism is provided to resolve the dc, failure
is guarenteed. WINS is not an option.
