AD Sites and Services - Same subnet and different Forests

I've an interesting one I haven't looked at before. Trying to get a server to login to the correct. Not sure if it's a networking issue or an AD Sites/Services config issue.

I've got a head quarter site (Site 1), and a remote site (Site 2).
I'm trying to get the server (ServerA) to login to Site 2, by having put the server in 10.13.250.0/24, which is the subnet assigned to Site 2.
However many times I reboot and try logging in to the server, it will continue to tell me I'm still in Site 1. Site 1 and Site 2 are in the same forest/domain, so I'm not sure why this simply doesn't work if I have 10.13.250.0/24 assigned to Site 2.

There is another forest that has 10.13.250.0/24 listed as a subnet as well, and it has its own separate domain controllers and AD. The subnet there is a different site (Site 3).
All servers in that subnet indeed login to Site 3.

So I'm wondering if Site 3 in that forest means we can't have 10.13.250.0/24 in Site 2 function properly...?

Would it mean I have to specify DNS server in the same site and allow the traffic?
garryshapeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ganesamoorthy STech LeadCommented:
Check the subnet conflict, don't think subnet in another forest is affect this, may be subnet /25/26 in same site


http://www.windowstricks.in/2009/11/free-tool-to-find-subnet-conflict-in.html
0
garryshapeAuthor Commented:
Thanks I tried the tool, and there's only one site so no conflicts fortunately.

I think the issue may be vLan/firewall related.
I can't even ping other DCs or netdom query dc to return any DC's from the server.
Also cannot gpupdate, it server says no server/dc can be contacted.
So I think it may be something with the firewall.
0
Will SzymkowskiSenior Solution ArchitectCommented:
As you have already listed client/server authentication is based on subnets. Did you change the IP address of the server to match the Site 2 Subnet?

when you login to that server run the following command..
set logonserver <press enter>

You should see the DC that you have authenticated with with should be from Site2. However if you have started that Group pOliyc is not working and there are other features that are not working then like you said it could be firewall related.

Will.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.