VPN Issues

Dangerous · 18 Apr 2006 at 12:29

Does anyone know of any issues why a VPN connection would be live for 60s then drop for another 60s and then return?

It doesnt fully drops the connection just times out to the server?

Skilldibop · 18 Apr 2006 at 13:05

Sounds like your either getting a lot of packet loss or your client is crap.

I'd have a mosey in your router stats and see what your CRC errors are like.

Another avenue of investigation would be helped by knowing which firewall your trying to connect to.

Dangerous · 18 Apr 2006 at 13:08

ISbox 6000 or something like that. Forgot to add this is only when connected via wired link into a router; GRPS connects fine.

just_grass · 18 Apr 2006 at 13:09

wouldn't be vpn dhcp lease time set wrongly?

just an idea. is it exactly 60 seconds every time?

Alex

Dangerous · 18 Apr 2006 at 13:10

Yep to the second.

60s fine
60s full packet loss
60s fine etc

just_grass · 18 Apr 2006 at 13:12

what are you connecting over? the internet?

lan / wan?

any details? - isp? has it changed recently? - VPN ever worked at all?

Alex

Dangerous · 18 Apr 2006 at 13:15

Connecting via ADSL with eclipse (moved from AOL as they didnt support it)

Same issue with AOL though.

Skilldibop · 18 Apr 2006 at 13:17

ISbox 6000 or something like that. Forgot to add this is only when connected via wired link into a router; GRPS connects fine.

Sounds like a router/line issue. And i think you mean GPRS

Ground penetrating radar system

like all mobile phones use.

wouldn't be vpn dhcp lease time set wrongly?

just an idea. is it exactly 60 seconds every time?

nope cos then it would do the same on GPRS too, and it doesn't. It could however be local DHCP. This is also required as VPN is useless without internet, would also tie in with the VPN not completely dropping as your probably getting the nea address within the VPN timeout period which is probably about 90 seconds.

just_grass · 18 Apr 2006 at 13:18

do you know by any chance if an ISA firewall is being used either at your end or at the server end?

Alex

Skilldibop · 18 Apr 2006 at 13:20

just_grass said:
do you know by any chance if an ISA firewall is being used either at your end or at the server end?

Alex

again, if it was at the remote end then it would have the same effect on GPRS.

And i doubt he has an ISA firewall on home ADSL tbh.

just_grass · 18 Apr 2006 at 13:21

Skilldibop said:
again, if it was at the remote end then it would have the same effect on GPRS.

And i doubt he has an ISA firewall on home ADSL tbh.

Okay yea i just missed your last post when i clicked submit.... :rolleyes:

but he may have something relating to ISA firewall at home - i don't know :confused:

but i came across this: http://support.microsoft.com/default.aspx?scid=kb;en-us;831531

slight coincidence.
Alex

Dangerous · 18 Apr 2006 at 13:22

Skilldibop said:
Sounds like a router/line issue. And i think you mean GPRS Ground penetrating radar system like all mobile phones use.

nope cos then it would do the same on GPRS too, and it doesn't. It could however be local DHCP. This is also required as VPN is useless without internet, would also tie in with the VPN not completely dropping as your probably getting the nea address within the VPN timeout period which is probably about 90 seconds.

aye 3G GPRS

The firewall is WatchGuard Firebox 700 that is managed by 3rd party but other users connect fine just this one user.

just_grass · 18 Apr 2006 at 13:23

Dangerous said:
aye 3G GPRS

The firewall is WatchGuard Firebox 700 that is managed by 3rd party but other users connect fine just this one user.

would this 3rd party have anything to do with an ISA firewall?

also... do you use PPTP or L2TP for VPN?

Alex

Skilldibop · 18 Apr 2006 at 13:28

The firewall is WatchGuard Firebox 700 that is managed by 3rd party

This man he plays with fire.

Some line stats, CRC from the remote router would be very useful, also maybe a screenie of the local DHCP config.

have a go from there i'd say.

Dangerous · 18 Apr 2006 at 13:28

Well its a fixed box so I doubt it has anything MS on there.

PPTP I think

just_grass · 18 Apr 2006 at 13:50

just learnt something.....

PPTP requires a Keep-alive packet to be sent... yea okay....

But at this microsoft site it says - EVERY 60 SECONDS default.

give google a search "pptp keep alive packet" - throws some info up about it all.

Alex

edit:
perhaps some are not being recieved or even sent and the server times out the connection before they are sent (and the client then silently reconnects?)

maybe changing this on the client could solve the problem? - or change the time before it drops out.

Dangerous · 18 Apr 2006 at 13:57

just_grass said:
just learnt something.....

PPTP requires a Keep-alive packet to be sent... yea okay....

But at this microsoft site it says - EVERY 60 SECONDS default.

give google a search "pptp keep alive packet" - throws some info up about it all.

Alex

edit:
perhaps some are not being recieved or even sent and the server times out the connection before they are sent (and the client then silently reconnects?)

maybe changing this on the client could solve the problem? - or change the time before it drops out.

Thats for NT this is 2000 Pro SP4

just_grass · 18 Apr 2006 at 14:02

Dangerous said:
Thats for NT this is 2000 Pro SP4

But isn't 2000 pro/server/whatever built on NT... i think so.

Surely its worth a shot.

Alex

Dangerous · 18 Apr 2006 at 14:05

just_grass said:
But isn't 2000 pro/server/whatever built on NT... i think so.

Surely its worth a shot.

Alex

One of the register values isnt in there so guess not.

Skilldibop · 18 Apr 2006 at 14:07

NT and 2000 networking wise are nion the same. XP is a big step up, as is server 2003.