[akmerc]

Here is my configuration:
SonicWall NS240 currently has VPN setup that works.
Main Site allows communication from Remote Site via VPN to Windows Server
Main Site also has a secondary subnet that communicates ONLY through internet but NOT to the Windows Server.

Sonicwall 192.168.168.x is main site
Remote Site is 192.168.0.x connecting to Main Site to access shared folders on server
Secondary subnet at Main Site is 192.168.0.x using Windows XP PC's. They are accessing a linux server at 192.168.0.215 which Main Site has no access to.

VPN remote ip's are 192.168.0.x - they can successfully access the Windows Server at 192.168.168.100 BUT NOT 192.168.0.215.

GOAL: Want to connect Remote Site to Secondary subnet

Willing to make router changes or whatever is necessary to get Remote Site to access Secondary Subnet with the only exception that the Secondary Subnet REMAINS.

VPN DHCP is turned off but willing to turn it on.
Willing to make the Linux Server 'discoverable' on the Windows Server. Don't know linux at all but another co-worker helped set it up and can make changes.

Any suggestions?

 

[Wand3r3r]

Re: Access secondary subnet from remote location

"VPN remote ip's are 192.168.0.x - they can successfully access the Windows Server at 192.168.168.100 BUT NOT 192.168.0.215."

Doesn't appear you need any changes except to allow access rights to the server. The vpn ips are in the same subnet as the linux server.

 

[akmerc]

Re: Access secondary subnet from remote location

The router at 192.168.0.254 does not allow discoverability. Are their certain ports that can be opened that can allow discoverability?

 

[Wand3r3r]

Re: Access secondary subnet from remote location

I see now. You have the same subnet at each site.

Didn't anyone ever tell you can't do that with routing?
How is the router to know which lan to send to when on each interface it has the same distination subnet listed?

You need to change one subnet to something else so they don't match like 192.168.1.x

 

[akmerc]

Re: Access secondary subnet from remote location

Since port 80 is the only port open on both subnets, I have routed traffic to use port 80 to communicate with the added check of a encryption key to start and end each packet.

It's a little slow but it works.

Also: A different encryption key is generated daily (16 bit so that it doesn't lag too much).

Problem solved.