Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

Adding a static route for a VPN tunnel

Jan 7, 2014 3:04PM PST

Hello everyone!



I have this strange problem, will try to describe



I have configured a VPN connection to my office. VPN is established, but whey I try to use different services, I get an error saying that the server have not been found (specifically, the server name can not be resolved). I have checked the "Tunnel all traffic through the VPN" option, but it did not help.



I think the reason is that my home network subnet is the same as my office, where the server is located (192.168.1.0). I know it sometimes can be an issue with Windows OS. Unfortunatelly, I can not change my home subnet. I thought may be a static route to the server will do the trick, but I am not sure.



Will a static route to the server. for example 192.168.1.2/32 point to VPN server will resolve my issue and what is really causing the problem, is it really my overlapping subnets?



Thank you!

Discussion is locked

- Collapse -
Answer
I'll write no.
Jan 7, 2014 3:12PM PST

A proper VPN works as if you are plugged into the other LAN. Your local lan should be inaccessible and not an issue.
Bob

- Collapse -
reply
Jan 7, 2014 7:15PM PST

The thing is that once the VPN is connected I can ping any subnet in the office except 192.168.1.0, which I also have configured at home

- Collapse -
192.168.1.0 is not considered a valid IP
Jan 7, 2014 7:29PM PST

That's what they call a broadcast IP and in some LANs you get a reply from everyone on the LAN.

Bob

- Collapse -
reply
Jan 7, 2014 7:51PM PST

Broadcast IP would be 192.168.1.255, but this has nothing to do with my problem.. My server ip is 192.168.1.2 and I can not ping it through vpn, however I can ping any other subnets in the office. Can not only ping 192.168.1.0 subnet, for exampe the server or any computer in 192.168.1.0, say 1.3 or 1.4 or 1.5 etc

- Collapse -
"In general, the first and last addresses in a subnet are
Jan 7, 2014 8:18PM PST

"In general, the first and last addresses in a subnet are used as the network identifier and broadcast address, respectively. All other addresses in the subnet can be assigned to hosts on that subnet."

It appears we have to catch on on what an IP is and what a subnet is. One thing is not the other.
Bob

- Collapse -
reply
Jan 7, 2014 8:21PM PST

Looks like you do not understand what I write..

I ping IP addresses in the 192.168.1.0 subnet, say 192.168.1.2, 192.168.1.3, 192.168.1.4 etc, and I do not get a reply. I do not ping 192.168.1.0, I understand that this is a network identifier, I am a Cisco Networking engineer with CCNP certification..

- Collapse -
I understand it very well.
Jan 7, 2014 8:25PM PST

I wrote router code in the 90s but when folk write "where the server is located (192.168.1.0) " I believe them.

It could be as simple as the NETMASK but many folk decline to share all the details so I can't comment.
Bob

- Collapse -
Typo. I meant catch up.
Jan 7, 2014 8:22PM PST

It's a bit late so I'll check in tomorrow.