Sonicwall VPN client

[asamol_it]

Hello...Both SonicWall and Linksys can't fix this problem.

The office is behind a SonicWall [SOHO3] router with VPN enabled. The remote
connection is through a Sonicwall global client.

When connecting from a remote site behind a Linksys BEFSR81 Cable/DSL router
nothing on the LAN side of the SonicWall is reachable. Port 500 is open on
the Linksys Router.
Both LAN networks are in the same network...192.168.1.xxx/24. The Win2000
server is DHCP server. And address from the server is received but I am
unable to ping the SonicWall gateway [192.168.1.5] or the DHCP server
[192.168.1.15] this is also the DNS server.

If I remove the Linksys router I am able to ping the GW and the DHCP server.
And reach the resources on the LAN.

If you have any ideas please pass them along.
Alex

MCP Network+ A+

 

[Michael Johnston [MSFT]]

If both LANs are on the same subnet you have a routing problem. If the client is on the 192.168.1.x network and the client VPNs into a 192.168.1.x network, then
the client will not use the VPN connection to route data to the remote network. It will see that it has a local route via the ethernet adapter for the 192.168.1.x
network. Change one of these subnets to something other than 192.168.1.x and this will work.


Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.

 

[asamol_it]

thank you...I was afraid of that...just what I need more things to
configure...

If both LANs are on the same subnet you have a routing problem. If the

client is on the 192.168.1.x network and the client VPNs into a 192.168.1.x
network, then

the client will not use the VPN connection to route data to the remote

network. It will see that it has a local route via the ethernet adapter for
the 192.168.1.x

network. Change one of these subnets to something other than 192.168.1.x and this will work.


Thank you,
Mike Johnston
Microsoft Network Support

rights. Use of included script samples are subject to the terms specified at

http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this

message are best directed to the newsgroup/thread from which they
originated.

 

[Jeff Cochran]

Hello...Both SonicWall and Linksys can't fix this problem.

The office is behind a SonicWall [SOHO3] router with VPN enabled. The remote
connection is through a Sonicwall global client.

When connecting from a remote site behind a Linksys BEFSR81 Cable/DSL router
nothing on the LAN side of the SonicWall is reachable. Port 500 is open on
the Linksys Router.
Both LAN networks are in the same network...

There's your initial problem. If both LAN's use the same networking
scheme (and there's no intervening LAN you're crossing...) then the
communications won't ever get routed. In essence, you've told your
network that it doesn't need to route anything since it's local, even
though it isn't.

192.168.1.xxx/24. The Win2000
server is DHCP server. And address from the server is received but I am
unable to ping the SonicWall gateway [192.168.1.5] or the DHCP server
[192.168.1.15] this is also the DNS server.

If I remove the Linksys router I am able to ping the GW and the DHCP server.
And reach the resources on the LAN.

Sure. The router wouldn't route, since because of your network
numbering it knew it didn't have to.

If you have any ideas please pass them along.

Renumber one or the other network. Put one on 192.168.2.xxx.

You may also run into issues with VPN's and the Linksys, especially
with the cantankerous Sonicwall client. Make sure you have the latest
firmware on the Linksys. If LanWench is hanging out here, I think she
deals with Linksys/Sonicwall configurations on a regular basis, if
not, you might try the win2000.networking group or ping her in the
Exchange groups.

Jeff

 

[asamol_it]

Jeff,
Thanks for the information...I'm going to try changing my home office
network first...this means bring down my whole network, two servers, 6
workstations, two printers, a managed switch, etc.
Thanks again, Alex

Hello...Both SonicWall and Linksys can't fix this problem.

The office is behind a SonicWall [SOHO3] router with VPN enabled. The remote
connection is through a Sonicwall global client.

When connecting from a remote site behind a Linksys BEFSR81 Cable/DSL router
nothing on the LAN side of the SonicWall is reachable. Port 500 is open on
the Linksys Router.
Both LAN networks are in the same network...

There's your initial problem. If both LAN's use the same networking
scheme (and there's no intervening LAN you're crossing...) then the
communications won't ever get routed. In essence, you've told your
network that it doesn't need to route anything since it's local, even
though it isn't.

192.168.1.xxx/24. The Win2000
server is DHCP server. And address from the server is received but I am
unable to ping the SonicWall gateway [192.168.1.5] or the DHCP server
[192.168.1.15] this is also the DNS server.

If I remove the Linksys router I am able to ping the GW and the DHCP server.
And reach the resources on the LAN.

Sure. The router wouldn't route, since because of your network
numbering it knew it didn't have to.

If you have any ideas please pass them along.

Renumber one or the other network. Put one on 192.168.2.xxx.

You may also run into issues with VPN's and the Linksys, especially
with the cantankerous Sonicwall client. Make sure you have the latest
firmware on the Linksys. If LanWench is hanging out here, I think she
deals with Linksys/Sonicwall configurations on a regular basis, if
not, you might try the win2000.networking group or ping her in the
Exchange groups.

Jeff