From: dave-thorn@nodash.verizon.net.invalid   
      
    wrote in message   
   news:u5mzb.5543$tu1.3295@fe3.columbus.rr.com...   
   > Dave Thornburgh wrote:   
   > > -Router uses DHCP to get an address from Verizon, and serves DHCP to the   
   LAN   
   > > with 192.168.2/24.   
   >   
   > Why did you choose 192.168.2.x?  Make sure that the office router is not   
   > also 192.168.2.x.  Otherwise, you'll have duplicated LAN IPs.  Or just   
   > take the plunge and try 192.168.3.whatever on your home router -- it's a   
   > quick change (and reboot).  Up until two weeks ago I was also using a   
   > BEFSR41 with similar settings.  However, I didn't need IPSec passthrough   
   > because our VPN is PPTP.   
      
   Long story short, I chose .2 before I got the DSL, since I had heard that   
   Verizon used modems with a built-in router (Westell 2200) which uses .1 for   
   the LAN side.  Alas, that wasn't the modem I got, so it never became an   
   issue.  At work, everything is 10.n.n.n   
      
   Also, some things do work fine while the router is connected - if it were an   
   addressing conflict, I would think even pings would fail.   
      
   My best guess is that my problem is something peculiar to the CheckPoint   
   client that isn't getting through the NAT properly.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)