RE: [SonicWALL]- Routing Problem

[Craig Fialkowski]

Title: Message

John,   Thanks for the reply. The 192.168.2.10 is a node on the Remote side. I believe you are correct in your methodology.   It seems the Default Gateway for the Local Network should be the Ethernet of the 1720 on that side.  In this scenario, that would be 192.168.1.2 I can access the Internet from a local Node using the above config.  I seems the problem is likely with the routing on the Local 1720 Router.   On the Sonicwall I set up the static route in the Advance/Routes tab   I used the following string  192.168.2.0 255.255.255.0 192.168.1.2                                        remote net   subnet             local 1720 Ethernet   Craig -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of John Wesselman Sent: Friday, November 01, 2002 1:45 AM To: [EMAIL PROTECTED] Subject: Re: [SonicWALL]- Routing Problem Craig,   What is the gateway IP of 192.168.2.10?  I am not a Cisco guy, but in a config I did for a customer, they are doing this very thing and the gateway of the remote LAN PCs is the router on that side.  Then they set their routing tables in the Cisco to know that Internet traffic goes to the other router, which passes Internet traffic to the Sonicwall.  Along this line, all of the PCs on the local LAN side gateway through their Cisco as well.  I am not sure if this suggestion will work for you without reworking your Cisco a little, but I know it can be done.   Also, when you set up the static routes, did you do that on the General/Network tab under the NAT config, or did you do it in the Advanced/Routes tab...or both?   Hope this helps.   John Wesselman Assured Network Security, LLC 200 Distillery Commons, Suite 410 Louisville, KY 40206-1990 (502) 719-9526 - voice (502) 802-5898 - mobile (502) 719-9569 - fax http://www.assurednet.net [EMAIL PROTECTED] ----- Original Message ----- From: Craig Fialkowski To: [EMAIL PROTECTED] Sent: Thursday, October 31, 2002 11:38 PM Subject: [SonicWALL]- Routing Problem I am trying to route Internet traffic to a remote LAN over a t1 connection.   Remote LAN --> CISCO1720 ---> T1 ---> CISCO1720  ----> Local Network----> Sonicwall SOHO/3 NAT --->DSL Router Public 192.168.2.10     192.168.2.1                   192.168.1.2          192.168.1.3           192.168.1.1   Local Network: Sonicwall LAN: 192.168.1.1 Local 1720 E0: 192.168.1.2 Nodes: 192.168.1.3 - 192.168.1.5   Remote Network: Remote1720 E0: 192.168.2.1 Node: 192.168.2.10   I can access all resources of the local LAN from the remote accept the Internet.  Trace Route from Remote to any Public address drops at the SONICWALL 192.168.1.1 address.   I can access Public IP addresses from the Local CISCO1720 with no problem.    It seems the Sonicwall has no clue about the 192.168.2.x network. Is the SONICWALL able to route requests from the Remote Network to the Internet and Back? Does there have to be a Static Route added to the Sonicwall?  I added 192.168.2.0 255.255.255.0 192.168.1.2 but no luck.   Help is greatly appreciated.   Craig   ---   Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.408 / Virus Database: 230 - Release Date: 10/25/2002