Author Topic: Netherlands Server Time-Outs.  (Read 8185 times)

Offline Indingo

  • BolehVPN Subscriber
  • Boatswain
  • **
  • Posts: 85
Netherlands Server Time-Outs.
« on: October 28, 2013, 07:58:19 PM »
Hey.

Anyone else been noticing over the past few weeks every now and then the Netherlands based server will time-out for 30 seconds or so and after a few refreshes comes back to normal? I only mention as I doubt its a configuration error as the other servers are fine for me. I was simply wondering if anyone else experienced the same thing?

Thanks.

Offline Chris

  • BolehVPN Staff
  • Admiral
  • *****
  • Posts: 2200
  • Beneath a cobalt moon
Re: Netherlands Server Time-Outs.
« Reply #1 on: October 29, 2013, 02:52:25 PM »
FullyRouted Netherlands? Please post your logs.

When was the last time you updated your configs though?

Offline Indingo

  • BolehVPN Subscriber
  • Boatswain
  • **
  • Posts: 85
Re: Netherlands Server Time-Outs.
« Reply #2 on: October 30, 2013, 12:44:13 PM »
I can post my logs later sure, you mean right after I am connected or after I have the time outs? I only seem to have problems with this one server, and my configs are updated daily on start.

Offline Indingo

  • BolehVPN Subscriber
  • Boatswain
  • **
  • Posts: 85
Re: Netherlands Server Time-Outs.
« Reply #3 on: October 30, 2013, 12:48:29 PM »
Version Server:  2.3.6

Version Current:  2.3.6

Run script:  0

Checking installed tap driver...

ROOT\NET\0000                                               : TAP-Windows Adapter V9
1 matching device(s) found.

Use port 44358 as management port

Wed Oct 30 04:46:15 2013 OpenVPN 2.2.2 i686-pc-mingw32 [SSL] [LZO2] [OBFUSCATION] [PKCS11] built on Mar 12 2013
Wed Oct 30 04:46:15 2013 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables

Wed Oct 30 04:46:15 2013 Control Channel Authentication: using 'C:/Users/User1/AppData/Local/BolehVPN/cfg/OpenVPN/ta.key' as a OpenVPN static key file
Wed Oct 30 04:46:15 2013 LZO compression initialized
Wed Oct 30 04:46:15 2013 UDPv4 link local: [undef]
Wed Oct 30 04:46:15 2013 UDPv4 link remote: 62.212.85.79:443

Wed Oct 30 04:46:18 2013 write UDPv4: No Route to Host (WSAEHOSTUNREACH) (code=10065)

Wed Oct 30 04:46:22 2013 write UDPv4: No Route to Host (WSAEHOSTUNREACH) (code=10065)

Wed Oct 30 04:46:25 2013 [UNDEF] Inactivity timeout (--ping-restart), restarting
Wed Oct 30 04:46:25 2013 SIGUSR1[soft,ping-restart] received, process restarting

Wed Oct 30 04:46:27 2013 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables

Wed Oct 30 04:46:27 2013 Re-using SSL/TLS context
Wed Oct 30 04:46:27 2013 LZO compression initialized
Wed Oct 30 04:46:27 2013 UDPv4 link local: [undef]
Wed Oct 30 04:46:27 2013 UDPv4 link remote: 62.212.85.79:443

Wed Oct 30 04:46:27 2013 [server] Peer Connection Initiated with 62.212.85.79:443

Wed Oct 30 04:46:30 2013 TAP-WIN32 device [TAP-Win32 Adapter V9] opened: \\.\Global\{9C7AFA12-3625-4C14-A590-18CBCF21EE1B}.tap
Wed Oct 30 04:46:30 2013 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.10.10.146/255.255.255.252 on interface {9C7AFA12-3625-4C14-A590-18CBCF21EE1B} [DHCP-serv: 10.10.10.145, lease-time: 31536000]
Wed Oct 30 04:46:30 2013 Successful ARP Flush on interface [19] {9C7AFA12-3625-4C14-A590-18CBCF21EE1B}

OK!

OK!

OK!
Wed Oct 30 04:46:40 2013 WARNING: potential route subnet conflict between local LAN [192.168.0.0/255.255.255.0] and remote VPN [0.0.0.0/0.0.0.0]

OK!

