PC's on Site A cannot join DC on site B

I have 2 sites, lets call them A and B

At site B they have Windows 2008 R2 server as the DC

Site B is on 192.168.0 LAN

Site A is connected via VPN Tunnel ADSL.

Cisco router at each site.

Site A is on 192.168.1 LAN

PC's at site A cannot join the Domain. Although can ping DC at site B bu IP and hostname.
Can use OWA.
PC can be taken phsyically to site B from A and joined to domain without iuuse. Then returned to site A. Log in then takes 30mins and network is slow.

Have checked all main things like DC is only using itself as DNS etc.

Any ideas guys?

Also does anyone know where i can see a list of exactly what actions are taken when a PC joins a Domain. Not how to do it of course, but what requestes and protocols are fired up in sequence in order so i can find where the steps fail etc.
LVL 15
jerseysamAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Randy DownsConnect With a Mentor OWNERCommented:
Sounds like a DNS issue. You didn't say you could ping site by FQDN.

Maybe this will help - http://www.techrepublic.com/blog/10things/10-tips-for-troubleshooting-dns-problems/1964
0
 
jerseysamAuthor Commented:
yes can ping by FQDN
0
 
Nagendra Pratap SinghCommented:
Seems like your sites are not set properly.

On a slow logging on pc open command prompt and type this

echo %logonserver%

This will give you the DC it is logging to.

The check the IP of this PC, IP of DC B and the IP of DCA
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
TomRScottConnect With a Mentor Commented:
Given that DNS and basic routing is functioning, make sure that all Microsoft services are allowed to pass through the VPN tunnel.

A Couple References:
- Tom
0
 
jerseysamAuthor Commented:
Thanks Tom,

are these ports to be opeend on the DC firewall or routers?
0
 
TomRScottCommented:
The simple answer is the configuration of the VPN tunnel at both ends.

I'm not clear on your configuration. You mention routers, but routers don't normally block ports. I'm guessing your network (simplified) is the following:

LAN A - Firewall - Internet - Firewall - LAN B - DC
Given that scenario, the VPN tunnel between the two firewalls and the LANs behind them is the where you allow traffic targeting the ports to pass through. And, all that configuration is takes place on the firewalls (unless you have VPN devices in parallel with the firewalls, rare but I've seen it done).

 - Tom
0
 
jerseysamAuthor Commented:
Thanks for your imput Tom.

This is my feeling too. However, the equipment at each end is controlled by a 3rd party. They say, of course, that their configs are fine.

I am still working on the issue, but thought i would update you. Still under investigation.
0
 
Nagendra Pratap SinghCommented:
Did you check your sites in Sites and services for the correct IP subnets?
0
 
TomRScottCommented:
Could you provide a more complete diagram than my guess above?

Please include the 3rd Party equipment.  It would be good to know what type of equipment that is and where it is in the line of communication.

 - Tom
0
 
jerseysamAuthor Commented:
Quick update.

Traffic is not firewalled between the 2 sites.

If i try to join the domain with an incorrect username or password then i get a logon authentication failure, so it must be talking, but if i use the correct username/password then it just hangs for a while and fails.

Do you think i should maybe configure RRAS on the DC?

Am still struggling a bit.
0
All Courses

From novice to tech pro — start learning today.