Question Locked

Can't map drive to a workstation across a VPN.

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

I am running SBS 2003 Prem. I also have 2 more 2003 Servers that are domain controllers in 2 separate physical sites. All sites are connected via PPTP VPN. The SBS uses it's own RRAS and ISA for routing and the other 2 sites have a Draytek router. All Servers and workstation are members of the same domain. The network is fully routed by way of static routes.

Everything seems fine replication works. Everything can ping each other by name or ip address.

Only problem is you cannot map a drive or browse to a workstation on another lan (ie via vpn) you can map a drive to a server on another lan (via vpn) or you can map a drive to a workstation of the same lan. Don't think it's an ISA problem as the problem exists also between the lans with the Draytek routers too.

I've been stuck on this problem for a while and would be eternally grateful if anyone knows the solution. Many thanks in advance.

13 replies

by unhappyuser

Have you updated your hosts/lmhosts file so the server name, and it's ip, are in the file? We had that same issue until we updated the file and then the mapping worked.

EMD

by ian.x.roberts

Thanks for replying. Do you mean update the hosts/lmhosts file on where I am trying to map a drive from or on each of the workstations I would try and map a drive to ?

by unhappyuser

On each workstation. For example: We have to connect to a remote location, via VPN, from two computers in our office. I updated the lmhosts file with the name of the server and it's ip on both PC's.

We run a script to automatically connect to the remote network then map a drive letter to that server and it's share. I can show you our script if you want it as an example.

EMD

by wizard-09

Looks like this is a DNS issue maybe, have you got a copy of the other domains dns like server1 has a copy of server2 as well as it's own and the same for server2 having server 1's DNS as well as its own DNS.

by ian.x.roberts

Hi ! Really don't think it is a DNS issue. All servers and workstations ar a member of the same domain. Also all can ping each other and get a reply so they can find each other okay. Also not able to map drive using ip address either so that takes DNS out of the equation. Thanks for looking though.

by wizard-09

Whats the error message you are getting when you try to connect.

by wizard-09

His DNS server should be doing this for him or im i getting this all wrong?

Should he not have A records for this?

by unhappyuser

In our case we don't want anyone else connecting to this server. The remote network is also not part of our domain.

I was thinking his setup may be like ours but you may be correct in your assumption and he needs to set an A record for it.

EMD

by wizard-09

Maybe should also check that NetBIOS over TCP/IP is enabled.

by unhappyuser

I didn't read your question well enough. I though you couldn't ping by name.

Check your VPN client settings. What is the Transport set to? Is enable transparent tunneling enable? What is your authentication set to? What are the settings on the other end? Is there a setting that is blocking the mappping?

EMD

by ian.x.roberts

Guys, thanks so much for taking the time to help me with this. I finally cracked it. I was the XP firewall. When I first looked at this I discounted it as I could see file and print sharing was enabled by group policy and because I could get through it from another computer on the same subnet. I started looking at a number of things like SMB registry settings then enabling Netbios on the demand dial interface. I got WINS running. However looking closer at the firewall setting I noticed the file and print sharing had a scope of local subnet set. After amending the scope in group policy to include my other subnets and running gpupdate /force it worked.

by unhappyuser

Thank you for posting. Some people never reply back after an issue has been resolved. An answer could help someone else with the issue. Glad to hear you resolved it!

EMD

This discussion is closed to new replies.