VPN Connection Linksys BEFW11S4

[rapidr]

Hi,

I have two routers that are the typical wireless Linksys BEFW11s4 models. Both are setup for VPN traffic with IPSEC Enabled and the proper ports/triguring ports configured as per Linksys' web site.

We have 1 2000 Server accepting VPN calls and 1 Workstation on the other end of the cloud connection. The connection works fine, however the workstation is unable to PING the server and we are unable to map drivers.

I have tried the following:
- Put both the server and workstation on the DMZ, no luck.
- Tried this same action with another ISP to ensure that ports aren't being blocked by the ISP themselves.

Finally this is the resolution to my problem:

Remove the router entirely from the workstation side of the cloud. ***** Everything now works perfectly!

Who needs a router or a firewall anyway????

Does anyone have any ideas on why both Linksys Routers with the same configuration doesn't work properly with a VPN connection? Is this Linksys' idea of forcing you to purchase their vpn router?

Thanks again for any ideas on how to get this to work through the router is apreciated.

 

[ChicagoTechNet]

assuming the router doesn't block the ping, what's the error when trying to connect the VPN?


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

 

[rapidr]

The VPN will connect fine with no errors appearing.

When we try to ping the server using the server's name or ip addrses, we receive:

Requst timed out.

Thanks!

 

[ChicagoTechNet]

quoted from

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 resources by ip, for example, use the net use h: \\serverip\sharename command.


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

http://www25.brinkster.com/ChicagoTech