SmallNetBuilder Forums
Go Back   SmallNetBuilder Forums > LAN & WAN > Routers

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 11-19-2012, 03:55 AM
Nick Nick is offline
New Member
 
Join Date: Nov 2012
Posts: 2
Thanks: 1
Thanked 0 Times in 0 Posts
Nick is just starting out
Question VPN Client Can't Ping LAN Clients After Replacing LAN Router

Hi, I just replaced my old router (TRENDnet TEW-633GR) with an ASUS RT-N66U. I've copied over all of my settings (port forwarding, static routes, etc) to get the new router set up and running. However, I'm having issues with VPN clients not being able to communicate with LAN clients. I'm using Windows Server 2008 R2 Standard RRAS as the VPN server, and it was working fine until I replaced the router.

First, a few IP addresses on the LAN:
Router: 192.168.1.1
VPN Server: 192.168.1.76 and 192.168.128.2 (Single NIC; this server also handles DHCP, DNS, and file/print sharing.)
VPN Client: 192.168.128.3
LAN Desktop: 192.168.1.50 and 192.168.1.51 (Dual NICs)
LAN Laptop: 192.168.1.204 (or 192.168.1.244 when connected through VPN)

The VPN client (another server running Windows Server 2008 R2 Web edition) is unable to ping anything except the VPN server (either of its IPs work), the router, and any other VPN clients. However, any of the directly-connected LAN clients (such as 192.168.1.50) can ping the VPN client, and it will respond. Even though my desktop and laptop are connected directly to the LAN, if I connect to the VPN server on either of them, I can access the remote VPN client that way. Firewalls and client machine software/configurations should be mostly ruled out since it worked with the old router. Oddly enough, the router and VPN client can ping each other both ways without issue. I am using the stock ASUS firmware that came with the router as well.

Any ideas on what could be causing this?

Thanks!
Reply With Quote
  #2  
Old 11-19-2012, 04:36 AM
Nick Nick is offline
New Member
 
Join Date: Nov 2012
Posts: 2
Thanks: 1
Thanked 0 Times in 0 Posts
Nick is just starting out
Default

Turns out the router's firewall was dropping packets from the VPN clients (possibly because they're on a different subnet or because of how the VPN server adds clients to the network). Oddly enough, nothing was showing up in the firewall logs about it dropping these packets.

Anyhow, I was able to fix it by running iptables -t nat -A POSTROUTING -o br0 -s 192.168.0.0/16 -d 192.168.0.0/16 -j MASQUERADE on the router. (By default, it had 192.168.1.0/24.) I was able to figure this out thanks to lfbb's post regarding a related issue.

Last edited by Nick; 11-19-2012 at 04:46 AM.
Reply With Quote
Reply

Tags
ping, router, routing, vpn

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


All times are GMT -4. The time now is 10:17 PM.


Top 10 Stats
Top Posters* Top Thanked
RMerlin  333
sm00thpapa  224
stevech  186
azazel1024  148
KGB7  134
htismaqe  88
jim769  83
philmiami  77
AcostaJA  69
ColinTaylor  59
RMerlin  5078
stevech  315
ryzhov_al  249
TeHashX  209
RogerSC  187
L&LD  186
joegreat  123
jlake  122
sfx2000  111
sinshiva  111
Most Viewed Threads* Hottest Threads*
Old ASUS RT-N66U...  23596
Old NETGEAR...  12932
Old Switched...  6883
Old 3.0.0.4.376.1...  6724
Old NEW RT-AC68R...  6443
Old ASUS...  5865
Old ASUS RTAC68U...  3468
Old Netgear...  3238
Old N66U daily...  2833
Old ASUS...  2764
Old ASUS RT-N66U...  169
Old NETGEAR...  161
Old Switched...  62
Old NEW RT-AC68R...  56
Old ASUS...  51
Old N66U daily...  47
Old ASUS RTAC68U...  41
Old Netgear...  41
Old Which router...  41
Old TP-Link...  38


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
© 2006-2014 Pudai LLC All Rights Reserved.