Re: Joining a domain remoted via VPN



Jeff,

Just remembered that joining a domain is easy. However after logging off
and then logging on, you need to logon with the VPN connection active. At
the three fingered salute screen, check logon using a dial up connection,
and you need to have the VPN set for anyone to use (IIRC). Sometimes it
gets a bit messy at this step. I can't remember the exact sequence, but I
think given a certain sequence it will reject the VPN as a dial up
connection during a logon, but then on the second try it accepts the dial
up/VPN connection.

If you have problems with this part, post back and I will try to figure out
the sequence and nail it properly. I only add a box to a domain
infrequently, so I usually muddle through it, but you needing the sequence
will cause me to add the process to my "how to" folder.

Jeff


"sailorfej" <jeff@xxxxxxxxxxxxx> wrote in message
news:1193729835.267123.137190@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Oct 29, 9:14 pm, "Jeff Jones" <no...@xxxxxxxxxxx> wrote:
Jeff,

I haven't had any problems joining a XP Pro box to a NT4 domain when I am
VPN into the network where the domain is.

I wouldn't think that the domain flavor would matter, I have always
thought
being VPN is as good as being wired into the network.

YMMV, test first, all the usual disclaimers.

Another Jeff"sailorfej" <j...@xxxxxxxxxxxxx> wrote in message

news:1193602510.056418.199940@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I have a interesting question, regarding joing new workstations to a
Windows 2003 domain.

I am setting up a new workstation for a client's network, I doing this
at my offices, the network the workstation will eventually live on is
at a different location. In order to complete the setup, I need to
join the workstation to the Active Directory domain at the client
site.

In the past I have always just got as far as I could at my office,
then spent a couple of hours finishing the setup at the client site
after joining the domain locally .

It would be a lot easier if I could join the computer to the domain
remotely and compete the setup here, and then just take the
workstation to the client, plug it in and go.

I do have a pptp vpn server setup at the client site, but it is not
running on a Windows server, and is using local authentication.

What I want to know is, has anyone ever tried joining a Windows XP
workstation to a domain remotely via its own pptp vpn client, and what
if any gotchas they ran into?

Thanks,
Jeff

Thanks Other Jeff,

I will give it a go, and post the results here.

Jeff



.



Relevant Pages

  • RE: SBS Standard VPN Setup using L2TP
    ... I understand that the login script is not applied when users logon through ... Windows" dialog box and choose an appropriate connection to gain access to ... and then logon by using dial-up connection option after you create the VPN ... Did you configure a login script group policy in AD or configure a logon ...
    (microsoft.public.windows.server.sbs)
  • Re: Disconnecting and reconnecting pc to domain remotely
    ... There's a procedure on the smallbizserver site for joining a computer ... reboot and a domain logon will work over VPN. ... Second and subsequent times, connect the VPN, switch the workstation ...
    (microsoft.public.windows.server.sbs)
  • Re: Bypass Domain GPO when not connected to network?
    ... There is an option to logon via dial up connection ... choose the VPN connectoid. ... them how to use secedit/gpupdate to refresh computer configuration policy ...
    (microsoft.public.win2000.security)
  • Re: offline files and vpn
    ... Perhaps try establishing the VPN connection PRIOR to logging into your ... Options>> Windows Logon Properties ... The folder is set up for offline use. ...
    (microsoft.public.windowsxp.work_remotely)
  • Where are VPN Connections in Windows Logon Dialog Box?
    ... up connection" in the Windows XP Logon Screen, ... The workstation then dials in to the RAS server, ... No we are implementing a Windows 2003 RAS Server with VPN over IPSec for our ...
    (microsoft.public.windowsxp.work_remotely)