Windows Forum

Ask something
Discussion Locked

VPN/PPTP connection Network Neighborhood

0 helpful
6 replies

by nateh

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

HI all,

I just set up a client with a remote connection from home using the built-in VPN to get on her office network.

They are running Win2003 SBS and her home PC is WinXP Pro.

The VPN connection is using PPTP and it connects fine. However, when she tries to look at some files in a directory on the remote server, the directory shows empty - no contents. If she waits about 7-8 minutes, the contents appear suddenly.

I have recreated this several times and I am stumped.

If I map a drive to the server internal IP address, I can get to the directory immediately. If I map a drive to the server name, and attempt to see the directory contents - same thing. Can't see it for about 7-8 minutes.

Seems like some name resolution, but I can't figure out what or why?

Any ideas?

thanks

Nate

6 replies

by curlergirl

How are you providing DNS services for the VPN connection - statically mapped or DHCP? Her VPN connection should be using the same DNS server settings as the workstations at the office. So, if you're not using DHCP to assign DNS servers, then you need to assign them statically. I'm thinking that if the primary DNS setting is pointing to a server at her ISP or something, it would take a long time to resolve names.

Hope this helps!

by nateh

I am using DHCP for the workstations in the office. I also set up the incoming RRAS to use the DHCP to assign addresses.

by greybeard770

names will resolve quicker if you include the FQDN instead of the netbios name. Using the IP address eliminates the time for name resolution as you have seen. Use server.domain.com instead of just SERVER.

by shmaltz

In my experience it is best that on the remote computers you create enteries in both the Host file and the lmhost file for the computers that this user will have to accsss.
If this is impossible, then make sure:
1. The local (the computer in the VPN client office) IP Net Address is different than the one in the remote office (VPN Server office). i.e. don't use 192.168.1.x in both places.
2. Her DNS always points to the DNS Servers in the remote office (this is a problem when she is not connected with VPN, but solves the hosts file problem).
3. Her WINS setting points to the WINS server in the remote office, if you don't have WINS on your network then you will have to setup LMHOST files.

If the problem is like you describe then it is for sure a name resolution problem, in wich case you want to make sure that you have good name resolution which is only possible if you set it up like described above, unless you have NETBIOS over TCP/IP disabled, in which case the WINS and LMHOST is not required.

This discussion is closed to new replies.