Solved

Need help with authentication problem for VPN users

Posted on 2008-06-26
2
263 Views
Last Modified: 2010-05-18
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?
0
Comment
Question by:achernob
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 30

Accepted Solution

by:
LauraEHunterMVP earned 500 total points
ID: 21876082
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

Featured Post

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A project that enables an administrator to perform actions within a user session context not just at the time of login but any time later on day(s) or week(s) later.
Active Directory security has been a hot topic of late, and for good reason. With 90% of the world’s organization using this system to manage access to all parts of their IT infrastructure, knowing how to protect against threats and keep vulnerabil…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

624 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question