Machine disjoined/joined to domain remotely via VPN

[greg.hart]

Hello,

If this is the wrong forum, please direct me to the correct one.

We have a remote employee connected via VPN whose machine was
disjoined from our domain. We have gone through the process of
rejoining this machine to the domain and the machine itself appears to
have been joined. It shows up in AD under computers, etc.

However when the person tries to login to the domain on the Windows XP
login screen, it states "<Domain Name> not available". I am assuming
it is because the person has not yet logged in the domain after the
machine has been rejoined, thus no credentials are cached locally.
The person can login with the local admin account.

Is there any way for me to get them to be able to login with there
domain id,password into the machine? I really don't want them to have
to send their machine in to fix this.

Thanks,
Greg

 

[Shenan Stanley]

If this is the wrong forum, please direct me to the correct one.

We have a remote employee connected via VPN whose machine was
disjoined from our domain. We have gone through the process of
rejoining this machine to the domain and the machine itself appears
to have been joined. It shows up in AD under computers, etc.

However when the person tries to login to the domain on the Windows
XP login screen, it states "<Domain Name> not available". I am
assuming it is because the person has not yet logged in the domain
after the machine has been rejoined, thus no credentials are cached
locally. The person can login with the local admin account.

Is there any way for me to get them to be able to login with there
domain id,password into the machine? I really don't want them to
have to send their machine in to fix this.

If your VPN (whatever you are using for a VPN client) can connect before
logon - yes - if they can set that up, that is.

It needs access to your domain - I am assuming that your domain is wisely
behind a firewall/on a private network. This means they will need to be
VPN'd in before they logon in order to pass their credentials through.

 

[greg.hart]

If your VPN (whatever you are using for a VPN client) can connect before
logon - yes - if they can set that up, that is.

It needs access to your domain - I am assuming that your domain is wisely
behind a firewall/on a private network.  This means they will need to be
VPN'd in before they logon in order to pass their credentials through.

How can I start the VPN (Cisco VPN) before getting passed the login
screen since the login screen appears first when booting XP? I can
login as a local admin start the VPN, but I don't know of a way to
"Switch IDs" except for logging off XP which would kill the VPN
connection. Am I missing something?

 

[Shenan Stanley]

If this is the wrong forum, please direct me to the correct one.

We have a remote employee connected via VPN whose machine was
disjoined from our domain. We have gone through the process of
rejoining this machine to the domain and the machine itself appears
to have been joined. It shows up in AD under computers, etc.

However when the person tries to login to the domain on the Windows
XP login screen, it states "<Domain Name> not available". I am
assuming it is because the person has not yet logged in the domain
after the machine has been rejoined, thus no credentials are cached
locally. The person can login with the local admin account.

Is there any way for me to get them to be able to login with there
domain id,password into the machine? I really don't want them to
have to send their machine in to fix this.

If your VPN (whatever you are using for a VPN client) can connect
before logon - yes - if they can set that up, that is.

It needs access to your domain - I am assuming that your domain is
wisely behind a firewall/on a private network. This means they
will need to be VPN'd in before they logon in order to pass their
credentials through.

How can I start the VPN (Cisco VPN) before getting passed the login
screen since the login screen appears first when booting XP? I can
login as a local admin start the VPN, but I don't know of a way to
"Switch IDs" except for logging off XP which would kill the VPN
connection. Am I missing something?

Not really a Windows/Microsoft related question. But the answer is fairly
simple:
A setting in your VPN client...

Given what you have:
http://lmgtfy.com/?q=Cisco+VPN+client+connect+before+logon

Would come up with several links. Not knowing the specific version of the
client of choice, I cannot narrow it down further for you - but I would bet
the FAQs, built-in help, etc would come in handy - as would likely some of
the links given in the results of the above Google search.

For example:
http://www.howtonetworking.com/Routers/ciscovpn1.htm

The particular steps are not very - if any - different between v4 and v5 of
the Cisco clients, however. Something along the lines of:

- Launch the VPN Client...
- Look in the "Options" menu for "Windows Logon Properties" and select it...
- Enable the "start before logon" option...

I cannot recall if a reboot is necessary after saving those options.

Hope that helps - let us know!

 

[greg.hart]

Not really a Windows/Microsoft related question.  But the answer is fairly
simple:
A setting in your VPN client...

Given what you have:http://lmgtfy.com/?q=Cisco+VPN+client+connect+before+logon

Would come up with several links.  Not knowing the specific version of the
client of choice, I cannot narrow it down further for you - but I would bet
the FAQs, built-in help, etc would come in handy - as would likely some of
the links given in the results of the above Google search.

For example:http://www.howtonetworking.com/Routers/ciscovpn1.htm

The particular steps are not very - if any - different between v4 and v5 of
the Cisco clients, however.  Something along the lines of:

- Launch the VPN Client...
- Look in the "Options" menu for "Windows Logon Properties" and select it....
- Enable the "start before logon" option...

I cannot recall if a reboot is necessary after saving those options.

Hope that helps - let us know!

Sorry. I posted a little too quick. I took a look around after your
last post and found the Start Before Login option. I just test it on
another machine and it seemed to work. I appreciate your time.

Greg

 

[Shenan Stanley]

If this is the wrong forum, please direct me to the correct one.

We have a remote employee connected via VPN whose machine was
disjoined from our domain. We have gone through the process of
rejoining this machine to the domain and the machine itself appears
to have been joined. It shows up in AD under computers, etc.

However when the person tries to login to the domain on the Windows
XP login screen, it states "<Domain Name> not available". I am
assuming it is because the person has not yet logged in the domain
after the machine has been rejoined, thus no credentials are cached
locally. The person can login with the local admin account.

Is there any way for me to get them to be able to login with there
domain id,password into the machine? I really don't want them to
have to send their machine in to fix this.

If your VPN (whatever you are using for a VPN client) can connect
before logon - yes - if they can set that up, that is.

It needs access to your domain - I am assuming that your domain is
wisely behind a firewall/on a private network. This means they
will need to be VPN'd in before they logon in order to pass their
credentials through.

How can I start the VPN (Cisco VPN) before getting passed the login
screen since the login screen appears first when booting XP? I can
login as a local admin start the VPN, but I don't know of a way to
"Switch IDs" except for logging off XP which would kill the VPN
connection. Am I missing something?

Not really a Windows/Microsoft related question. But the answer is
fairly simple: A setting in your VPN client...

Given what you have:
http://lmgtfy.com/?q=Cisco+VPN+client+connect+before+logon

Would come up with several links. Not knowing the specific version
of the client of choice, I cannot narrow it down further for you -
but I would bet the FAQs, built-in help, etc would come in handy -
as would likely some of the links given in the results of the above
Google search.

For example:
http://www.howtonetworking.com/Routers/ciscovpn1.htm

The particular steps are not very - if any - different between v4
and v5 of the Cisco clients, however. Something along the lines of:

- Launch the VPN Client...
- Look in the "Options" menu for "Windows Logon Properties" and
select it...
- Enable the "start before logon" option...

I cannot recall if a reboot is necessary after saving those options.

Hope that helps - let us know!

Sorry. I posted a little too quick. I took a look around after
your last post and found the Start Before Login option. I
just test it on another machine and it seemed to work.
I appreciate your time.

Glad you got it sorted!