asked on

VPN

I can VPN in and remote connect to my network at work but I can't see any of the computers or printers on the internal network. I have a feeling it has something to do with how i set up my WINS server. I am running on SBS 2003.

nprignano

can you connect to these devices using their internal IP? can you use Remote Desktop and connect this way? is it just UNC naming that does not work, or can you not connect at all? If you have a WINS server setup, you can use WINS to do UNC to IP translation as DNS does nto work over VPN.

nprignano

iscairns

ASKER

Yes i can vpn in them use remote desktop connect to connect using the internal IP but when i look in network places it only shows my computer.

nprignano

is your PC a member of the domain? how is the vpn authentication handled - by the firewall or using a RADIUS server?

nprignano

iscairns

ASKER

Yes my Pc is a membe of the domain and the vpn comes through a Firewall

iscairns

ASKER

Ok so i changed around a few things and now i can see the other computers but i can only access the server. the others say that the network path was not found

nprignano

is the network path found when you use the IP? what few things did you change around?

johnrmorris

The easiest fix is to add all the pc's you want to connect to into your hosts file. XP C:\WINDOWS\system32\drivers\etc or on 2000 C:\WINnt\system32\drivers\etc . There is an example in the hosts.sam (sample) file, just add your entries below it and save the file without an extension. You should then be able to access the pc's by name.

ASKER CERTIFIED SOLUTION

Rob Williams

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

nprignano

you could also assign the wins server using DHCP.

nprignano

Rob Williams

If using the built-in Windows VPN server it doesn't handle DHCP assignments as you would expect and as I recall will not assign scope options such as WINS. However worth a try as it would be the better option. If using a DHCP relay agent it may work OK.

ImmediateAction

*not to sure about this, so take it as an idle suggestion to check.
You might want to check if NetBIOS over tcp/ip is enabled on the network card on the VPN Server that is accepting the connection

(Windows) Control Panel --> Network Connections --> < your LAN Connection accepting VPN Clients> Properties --> TCP/IP --> Advanced --> WINS --> "Enable NetBIOS over TCP/IP"

ImmediateAction

**and i would expect there was a firewall on / in front of that network card. Not sure about nps first comment about DNS, but i would expect a dns address on the vpn client that is specific to the remote domain AD DNS server; so it can find domain specific resources.