Event ID 1053

  • Thread starter Thread starter Robert Smith jr.
  • Start date Start date
R

Robert Smith jr.

Hi,

I am seeing a very strange issue with our AD. All of our computers are
connected directly to the internet (class B address range). When a client
(XP) is on one of our local network segments, logging in to the Windows 2000
AD works great. If the machine is then moved to a different network
(dedicated DSL line for example), the Domain Controllers cannot be found.
Nslookup and all other DNS resolution appears to work, but event ID 1053
errors occur in the event log. If the network wire is pulled, the
connection times out in a few seconds and continues the login process.
Otherwise it can be up to 15 minutes before the machine continues.

This is really baffling. In one of the KB articles, it said something
abount doing an nslookup on
guid._msdcs.<root of domain>. This lookup does not work correctly no matter
where I try it.

Any help would be greatly appreciated!

Thanks,

Bob
 
In
Robert Smith jr. said:
Hi,

I am seeing a very strange issue with our AD. All of our
computers are connected directly to the internet (class B
address range). When a client (XP) is on one of our
local network segments, logging in to the Windows 2000 AD
works great. If the machine is then moved to a different
network (dedicated DSL line for example), the Domain
Controllers cannot be found. Nslookup and all other DNS
resolution appears to work, but event ID 1053 errors
occur in the event log. If the network wire is pulled,
the connection times out in a few seconds and continues
the login process. Otherwise it can be up to 15 minutes
before the machine continues.

This is really baffling. In one of the KB articles, it
said something abount doing an nslookup on
guid._msdcs.<root of domain>. This lookup does not work
correctly no matter where I try it.

Any help would be greatly appreciated!
Click to expand...

If the only way you can get to the DC is through the internet, then you need
a VPN connection to the domain. Otherwise all the AD ports and services are
blocked by the firewall.
Even if the DNS client could resolve the DCs records the ports are closed
and you wouldn't be able to contact the DC. If you set up a VPN connection
using the AD DNS in the VPN, you have an open pipe to the network and domain
authentication will work.
Otherwise, leave the cable disconnected and log on with a local account.
 
Back
Top