From: one@atime.com   
      
   Hi Bob:   
      
   you're using Netscreen remote s/w client, but what model is the   
   workplace firewal? I assume you're using IPSEC as your tunnelling   
   protocol?   
      
   Hmmm...If you can connect to the remote firewall, but can't connect to   
   the internal servers, then I wonder if the proper ports are being   
   forwarded beyond the firewall for you to connect to the servers etc.   
      
   When you say you can't connect to the servers or your mailbox, what   
   method/technology are you using to do so? Is this a Microsoft network   
   behind the firewall? Are you trying to connect via machine names?   
   IP Adddresses? Mapped drives?  What are the error messages you get?   
      
   Are you sure the pass-through in your home gateway is IETF standard   
   IPSEC?   
      
   If all else fails, your office firewalls should keep logs of   
   connection events. Have the IT technicians told you what those are   
   indicating?   
      
   Have you tried connecting without your gateway (with an   
   antivirus and software firewall) ?   
      
   Maybe it's just me, but I fail to see how upgrading to a static IP   
   would make any diff. whatsoever. If you are authenticaing to the   
   firwall, you have permissions to enter, you just are having trouble   
   seeing what's behind the door.   
      
      
   Dave   
      
   On 17 May 2004 04:53:56 -0700, bob101@mailinator.com (bob101) wrote:   
      
   >I'm at home trying to connect to my workplace VPN through an Actiontec   
   >DSL Gateway, and am having no luck.   
   >I'm running XP Pro, and on my machine my IT dept have installed   
   >NetScreen Remote software which has to be activated before I can get   
   >into the VPN. It all worked fine via dial-up, BTW. Then I get DSL and   
   >the Actiontec router, and it's no soap.   
   >I've talked to the Actiontec tech support people, and we've tried   
   >various different settings on the router, but still no good. VPN   
   >passthrough is enabled, ports have been forwarded, it still doesn't   
   >work, so they tell me the problem is with the VPN I'm trying o connect   
   >to. One clue is, I can connect to the workplace firewall OK and   
   >authenticate myself, but not to the servers or my mailbox.   
   >When I talk to my IT dept, they tell me the problem is with the   
   >router: either I should upgrade to a static IP address from my ISP, or   
   >I should disable NAT. On this router NAT can only be disabled if you   
   >add a static routing address, and the Actiontec support people won't   
   >even tell me how do do this - I don't know what a static routing   
   >address is, and when I've tried my best I couldn't connect to the   
   >internet at all - (legal problems if their firewall is down and I get   
   >hacked?).   
   >   
   >So I'm stuck, back with my crappy dialup.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)