How to configure VPN client to join a domain?

Hi all,

After several times of tweaking I finally got my VPN set up. The client side
is a Win2003 server co-located in the ISP side which serves also a web
server). The server side is a Netgear FVS318 router. The VPN protocol is
IPSec. I did not use remote access service.

After the VPN is connected, I am able to ping each other, or access files by
typing ip address. It is a great step forward, however I am not able to make
the machine a domain. Even computer browsing seems not there. I am not a
network expert but I have a quite a lot of hands on experience. what I
should do next to bring that computer into the domain? BTW, the office side
uses Windows 2003 active directory.

Your input is greatly appreciated.

Jack

Hi Jack,

First step would be to point your web server's DNS (DNS setting under
TCP/IP) to your AD DNS (probably your AD server).
To do this open your TCP/IP properties on your web server and under DNS
enter IP of your AD DNS server. This should be your primary DNS setting..

Clients (in this case web server) will find AD using DNS. If your DNS points
to something other then your AD DNS it will not find appropriate records and
will not be able to join the domain.

If this doesn't help, could you write down an error that you get when you
try to join the computer to domain.

Mike

"Jack Tan" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi all,
>
> After several times of tweaking I finally got my VPN set up. The client
side
> is a Win2003 server co-located in the ISP side which serves also a web
> server). The server side is a Netgear FVS318 router. The VPN protocol is
> IPSec. I did not use remote access service.
>
> After the VPN is connected, I am able to ping each other, or access files
by
> typing ip address. It is a great step forward, however I am not able to
make
> the machine a domain. Even computer browsing seems not there. I am not a
> network expert but I have a quite a lot of hands on experience. what I
> should do next to bring that computer into the domain? BTW, the office
side
> uses Windows 2003 active directory.
>
> Your input is greatly appreciated.
>
> Jack
>
>

Miha,

Miha,

Thanks a lot. After I set the DNS to the itnernal ip address, it works and I
succesfully joined the domain.

One more question: since that remote server is web server and it also needs
accessing internet resources occasionally. In case the VPN connection is
broken can it still access the Internet resources? Is there anyway to enter
a backup DNS address without impacting the domain connection?

Thanks again,
Jack


"Miha Pihler" <mihap-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Jack,
>
> First step would be to point your web server's DNS (DNS setting under
> TCP/IP) to your AD DNS (probably your AD server).
> To do this open your TCP/IP properties on your web server and under DNS
> enter IP of your AD DNS server. This should be your primary DNS setting..
>
> Clients (in this case web server) will find AD using DNS. If your DNS
points
> to something other then your AD DNS it will not find appropriate records
and
> will not be able to join the domain.
>
> If this doesn't help, could you write down an error that you get when you
> try to join the computer to domain.
>
> Mike
>
> "Jack Tan" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Hi all,
> >
> > After several times of tweaking I finally got my VPN set up. The client
> side
> > is a Win2003 server co-located in the ISP side which serves also a web
> > server). The server side is a Netgear FVS318 router. The VPN protocol is
> > IPSec. I did not use remote access service.
> >
> > After the VPN is connected, I am able to ping each other, or access
files
> by
> > typing ip address. It is a great step forward, however I am not able to
> make
> > the machine a domain. Even computer browsing seems not there. I am not a
> > network expert but I have a quite a lot of hands on experience. what I
> > should do next to bring that computer into the domain? BTW, the office
> side
> > uses Windows 2003 active directory.
> >
> > Your input is greatly appreciated.
> >
> > Jack
> >
> >
>
>

Sure. Enter e.g. your ISP's DNS in second place.

Mike

"Jack Tan" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Miha,
>
> Miha,
>
> Thanks a lot. After I set the DNS to the itnernal ip address, it works and
I
> succesfully joined the domain.
>
> One more question: since that remote server is web server and it also
needs
> accessing internet resources occasionally. In case the VPN connection is
> broken can it still access the Internet resources? Is there anyway to
enter
> a backup DNS address without impacting the domain connection?
>
> Thanks again,
> Jack
>
>
> "Miha Pihler" <mihap-(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Hi Jack,
> >
> > First step would be to point your web server's DNS (DNS setting under
> > TCP/IP) to your AD DNS (probably your AD server).
> > To do this open your TCP/IP properties on your web server and under DNS
> > enter IP of your AD DNS server. This should be your primary DNS
setting..
> >
> > Clients (in this case web server) will find AD using DNS. If your DNS
> points
> > to something other then your AD DNS it will not find appropriate records
> and
> > will not be able to join the domain.
> >
> > If this doesn't help, could you write down an error that you get when
you
> > try to join the computer to domain.
> >
> > Mike
> >
> > "Jack Tan" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > Hi all,
> > >
> > > After several times of tweaking I finally got my VPN set up. The
client
> > side
> > > is a Win2003 server co-located in the ISP side which serves also a web
> > > server). The server side is a Netgear FVS318 router. The VPN protocol
is
> > > IPSec. I did not use remote access service.
> > >
> > > After the VPN is connected, I am able to ping each other, or access
> files
> > by
> > > typing ip address. It is a great step forward, however I am not able
to
> > make
> > > the machine a domain. Even computer browsing seems not there. I am not
a
> > > network expert but I have a quite a lot of hands on experience. what I
> > > should do next to bring that computer into the domain? BTW, the office
> > side
> > > uses Windows 2003 active directory.
> > >
> > > Your input is greatly appreciated.
> > >
> > > Jack
> > >
> > >
> >
> >
>
>