VPN / Remote computer joining the domain

I am using Win2k3 Sm. Bus. at office. I am trying to connect from home
to my network. I connect and it authenticates with no problem, however
I cannot browse my network. I go to My Computer and try to join the
domain, thinking that may be I should do that before being able to
browse the network, however it tells me it cannot locate my domain
controller. Any ideas?

You don't need to join to the domain to browse the network. However, you may
need to setup WINS server. This search result may help.
Name resolution on VPN
Name resolution is big issue in VPN access. If your VPN server doesn't
setup correctly or the VPN client can't receive the VPN DNS and WINS
settings, ...
www.chicagotech.net/nameresolutionpnvpn.htm


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"john" <(E-Mail Removed)> wrote in message
news:9e8e8da0-c577-4217-a8f2-(E-Mail Removed)...
>I am using Win2k3 Sm. Bus. at office. I am trying to connect from home
> to my network. I connect and it authenticates with no problem, however
> I cannot browse my network. I go to My Computer and try to join the
> domain, thinking that may be I should do that before being able to
> browse the network, however it tells me it cannot locate my domain
> controller. Any ideas?

VPN just gives you an IP connection. It is not like a LAN connection.
Browsing depends on broadcasts, and those don't work on a WAN connection. It
is difficult to get it to work for a dialup client, even with WINS.

You will probably need to use the FQDN to contact your LAN machines, not
just the machine name. The remote client should get the DNS server address
when it connects but you will need to specify the domain suffix (unless you
put it in the connection properties on the client).

When you can ping the server by name you can see its shares using a net
view command. You can then map a share using net use (and you can specify
your domain username and password in the command).

You can't join a dialup machine to the domain. You can log in to the
domain, but you have to do it at connection time using the "login using a
dialup connection" option. Most users don't like that because they have to
log out locally before they can connect via VPN. Mapping a share manually is
probably better.

"john" <(E-Mail Removed)> wrote in message
news:9e8e8da0-c577-4217-a8f2-(E-Mail Removed)...
> I am using Win2k3 Sm. Bus. at office. I am trying to connect from home
> to my network. I connect and it authenticates with no problem, however
> I cannot browse my network. I go to My Computer and try to join the
> domain, thinking that may be I should do that before being able to
> browse the network, however it tells me it cannot locate my domain
> controller. Any ideas?

On Aug 27, 3:45*pm, "Bill Grant" <not.available@online> wrote:
> * *VPN just gives you an IP connection. It is not like a LAN connection.
> Browsing depends on broadcasts, and those don't work on a WAN connection.It
> is difficult to get it to work for a dialup client, even with WINS.
>
> * You will probably need to use the *FQDN to contact your LAN machines, not
> just the machine name. The remote client should get the DNS server address
> when it connects but you will need to specify the domain suffix (unless you
> put it in the connection properties on the client).
>
> * * When you can ping the server by name you can see its shares usinga net
> view command. You can then map a share using net use (and you can specify
> your domain username and password in the command).
>
> * * You can't join a dialup machine to the domain. You can log in to the
> domain, but you have to do it at connection time using the "login using a
> dialup connection" option. Most users don't like that because they have to
> log out locally before they can connect via VPN. Mapping a share manuallyis
> probably better.
>
> "john" <johnbah...@hotmail.com> wrote in message
>
> news:9e8e8da0-c577-4217-a8f2-(E-Mail Removed)...
>
> > I am using Win2k3 Sm. Bus. at office. I am trying to connect from home
> > to my network. I connect and it authenticates with no problem, however
> > I cannot browse my network. I go to My Computer and try to join the
> > domain, thinking that may be I should do that before being able to
> > browse the network, however it tells me it cannot locate my domain
> > controller. Any ideas?

I am not using a dialup amchine. Both the network and remote have dsl
connections.

"john" <(E-Mail Removed)> wrote in message
news:bbd565fc-c66b-4cbc-ae58-(E-Mail Removed)...
On Aug 27, 3:45 pm, "Bill Grant" <not.available@online> wrote:

> I am not using a dialup amchine. Both the network and remote have dsl
> connections.

Actually you are. VPN is a dialup technology. VPN just uses an IP# in place
of a Phone# and uses a Virtual Dialup Adapter instead of a Modem. But
beyond that iwt works on the same priciples as old style dialup.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------