Browsing issues with VPN

[Sholeh]

I have a Linksys BEFVP41 in my home office. I have set up two tunnels on the VPN router. I tried setting up IPSec on the remote computers without success. In fact I can no longer see any of the computers on my network (connected locally) on one of the computers any more. Any ideas why that is? I am now trying SSH Sentinel. With this software I am able to establish connections from both remote computers. However, one of the computers shows up in Network Neighborhood and the other doesn't. The one that does, I can not ping the name or IP of. I can ping the IP, but not the name of the other computer, which doesn't show up in NN. The one that I can see, but not ping, is behind a Linksys router on XPPro. The one that I can not see, but can ping, is behind a D-link router on W2000Pro. I do not have a domain set up at my home office, just a workgroup. All of the computers have the same workgroup name. I don't know much at all about the DNS and WINS settings and they are at the default settings. The remote computers are connecting through an IP. What should I do to be able to see and browse the computers locally and/or remotely?

Thanks,
Doug

 

[ChicagoTechNet]

this may help quoted form

http://www25.brinkster.com/ChicagoTech

Unable to browse through PPTP/VPN connection
Symptoms: 1. If the WINS server is on the same computer as the PPTP/VPN server, and you attempt to connect to a computer using a PPTP/VPN client, you may experience following problem: 1) The NetBIOS name of the computer to which you are attempting to connect is not resolved. 2) You may receive an error message similar to the following error message: "System error 53 has occurred. The network path was not found" when using net view or opening Network Knighthood.
2. If the WINS server is not on the same computer as the PPTP server and you attempt to connect to a computer using a PPTP client, you may be able to connect to computers on your local area network (LAN), but you may be unable to connect to network shares or resources on the PPTP server.
Resolutions: Inability to browse often means the client can't resolve NetBIOS names.
1. If this is a workgroup network, enable NetBIOS over TCP/IP on the server and clients.
2. If this is domain network and the WINS server is on the same computer as the PPTP/VPN server, move the WINS server to a different computer.
3. Add the NetBEUI protocol for your PPTP tunnel instead of, or in addition to, TCP/IP.
4. By default, most routers and firewalls prevent the transmission of NetBIOS names unless you enable UDP ports 137 and 138 and TCP port 139. Try to enable UDP ports 137 and 138 and TCP port 139 across all routers and firewalls between the PPTP/VPN client and PPTP/VPN server.
5. Make sure the client has correct DNS, WINS and Master Browser settings.
6. Make sure the default gateway points to the remote network rather than to the ISP.
7. Some ISP might block ports required for NetBIOS name broadcasts.
8. If WINS address is not distributed upon connection to VPN, LMHOSTS should be configured to enable Domain to be located.
9. If you try these techniques and the client still can't browse, try to use UNC to connect to the remote LAN, for example, use the net use h: \\servername\sharename command.

For more tips or information, go to

http://www25.brinkster.com/ChicagoTech

Robert Lin, MS-MVP, MCSE & CNE
Windows, Network and How to at

http://www25.brinkster.com/ChicagoTech

 

[Sholeh]

I don't have a PPTP/Server running on a computer. I assume this is all being handled by the VPN router. So I don't believe most of this is applicable, right? I don't have any control over these settings within my VPN router.

1. Yes, and this setting is already acitve.
2. No, there is no domain on the network.
3. Can this be done for the router?
4. I believe this is ok, because I can see one of the computers.
5. If I change these settings on the client end, I will not be able to get access outside of the LAN because the DNS has to be set to what the router uses for the DNS.
6. How and will I be able to browse the internet if I change this?
7. OK
8. Not sure if this is necessary.
9. I've tried this and it doesn't work either.

Thanks,
Doug

 

[markku]

Hi Sholeh,

Sentinel/BEFVP41 combo does not support Netbios broadcasts, hence the remote computers should not be visible in network neighbourhood.

You should use \\remo.te.LAN.IP\shared_resource to connect.

Please check for any firewall programs in non-pinging machine and remove ( not disable ) them. IPSec passthru should be enabled in Linksys routers.