RE: Clients logging into the wrong DC at remote site

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance


Yeah I've been through this one. Everything checks out fine. Seems like I
have a one off problem that just doesn't make much sense. I think I am going
to demote the DC and re-install AD to see what happens. Hopefully that will
work.


thanks
"Masterplan" wrote:

Hi,

Follow the steps on this article to solve the problem:
http://support.microsoft.com/kb/247811.

Hope this will help you!

"scott6099" wrote:

Hmmm thanks for the response but the link appears to be dead...



"Jon E" wrote:

Scott,

Take a look at this site on DC locator process
http://blogs.dirteam.com/blogs/jorge/archive/2007/07/01/dc-locator-process-in-w2k-w2k3-r2-and-w2k8-part-1.aspx

--
Jon


"scott6099" wrote:

I have setup a test network with 2 subnets:
172.16.0.0 mask 255.255.0.0 (Site A)
192.168.1.0 mask 255.255.255.0(Site B)

there are 3 DC's in site A and 1 Exch Svr and one DC and and Exch Svr in
Site B. Site B and A are connected via 100Mb Ethernet router. All firewalls
are disabled between sites. I have configured AD sites and services to
reflect the above configuration and replication and DNS are all working fine.
The exchange servers are also working fine and routeing mail with no issues.
The problem is all the clients think they are in Site A (per nltest
/dsgetsite). The DC in site B reports correctly that it is in site B. I
have run DC-Diag and netdiag and all tests pass. The only reason I
discovered the issue was when looking at the exchange server at site b I
noticed it was using Site A's DC's for the configuration and GC. I have
been through just about all the messages here looking at similar issues and
have still not been able to resolve this. Among the things I have done
include cleaning up DNS so that the server records show only the correct
servers under each site. It does look like occasionally the exchange server
will re-discover that it is in Site B but always switches to Site A after
about 15 minutes. I also now know far more about the logon process than I
ever wanted and short of wiping the DC and starting over I am currently
stuck.

Thanks in advance for any help or suggestions

Scott


.

Relevant Pages

  • Re: ? for Mark Fugatt [MVP]
    ... your Exchange server is configured to correctly use DNS, ... you receiving mail is that the servers that host your public DNS information ... > confirm my DNS configuration on my server is correct. ...
    (microsoft.public.exchange2000.win2000)
  • Re: NDRs sending to domain - Urgent Help Required
    ... The domain in question in Recipient Policy should be set as non auth (you ... question to an accepting Exchange server at the sister company. ... A configuration error in the e-mail system caused the ...
    (microsoft.public.exchange.admin)
  • RE: Clients logging into the wrong DC at remote site
    ... Take a look at this site on DC locator process ... reflect the above configuration and replication and DNS are all working fine. ... It does look like occasionally the exchange server ...
    (microsoft.public.windows.server.active_directory)
  • RE: Clients logging into the wrong DC at remote site
    ... there are 3 DC's in site A and 1 Exch Svr and one DC and and Exch Svr in ... reflect the above configuration and replication and DNS are all working fine. ... It does look like occasionally the exchange server ...
    (microsoft.public.windows.server.active_directory)
  • Outlook 2007 - Exchange server unavailable on 1 of 2 almost identical systems
    ... However on the virtual system, with an identical configuration, some things just give an error that the Exchange server isn't available. ... Both systems run Outlook 2007 SP2, and I have no access to the Exchange server admin interface. ... Oh, and on the Outlook Web Access interface, everything works, even the Global Address List... ...
    (microsoft.public.outlook.general)