OK!
Wed Oct 30 04:46:40 2013 Initialization Sequence Completed

Run script:  1


(My On Login, Logs)

Let me know if you need anything else, I have only had the problem on this server, and non of the others.

Offline Chris

  • BolehVPN Staff
  • Admiral
  • *****
  • Posts: 2200
  • Beneath a cobalt moon
Re: Netherlands Server Time-Outs.
« Reply #4 on: October 30, 2013, 01:42:59 PM »
Does your internet connection drop out? Are you on wireless? Log shows that it's your connection to the server dropping and so it times out and reconnects.

Do you require the NL server specifically for anything? If not, perhaps another server would serve you just as well?

Offline Indingo

  • BolehVPN Subscriber
  • Boatswain
  • **
  • Posts: 85
Re: Netherlands Server Time-Outs.
« Reply #5 on: October 30, 2013, 01:57:06 PM »
Does your internet connection drop out? Are you on wireless? Log shows that it's your connection to the server dropping and so it times out and reconnects.

Do you require the NL server specifically for anything? If not, perhaps another server would serve you just as well?

I am on wireless yes, but don't have the same problem with any of the other servers just the NL server. My connection is fine, its just this one server that gives me drop-outs. I use the NL server because its ports are closed, the Canada and HK servers are ports closed also "Don't wish to use the UK server". I could use Canada/HK but both are far and slow the connection down. I wish to only use a server with closed ports and not open ones such as the Netherlands server which is geographically close to me and the fastest server for me.I also like that it has "Static" and not "Dynamic IP". I would like to get the issue resolved, I am not sure why supposedly this is the only server that gives me problems.

Offline Chris

  • BolehVPN Staff
  • Admiral
  • *****
  • Posts: 2200
  • Beneath a cobalt moon
Re: Netherlands Server Time-Outs.
« Reply #6 on: October 30, 2013, 09:21:43 PM »
What about FullyRouted-France? Fits your requirements pretty well.

Please also do a traceroute to the NL server, and a pingtest with -n 100

Post your results here

Offline Indingo

  • BolehVPN Subscriber
  • Boatswain
  • **
  • Posts: 85
Re: Netherlands Server Time-Outs.
« Reply #7 on: October 30, 2013, 09:59:26 PM »
What about FullyRouted-France? Fits your requirements pretty well.

Please also do a traceroute to the NL server, and a pingtest with -n 100

Post your results here

France exit IP and enter IP are different, I also find many open ports/stealth "not closed" ports. I require both enter and exit IP to be the same and static, and all the ports but the ones needed to be blocked. Just like the NL server, but without the drop-outs.

Offline Chris

  • BolehVPN Staff
  • Admiral
  • *****
  • Posts: 2200
  • Beneath a cobalt moon
Re: Netherlands Server Time-Outs.
« Reply #8 on: October 31, 2013, 02:49:44 PM »
Alright. Could you do a pingtest and traceroute as stated in my last post?

Offline Indingo

  • BolehVPN Subscriber
  • Boatswain
  • **
  • Posts: 85
Re: Netherlands Server Time-Outs.
« Reply #9 on: November 01, 2013, 02:48:28 AM »
Alright. Could you do a pingtest and traceroute as stated in my last post?

I would really love to man... but its driving me crazy. I have tried a few times already and it takes me so many retries to get it to work, and when it works it disconnects during testing. I seriously don't know why its only this server.. but like, its getting to a point trying to find the answer myself is just wasting my time.

Offline Chris

  • BolehVPN Staff
  • Admiral
  • *****
  • Posts: 2200
  • Beneath a cobalt moon
Re: Netherlands Server Time-Outs.
« Reply #10 on: November 01, 2013, 02:58:17 PM »
Sorry, I should have been clearer. With the VPN off, please run the pingtest and traceroute.

Where is your location by the way Do you have any antivirus / firewalls installed? Any other VPN software?

Offline Indingo

  • BolehVPN Subscriber
  • Boatswain
  • **
  • Posts: 85
Re: Netherlands Server Time-Outs.
« Reply #11 on: November 01, 2013, 10:32:37 PM »
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows>tracert 62.212.85.79

