Re: ADAM connecting to incorrect server

What about the secure channel on the local machine?

nlest /sc_query:domainname




--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm


Luis Carlos Delgado (Costa Rica) wrote:
Hello:

We ran the nltest command as you instructed and it returned DC's from the local subnet.

We also checked the Subnets/sites configuration in AD Sites and Services and everything seems to be correctly configured.

Any ideas?

Thanks.

"Joe Richards [MVP]" wrote:

Is your site/subnet definitions correct? What DC does the server itself prefer to use when you look at nltest /dsgetdc:domainname


--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm


Luis Carlos Delgado (Costa Rica) wrote:
We installed ADAM on a member server.

Our problem is that a network traffic monitoring application reports that ADAM is connecting to a server that is across the WAN (on a very slow link).

We need to enforce ADAM to connect to DC's on the local subnet, not across the WAN.

netstat confirms what the application reports, that ADAM is connecting to a server across the WAN.

Any ideas on how to fix this?

Thanks.
.

Relevant Pages
Loading