This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unable to access remote LAN

I'm connecting via SSL, and I can't connect to a remote computer, say at 192.168.1.56. The network I'm currently connect to is also 192.168.1.x, so I'm guessing this might be interfering. Is this the case? Other than changing my remote LAN to something other than 192.168.1.x, is there a way around this? Thanks!

This thread was automatically locked due to age.

Parents

0 Scott_Klassen over 10 years ago

It's best practice never to use 192.168.1.x or 192.168.0.x, as every router manufacturer uses one or the other as default. As you've found, this can create painful remote access issues.

Your basically looking at doing something like: How to tunnel between two UTMs which use the same LAN network range. Although the kb article is for site-to-site, the same thought process of using "fake" IPs and converting would apply.

You best bet really is to re-address one of the networks.

__________________
ACE v8/SCA v9.3

...still have a v5 install disk in a box somewhere.

http://xkcd.com
http://www.tedgoff.com/mb
http://www.projectcartoon.com/cartoon/1
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Scott_Klassen over 10 years ago

It's best practice never to use 192.168.1.x or 192.168.0.x, as every router manufacturer uses one or the other as default. As you've found, this can create painful remote access issues.

Your basically looking at doing something like: How to tunnel between two UTMs which use the same LAN network range. Although the kb article is for site-to-site, the same thought process of using "fake" IPs and converting would apply.

You best bet really is to re-address one of the networks.

__________________
ACE v8/SCA v9.3

...still have a v5 install disk in a box somewhere.

http://xkcd.com
http://www.tedgoff.com/mb
http://www.projectcartoon.com/cartoon/1
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data