Tracing route to br3nl.bolehvpn.net [62.212.85.79]
over a maximum of 30 hops:

  1     3 ms     3 ms     3 ms  SkyRouter.Home [192.168.0.1]
  2     *        *        *     Request timed out.
  3    15 ms    17 ms    14 ms  ip-84-38-37-12.easynet.co.uk [84.38.37.12]
  4    17 ms    15 ms    15 ms  027808f3.bb.sky.com [2.120.8.243]
  5    12 ms    12 ms    12 ms  peering.thn.lon.leaseweb.net [195.66.225.56]
  6    21 ms    19 ms    19 ms  31.31.32.73
  7    19 ms    22 ms    25 ms  85.17.100.143
  8    19 ms    18 ms    20 ms  te9-3.hv15.evo.leaseweb.net [82.192.95.227]
  9    18 ms    19 ms    18 ms  br3nl.bolehvpn.net [62.212.85.79]

Trace complete.

@@

C:\Windows>ping 62.212.85.79

Pinging 62.212.85.79 with 32 bytes of data:
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57

Ping statistics for 62.212.85.79:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 18ms, Average = 18ms

UK, England. GDATA Internet Security 2014, Mullvad VPN "Not a problem, checked already."

Offline Chris

  • BolehVPN Staff
  • Admiral
  • *****
  • Posts: 2200
  • Beneath a cobalt moon
Re: Netherlands Server Time-Outs.
« Reply #12 on: November 03, 2013, 08:44:23 AM »
ping 62.212.85.79 -n 100

After you run the above command, is there any packet loss? Could you also try the FullyRouted-TCP-EU server?

Will be referring this to my supervisor.
« Last Edit: November 03, 2013, 08:56:45 AM by Chris »

Offline PitBoss

  • Administrator
  • Admiral
  • *****
  • Posts: 1250
Re: Netherlands Server Time-Outs.
« Reply #13 on: November 03, 2013, 09:22:59 AM »
You can use France server. The entry IP is only use by the user to connect to the server and and there are 4 entry IP for this server and one exit IP. Reason is, this server is a gigabit server with 4 redundant/load balancing static entry IPs and one exit IP.

I will check on the NL server but this is usually due to some network stack getting corrupted, either from client or server side.
Since all other servers is doing ok, then it could be server side.

In the mean time, reset your network stack by doing this:

Open command prompt and then type (make sure run as administrator):

netsh int ip reset C:\netsh.log.txt
netsh winsock reset

You may need to reboot your PC a couple of times after doing this.

Or you can just visit this http://support.microsoft.com/kb/299357

See if this resolves the issue or not.
« Last Edit: November 03, 2013, 09:41:00 AM by PitBoss »

Co-Founder / Administrator

Offline Indingo

  • BolehVPN Subscriber
  • Boatswain
  • **
  • Posts: 85
Re: Netherlands Server Time-Outs.
« Reply #14 on: November 03, 2013, 05:41:26 PM »
ping 62.212.85.79 -n 100

After you run the above command, is there any packet loss? Could you also try the FullyRouted-TCP-EU server?

Will be referring this to my supervisor.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>ping 62.212.85.79 -n 100

Pinging 62.212.85.79 with 32 bytes of data:
Reply from 62.212.85.79: bytes=32 time=21ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=21ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=42ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=21ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=34ms TTL=57
Reply from 62.212.85.79: bytes=32 time=41ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=31ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=23ms TTL=57
Reply from 62.212.85.79: bytes=32 time=20ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=76ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=20ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=20ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=38ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=23ms TTL=57
Reply from 62.212.85.79: bytes=32 time=20ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=21ms TTL=57
Reply from 62.212.85.79: bytes=32 time=38ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=20ms TTL=57
Reply from 62.212.85.79: bytes=32 time=20ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=89ms TTL=57
Reply from 62.212.85.79: bytes=32 time=18ms TTL=57
Reply from 62.212.85.79: bytes=32 time=19ms TTL=57

Ping statistics for 62.212.85.79:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 89ms, Average = 21ms

In the mean time, reset your network stack by doing this:

Open command prompt and then type (make sure run as administrator):

netsh int ip reset C:\netsh.log.txt
netsh winsock reset

You may need to reboot your PC a couple of times after doing this. See if this resolves the issue or not.

Done, I will use NL server today and see if the problem is still there. Let me know if you find anything on the server end.

Thanks Chris, PitBoss.
« Last Edit: November 03, 2013, 05:50:36 PM by Indingo »