Authentication to wrong AD Domain server

  • Thread starter Thread starter Ed Kaye
  • Start date Start date
E

Ed Kaye

I have a Win 2000 server that seems to be authenticating to the wrong AD
domain controller. The Server has more than one NIC card, so we utilize
persistent routes to point to the local networks. The persistent routes
are using a metric value of 6. Only one NIC card is set up with a Default
Gateway parameter (by default a metric value of 1). The Local AD domain
controller is located on a local lan pointed to by a persistent route. My
AD group believes that we are routing via the Default Gateway because we are
not authenticating to the Local AD domain controller. How can this happen?

Ex: Default Gateway: 198.169.x.x
Persistent route: 172.21.x.x
Persisten route: 172.22.x.x
AD Local Domain: 172.22.y.y
 
Check which DNS server is in use and whether the right global catalog server
is reachable. Also I would ensure the NIC with IP responsible for the local
segment is at the top of bindings list. netdiag could also help if you run

netdiag /debug (or v(erbose)) /test:dclist
and
netdiag /debug /test:dsgetdc

Other tests syntax is available through 'netdiag /?'.
 
Back
Top