Active Directory Sites and Services, issue with replication

Hello all,

This is a bit weird to me, but I am not sure what is wrong.  Background Info.

Windows 2012R2 servers running in Forest/domain functional level 2008r2.
Two Sites, connected with a 30MB vpn connections
Site A is main default site, Site B is remote site.
Site A contains a server with all FSMO roles.
Site B contains a server with R/W AD controller
In Sites and services, everything is default.  No custom links.
Intersite Transport is the "DEFAULTIPSITELINK"
Active Directory appears to be healthy.

I have two sites in Sites and services.  Each site has 1 server.  Each site has more than one subnet attached to it.  All the site links are automatically generate.  repadmin /kcc shows no errors, repadmin /syncall shows no errors.

When I create a user on a server in Site A, the user doesn't show up as a user on the AD server in Site B.  The converse is also true.  It is the same for new computers that join the domain.  I have waited 24 hours to see if the users would replicate eventually, thinking it was a timing issue.  Nope, not even after 24 hours.

If I move AD server in Site B to site A, the users that were created when the server was in Site B do not replicated to the server in Site A.  BUT......With the servers in the same site, if I create a brand new user, the user is IMMEDIATELY replicated to all servers, and all is good.  

After creating the user, and seeing that is replicated to all the servers, I can then move AD server from Site A back to Site B,  change password, change username, change anything, and it is replicated to all the servers.

I can freely move FSMO rolls between servers that are in different sites, so I feel confident that replication is working properly.  Since the domain was built with 2008r2, it is DFS replications, and all looks good in the console

Is there anything I can check to see what is going on.  Any, "A HA!" moments that anyone can share?

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.

If you create a user in one site and then force replication from that site to the other (without moving a DC), does the user show up at the other site?

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
thafemannAuthor Commented:
Hello DrDave,

I just did that, and the user SHOWED UP! me thinking.

I looked that the IP DEFAULTIPSITELINK, and then noticed that it was set to 1800.....30 hours.  So when I came back about 24 hours later, I was still 6 hours short.  I changed it to 90 minutes....

But wait, there is more.

For the fun of it I went into the replication schedule.  Yep......the entire schedule was set to "Not Available" except a very small 60 minute window on saturday.  Fun.......
Fun indeed! Sounds like you nailed it, though.
thafemannAuthor Commented:
The solution provided only gave me a nudge in the right direction to find the solution.  Thanks.  :)
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
Microsoft Server OS

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.