VPN L2TP connection problems since last week

M

MobileAllOver

Well-Known Member
Joined
Jan 11, 2006
Messages
402
Reaction score
0
Location
Pretoria
I've been using VPN L2TP for the past few months and had absolutely no problems at all.

I started off with normal PPTP connections running on the 'internetVPN' APN to ensure that connection works for more than 3 minutes. (Issues with GRE protocol etc)

Migrated to L2TP with certificates, L2TP etc running on UDP ports 500 and 4500.

Anyone with the same issue / problem? Connections works 100% on normal DSL connection.
 
MobileAllOver said:
I've been using VPN L2TP for the past few months and had absolutely no problems at all.

I started off with normal PPTP connections running on the 'internetVPN' APN to ensure that connection works for more than 3 minutes. (Issues with GRE protocol etc)

Migrated to L2TP with certificates, L2TP etc running on UDP ports 500 and 4500.

Anyone with the same issue / problem? Connections works 100% on normal DSL connection.
Click to expand...

We did have a problem with VPN ports last week Thursday but I'm told that was resolved then.

If you're still seeing the problem, please PM me as much info as you can + your contact details and we'll look into it.
 
I'll do some tests this side, will let you know... Just tested with my own connection again, everything worked 100% My colleague is still having the problem, will investigate...
 
Hi 3g... Having the same problem again, will PM you all relevant details.

Currently in Midrand @ Bytes...
 
Please check you PM 3g....

Based on my network experience I think it has to do with the 196.x.x.x vs 41.x.x.x IP allocations...

MOB
 
Might be the IS backbone, but I doubt it.

When I try to connect to my Server @ Home (changeip address), it also doesn't work.
Neither VPN / RDP / SSH works...... Nothing.

But it does work via my
1. DSL connection
2. MTN TyTn connection
3. From my hosted server @ ISP
 
Thanks to Peet and Jannie from Vodacom - problem resolved.

Had to do with IS's local routes ; my firewall only accepted traffic from IPs within South Africa and considered some of the 41.x.x.x as international IPs seeing that these allocations were fairly new.
 
MobileAllOver said:
Thanks to Peet and Jannie from Vodacom - problem resolved.

Had to do with IS's local routes ; my firewall only accepted traffic from IPs within South Africa and considered some of the 41.x.x.x as international IPs seeing that these allocations were fairly new.
Click to expand...

Before we activated the new IP's, we informed all the ISP's about them so they could get their routing sorted.

And, best of all, they confirmed they did it. :confused:
 
Just to clarify - it was the local routes on my own firewall, I've performed a manual update from the public-route-server.is.co.za ...
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X