Reply
Highlighted
Tutor

Remote IP Subnet is same as LAN IP Subnet traffic won't route

Local Office LAN IP Subnet is 192.168.1.0

Remote Home LAN IP Subnet is 192.168.1.0

VPN Client connects but nothing routes.  I beleive this is because both LANs are on the same subnet.  Is there any way to configure the Remote Client Setup to allow this to work or do I have to put the Remote User's LAN on a different Subnet.

BTW: that is what I did to fix it on one client but I have many home users with Routers that default to use the 192.168.1.0 subnet.

Yes: Shame on me for leaving my office LAN on the default Subnet of 192.168.1.0.

 

Thank you in advance for any suggestions.

 

Mike

Model: SRXN3205|ProSafe Wireless-N VPN Firewall
Message 1 of 2

Accepted Solutions
Highlighted
NETGEAR Moderator

Re: Remote IP Subnet is same as LAN IP Subnet traffic won't route

@Augello,

 

The only solution here is to change the LAN IP Subnet to a different IP address range.  It is either you change the IP address range of the Local Office LAN IP Subnet or Remote Home LAN IP Subnet 

 

 

Regards,

 

DaneA

NETGEAR Community Team

View solution in original post

Message 2 of 2

All Replies
Highlighted
NETGEAR Moderator

Re: Remote IP Subnet is same as LAN IP Subnet traffic won't route

@Augello,

 

The only solution here is to change the LAN IP Subnet to a different IP address range.  It is either you change the IP address range of the Local Office LAN IP Subnet or Remote Home LAN IP Subnet 

 

 

Regards,

 

DaneA

NETGEAR Community Team

View solution in original post

Message 2 of 2
Top Contributors
Discussion stats
  • 1 reply
  • 677 views
  • 0 kudos
  • 2 in conversation
Announcements