Connecting to a domain using VPN

[Dan]

I have a win2k3 network and have remote clients using XP Pro. They connect
using Symantec VPN client or WindowsXP VPN. I was told that remote users
and/or laptop users should have there machine setup on the domain.

How do I do that? I tried testing. Connected VPN, went to My
Computer/Properties --Change. Entered the admin info and received the
message Welcome to the XYZ domain, must reboot to take affect.

So I rebooted and because when the system first comes up I am not connected
to the VPN, I cannot log onto the domain. Is there a way around this? Or
should remote users log onto their local machine then VPN?

Dan

 

[Phillip Windell]

Examine the Crtl+Alt+Del login prompt. There is a checkbox to "Log in using
dialup connection",...use it,...choose the VPN Connection. But you are
probably just plain screwed with the Symantec VPN Client.

Actually they don't have to be domain members and do not have to be logged
into the domain for every function. Some things only require the correct
user credentials.

Remote Access VPN will never create an identical situation to being
physically in the office on the LAN. Even if you come close to simulating
the behavior, the performance will still always stink. Get used to it. VPN
is just a glorified "dial up" connection and it does not, and probably will
never, live up to all the maketing "hype" about it.

 

[Dan]

Thanks Phillip,

Crtl+Alt+Del prompt does not show the VPN it shows only dial-up. The
strange part is that if I join a laptop on-location then log in
"on-location" then go off-site I can log onto the laptop and once the VPN is
established all is well. What I'm facing now is that remotely I can join
the domain which requires a reboot. Once rebooted I can't logon with the
Userid Domain pair. I even tried adding the users in the control panel but
since he never logged on "to the domain" the remote computer does not have
the credentials to allow him to log on.

Anyway, Thanks for the help....

Dan

Examine the Crtl+Alt+Del login prompt. There is a checkbox to "Log in using
dialup connection",...use it,...choose the VPN Connection. But you are
probably just plain screwed with the Symantec VPN Client.

Actually they don't have to be domain members and do not have to be logged
into the domain for every function. Some things only require the correct
user credentials.

Remote Access VPN will never create an identical situation to being
physically in the office on the LAN. Even if you come close to simulating
the behavior, the performance will still always stink. Get used to it. VPN
is just a glorified "dial up" connection and it does not, and probably will
never, live up to all the maketing "hype" about it.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

I have a win2k3 network and have remote clients using XP Pro. They connect
using Symantec VPN client or WindowsXP VPN. I was told that remote users
and/or laptop users should have there machine setup on the domain.

How do I do that? I tried testing. Connected VPN, went to My
Computer/Properties --Change. Entered the admin info and received the
message Welcome to the XYZ domain, must reboot to take affect.

So I rebooted and because when the system first comes up I am not connected
to the VPN, I cannot log onto the domain. Is there a way around this? Or
should remote users log onto their local machine then VPN?

Dan

 

[Phillip Windell]

Thanks Phillip,

Crtl+Alt+Del prompt does not show the VPN it shows only dial-up. The

VPN is a dialup connection and it will be listed as a dialup connection. If
the machine you are atempting this with is one that uses the normal Windows
Dialup Networking to create the VPN connection then is will be listed there.
If the machine is one using the Symantec Client, then it probably won't,...I
am not familiar with the Symantec situation.

strange part is that if I join a laptop on-location then log in
"on-location" then go off-site I can log onto the laptop and once the VPN is
established all is well.

That is not strange. That is normal. You are using the "cached account" that
the domain recognizes once the link comes up.

What I'm facing now is that remotely I can join
the domain which requires a reboot. Once rebooted I can't logon with the
Userid Domain pair. I even tried adding the users in the control panel but
since he never logged on "to the domain" the remote computer does not have
the credentials to allow him to log on.

You first have to actually log the machine in with his credentials while
dircetly on the domain to create the "cached account" before that will work.
It is also possible that the cached account could be lost later and you
would have to repeat the process. I don't consider "cached accounts" to be
dependable,..they should only be looked at as a convienience.