Need help with authentication problem for VPN users

OK, I'll try to be as descriptive as possible here.  I have users that are VPN home users that cannot authenticate to Active Directory.  We are using these Proventia VPN appliances at the users locations.

Our AD topology here is hub and spoke.  With our home office being the hub, and all the remote offices (not the home VPN users) being spokes with DCs at all the spoke locations, as well as DCs at the main office.

Due to security restrictions, these VPN users are only allowed to communicate with the Hub home office location, and all communication to spokes is restricted.

Make sense?

So, here's my understanding of AD authentication.  First a PC looks for a DC on its local subnet (There are none on the VPN users subnets) If it fails to find a local DC, it does an LDAP query to DNS to locate a DC.  Once a non preffered DC responds, it tells the PC its AD site information, and then caches in what preffered DC it should be using.

So the PC successfully queries DNS for a list of DCs, but since communcation to spoke DCs is shut off, these DCs do not respond, and the PC sits forever at a login screen and never receives its site information.

Placing a DC on the local subnet for the VPN users is not possible, since each PC is on its own subnet.

My question is, is there a way to force a PC to only look at specific DCs during initial authentication before it is able to grab its site information from AD?
achernobAsked:
Who is Participating?
 
LauraEHunterMVPConnect With a Mentor Commented:
Can you supernet the hub site to include the IP address range that you are providing to your VPN clients?  That's how I usually do it.  HUBSITE contains the IP ranges that physically correspond to that location, as well as the to Class C that I've allocated for incoming VPN connections. That way the VPN clients are -in- the HUBSITE, from AD's perspective.

If this isn't an option, then you're not going to have much luck - there isn't any good way to force an AD client to use a specific DC for auth.  AD expects all DCs to be similarly "available", so if you start muckling around with DENY ACLs on routers and VPN connections, you're going to run into exactly the type of situation that you're describing.
0
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.

All Courses

From novice to tech pro — start learning today.