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 524 of 2,348   
   JW to Helpful   
   Re: PPTP from client through Linksys WRT   
   24 Nov 03 00:57:22   
   
   From: TheTenorXYZ@attXYZ.net   
      
   It's the latest firmware.   
      
   "Helpful"  wrote in message   
   news:Zy6dnU0lL5RTuVyiXTWc9g@ptd.net...   
   > Perhaps its time to reflash the firmware?   
   >   
   > "JW"  wrote in message   
   > news:Vk6wb.215348$9E1.1152969@attbi_s52...   
   > > Like I said, I've had this working for a couple of years using the old   
   > > Linksys router.  I've long ago taken care of all those issues (different   
   > > subnets, etc). It just fails to authenticate with the new router. And   
   > > Linksys is certainly quick to respond to an e-mail to their support   
   > address,   
   > > but they just keep giving me garbage. They are even telling me to   
   forward   
   > > "Port" 47 - which won't help at all since there is no "Port" 47 involved   
   > in   
   > > PPTP (it's "Protocol" 47). Additionally they're telling me to forward   
   port   
   > > 500 which is used by ipsec... not PPTP.   
   > >   
   > > They (Linksys) did give me a phone number to call so I'll try that   
   > tomorrow,   
   > > but I don't hold out much hope given how little their support people   
   know.   
   > > They are just reading from a script it seems.   
   > >   
   > > Wes   
   > >   
   > >  wrote in message   
   > > news:leXvb.31006$kL2.9924@fe3.columbus.rr.com...   
   > > > JW wrote:   
   > > >   
   > > > > This has been working flawlessly until I connected my new WRT54G   
   here   
   > at   
   > > > > home. Now it makes the initial connection with the server and then   
   > hangs   
   > > at   
   > > > > "Verifying Username and Password" until it times out with error 628   
   > > > > (terminated by remote computer).   
   > > >   
   > > > Make sure the subnet of the LAN address on the local router is   
   different   
   > > > than the remote router LAN address.  For example, if the office router   
   > > > has a LAN address of 192.168.0.1, make sure your home router LAN   
   address   
   > > > is something like 192.168.1.1.   
   > > >   
   > >   
   > >   
   >   
      
   --- 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