http://www.dslreports.com/forum/r20949613 en Wed, 11 Nov 2009 13:59:46 EDT Wed, 11 Nov 2009 13:59:46 EDT http://www.dslreports.com/forum/remark,21009520 fox7 : Doc:
Why do they do that?? Don't they think we would like to know what the solution was??

fox7]]> http://www.dslreports.com/forum/remark,21009520 Tue, 26 Aug 2008 13:36:20 EDT http://www.dslreports.com/forum/remark,20988255 DocLarge : Nice!

What was the solution?]]> http://www.dslreports.com/forum/remark,20988255 Thu, 21 Aug 2008 23:33:33 EDT http://www.dslreports.com/forum/remark,20987564 Trinijoy : I figured it out. Thank you for all your help!]]> http://www.dslreports.com/forum/remark,20987564 Thu, 21 Aug 2008 21:26:22 EDT http://www.dslreports.com/forum/remark,20986638 DocLarge : In case the issue points to dhcp lease time, try either increasing the dhcp lease, or issue static ip addresses (as a test) if your environment isn't too expansive.]]> http://www.dslreports.com/forum/remark,20986638 Thu, 21 Aug 2008 18:07:09 EDT http://www.dslreports.com/forum/remark,20954088 rjs1003 : OK, if all of your VPNs go down together I can now see why you're looking at the server!
Keep-alive would be for individual tunnels so I wouldn't expect that to help you here.

Mark910 may well have a good point...
I take it the server is on a static address... is it serving DHCP addresses to the whole LAN or just the VPN? As mark said, making sure those leases are long enough may well help.

I guess the other thing to look at is what processes you might have on the server which run every 2 hours... maybe your software firewall cleans itself up, or you have some sort of cron or at job for some other purpose which is messing with your network for some reason.

Bob]]> http://www.dslreports.com/forum/remark,20954088 Fri, 15 Aug 2008 04:43:06 EDT http://www.dslreports.com/forum/remark,20950033 Mark910 : The one thing I would suggest to check is the DHCP server lease timing for individual IP addresses. It may not be set long enough. This may be affecting the other computers too but since they aren't in a VPN connection they may not notice the drop.
--
"Don't worry that children never listen to you. Worry that they're always watching you."
GO »Team Discovery HELP find the CURE!]]> http://www.dslreports.com/forum/remark,20950033 Thu, 14 Aug 2008 11:59:24 EDT http://www.dslreports.com/forum/remark,20949925 Trinijoy : No everyone drops in the VPN (We have three USERS at only one given time.) We all drop at the same time.

What could I check in my settings, that possibly could be happening? You mentioned something like keep-alives. Where do I check that?

Even if I login 30 minutes later, if in 30 minutes the 2 hours happens we will both gets disconnected. It doesn't matter when someone logs in, it matters how long whatever is disconnecting has been up and whenever we fall into that 2 hour mark we get disconnected. For instance I can VPN in 2 minutes before 2 hours, and in 2 minutes hits it kicked it off. Then resets whatever timer is existing for this.]]> http://www.dslreports.com/forum/remark,20949925 Thu, 14 Aug 2008 11:38:50 EDT http://www.dslreports.com/forum/remark,20949796 rjs1003 : I don't think you've ruled out the router necessarily, because the VPN connection is passing through from WAN to LAN of the router (the LAN PCs just go through the LAN side which is just a simple switch, I guess), and it is possible the router times out the NAT mapping on the encrypted packets which is letting this happen. Now this shouldn't happen (providing the VPN is active or keep-alives are enabled) - ie it would be a bug in the router... but from your post I wouldn't rule it out.

Is this VPN using L2TP/IPSec or PPTP, by the way?

I guess you could confirm whether the VPN server's NIC is having a problem simply by pinging some other host on the LAN continuously (ping -t from a DOS prompt) and if it's the NIC then it'll presumably drop pings for a short period. But why would this sync to your VPN tunnel's uptime so well? Doesn't sound particularly likely.

Even if it's not the NIC, it could be the server losing the connection - if something causes it to reload its VPN config, but you wouldn't expect something like this to happen at an interval related to the time a connection has been up.

Perhaps a good test would be to log on from 2 VPN clients (maybe take a laptop home?) a few minutes apart... I bet one continues whilst the other stops... ?

Bob]]> http://www.dslreports.com/forum/remark,20949796 Thu, 14 Aug 2008 11:13:10 EDT http://www.dslreports.com/forum/remark,20949613 Trinijoy : Okay here it goes:

I have a Windows 2003 Server machine with a built in NIC. Then from that Built in NIC I have a WRT54GS Version 7 router, then from that route I have a hooked up a 16 port switch, of which 12 computers are hooked up. And a major Server based system for Purchasing/Manufacturing that sort of thing.

The VPN is configured in 2003. Everything is setup correctly, I have the DHCP server built into 2003 give out the IP address. That works fine.

So A user like me connects to the VPN. Everything work fine, i can access the other network, i get assigned an IP. Everything works DANDY. Then all of a sudden after 2 hours, exactly EVERY SINGLE TIME the VPN disconnects for about 6 seconds, and then i am able to re-connect, and this is a big deal because the Major Server system for our purchasing freaks out when a user disconnects without doing in properly.

Now what I noticed was this, I thought it was the router but it can't be because all of 12 computers at the other network would get kicked off the Purchasing system. They don't and they all stay on the WEB. So the route is not losing Internet, or the internal network connection.

Now is it me? no, because I have actually tested this on a different computer on a different network (my home actually) and it gets disconnected in the same amount of time.

I think it's the actual COMPUTER losing the connection. I think I have narrowed it down to the NIC card losing connection for a few seconds, is this possible? It's not the router, because the computer does this whether it's direct in the router, or in the switch. If it was the cable, it wouldn't connect at all, if I am correct.

So can someone help me and tell me what exactly is going on? ]]> http://www.dslreports.com/forum/remark,20949613 Thu, 14 Aug 2008 10:37:49 EDT