-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 craig The sonicwall needs to know that the 192.168.2.X network is available through the local 1720. Without dynamic routing the remote network is unknown to the local network. Thus, the need to create static routes. Once you have done this it should allow internet access for the remote network. This is assuming:
1. the remote 1720 is the default route for clients 2. the remote 1720 has the local 1720 has its default (don't know the type of connection - frmae, etc..) 3. the local 1720 default gateway is the Sonicwall. 4. Sonicwall has a route that says to get to remote lan go to local 1720 Remote-->1720--->1720--->sonicwall-->internet As requested an intro: My name is Jeff Thomas. I work at Nodewarrior Networks in Los Angeles. We are a Sonicwall reseller and training center. -----BEGIN PGP SIGNATURE----- Version: PGP 7.1.1 iQA/AwUBPcLKW2n5SSpQYDJ0EQLPXACeJadOBETx7vyBTfrORw9VlMrFTHMAoI0Y RumvGeP/5ExpmdAjj2E4CqTN =hw3+ -----END PGP SIGNATURE----- --- [This E-mail scanned for viruses by Declude/F-Prot AV] =================================================================================================== To unsubscribe, send email to [EMAIL PROTECTED] In the body of the email put the following: unsubscribe sonicwall your_name The archive of this list is at http://www.mail-archive.com/sonicwall%40peake.com/
