Adding A System connected via VPN to domain.

I have a system that I added to my domain over a VPN connection. It successfully added, but after restart when I try to login to a domain account, it says it cannot locate a domain controller (makes since since I can't run the VPN client to connect to my network until I'm actually logged into the computer) Is there a way around this? Or does the system actually need to be physically connected to my network first?
LVL 1
Methodman85Asked:
Who is Participating?
 
Rob WilliamsCommented:
Once the computer has joined a domain, there is a check box option in the logon box that allows for a dial-up connection. If you are using a Windows VPN check that box and during logon and you will be presented with a list of dial-up and/or VPN connections. Choose the appropriate VPN connection, and it will connect and authenticate before logging into the PC so that the domain is present at logon, allowing for group policy to be applied, and logon scripts executed.
0
 
Methodman85Author Commented:
And if it's not a Windows based VPN?
0
 
Rob WilliamsCommented:
That option only works with Windows VPN client.
Seems to me Cisco has a similar option, though it works differently, but it is the only other I know of.

However, normally you can log onto the PC using cached credentials, and then connect the VPN. Though this allows you access to resources, it does not apply group policies or run logon scripts.
I suspect the issue is that until you have logged in once to the domain, there are no cached credentials. Is it possible to set up a Windows VPN connection just long enough for one connection, or visit the site long enough to log on?

If not you can use a local non domain account, and then connect the VPN, however that negates any advantages of joining the domain, but it does allow access to reources.

0
On-Demand: Securing Your Wi-Fi for Summer Travel

Traveling this summer?Check out our on-demand webinar to learn about the importance of Wi-Fi security and 3 easy measures you can start taking immediately to protect your private data while using public Wi-Fi. Follow us today to learn more!

 
LBizzleCommented:
System should not NEED to be connected to the network as the profile should be cached locally for instances just like this. So if the network goes down people can still accomplish some work being able to login locally.

Is the domain (Is primary Domain controller) Windows 2000 or 2003? Is the Machine XP?
0
 
LBizzleCommented:
RobWill is correct, one of the Options of the Cisco client is a check box to launch VPN client before logging in. In the Cisco client under Options is Windows Logon Properties, there is a check box to  Enable start before login.
0
 
Methodman85Author Commented:
Thank you both.
The login couldn't be cached since there has never been a successful login, the system was remotely added to the domain, therefore after reboot was the first actual login to the domain, that's why I needed the VPN connection beforehand.
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.