home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.dcom.vpn      VPN protocols, clients, awesomeness      2,348 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 1,463 of 2,348   
   Mike Drechsler - SPAM PROTECTED EMA to Chuck Bridgeland   
   Re: Netgear FVS318 and ProSafe Client se   
   31 Jan 05 18:34:33   
   
   From: mike-newsgroup@-DELETETHISPART-.upcraft.com   
      
   Chuck Bridgeland wrote:   
   > On 26 Oct 2004 07:55:24 -0700, Sean Rumelhart  wrote:   
   >   
   >   
   >>"Matt Shepherd"  wrote in message   
   news:...   
   >>   
   >>>I'm e-mailing Eric a working config for our FVS318 client/router   
   >>>relationship (without any sensitive information enclosed, obviously) ...   
   >>>- Matt   
   >>   
   >>Could you email me the same setup? I am also having a problem with the   
   >>Prosafe VPN client to an FVL328. I can establish a connection, but   
   >>cannot "see" any of the computers on the domain that is behind the   
   >>FVL328.   
   >>   
   >>Thanks in advance for any assistance,   
   >>   
   >>Sean   
   >   
   >   
   > Months later: Me too, me too, por favor.   
   >   
   > The Netgear docs seem to assume that if you can ping across the tunnel,   
   > everything's OK.  I can ping, but only by ip, not name.   
   >   
   > I set up a WINS server on the far end.  No help.  The best I can do is to   
   > make an lmhosts file explicitly setting the address of the two servers that   
   > need to be accessed, after which I can ping my name, map drives by name,   
   > etc.  The computers that will have the client software are laptops that are   
   > in and out of the office, so I don't think there will be a problem with   
   > doing it this way, but I'd like to get it to work right.  I still can't   
   > properly log into the domain either.   
   >   
   > Any help would be appreciated.   
      
   Indeed name resolution has nothing to do with VPN.  If your name   
   resolution is not working then let us know what DNS and WINS servers the   
   client obtains when connecting through VPN.  (use the ipconfig /all   
   command in windows 2000/XP)   
      
   If it does not obtain a server address then you simply must have the   
   DHCP server that gave the client it's address also give them the correct   
     DNS/WINS servers address also.  This should fix your domain log-in.   
      
   --   
   WARNING!  Email address has been altered for spam resistance.   
   Please remove the -deletethispart-. section before replying directly.   
   Mike Drechsler (mike-newsgroup@-deletethispart-.upcraft.com)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca