Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Attention: The Community will be in read-only mode on 12/14/2017 from 12:00 am pacific to 11:30 am.

During this time you will only be able to see content. Other interactions such as posting, replying to questions, or marking content as helpful will be disabled for few hours.

We apologize for the inconvenience while we perform important updates to the Community.

New Member

RV180W site-to-site vpn tunnel connected, no lan access

I have configured two RV180's with an ipsec vpn tunnel using the "Quick strart:  Configure Site to Site VPN", the connection is established OK.

I cannot ping or otherwise access any host from either end.  Each end can ping the other's LAN gateway, but not beyond.  I can ping 10.0.0.1 but not 10.0.0.100 (a remote host ip)

I cannot see ay windows shares either (do I need a rule to allow netbios through 137,138/UDP, 139/TCP?).

What do I need to complete the connection?  I figured using the vpn "quick-start wizard" would set up all appropriate FW rules and default routes, but it appears thats not the case?

This VPN Tunnel will Connect to the Following Peers:     Gateway

Connection Name and Remote IP Type

  New Connection Name: vpn

  Pre-Shared Key:      presharedkey

Endpoint Information:

  Remote Gateway Type:     IP Address

  Remote WANs IP Address / FQDN:  WAN.address.of.remote_rv180

  Local Gateway Type:     IP Address

  Local WANs IP Address / FQDN:   WAN.address.of.local_rv180

Secure Connection Remote Accessibility

  Remote LAN (Local Network) IP Address:     10.0.0.0

  Remote LAN (Local Network) Subnet Mask: 255.255.255.0

  Local LAN (Local Network) IP Address:     192.168.1.0

  Local LAN (Local Network) Subnet Mask:     255.255.255.0

Selection_001.pngSelection_002.png

2 REPLIES
Silver

RV180W site-to-site vpn tunnel connected, no lan access

Hello Larry,

Since you can ping both routers the tunnel is up and running correctly.  Usually when you cannot ping a host it is because of the Windows firewall, or some other kind of security software, blocking the ping.  You can try disabling the Windows Firewall temporarily to see if you can ping then.  If that works you can add a rule to the firewall to allow pings in permanently.

As for the Windows shares, you won't be able to browse for them, but you should be able to access them by opening a Windows Explorer window (like when looking at a folder) and typing /// in the address bar.

Since the two ends are in different subnets Windows won't broadcast this information out, but you will be able to access it directly using the above method.

Let me know if that works for you,

Christopher Ebert

---

Network Support Engineer - Cisco Small Business Support Center

New Member

RV180W site-to-site vpn tunnel connected, no lan access

I cannot connect to any known shares by IP.  I have tried to add a static route, but this system won't allow it (I added a route through the WAN IP).

The other sites' router allowed me to add a static route through the WAN address:

643
Views
0
Helpful
2
Replies
CreatePlease to create content