Hideway Forum

Bitte loggen sie sich ein oder registrieren sie sich.

Einloggen mit Benutzername, Passwort und Sitzungslänge
Erweiterte Suche  

Neuigkeiten:

Welcome to Hideway's support forum

Autor Thema: port closed  (Gelesen 3213 mal)

vanish

  • Newbie
  • *
  • Beiträge: 5
port closed
« am: März 12, 2010, 23:05:42 »

hi
im using PPTP-Protocol but when i connect after 2 or 3 min it shows this error:



can u help me?
Gespeichert

hideway2

  • Administrator
  • Full Member
  • *****
  • Beiträge: 130
Re: port closed
« Antwort #1 am: März 13, 2010, 02:55:16 »

Hello,

could you please let us know if ...

... you have been following the guide for setting up the PPTP-Connection posted in this forum.
... you have been able to successfully establish a PPTP connection before the error message appeared.
... you have changed your system (e.g. installed or changed your firewall, anti-virus software, etc.) before the error message appeared.

Please also post the settings you have entered and the operating system you are using to setup your connection.


Kind regards,
hideway2
Gespeichert

vanish

  • Newbie
  • *
  • Beiträge: 5
Re: port closed
« Antwort #2 am: März 13, 2010, 09:06:54 »

hi
Zitat
... you have been following the guide for setting up the PPTP-Connection posted in this forum.
yes
Zitat
... you have been able to successfully establish a PPTP connection before the error message appeared.
yes
Zitat
... you have changed your system (e.g. installed or changed your firewall, anti-virus software, etc.) before the error message appeared.
i just installed ESET NOD32 smart security
Zitat
Please also post the settings you have entered
what? :o
Zitat
operating system you are using to setup your connection.
windows 7

thanks for your support
Gespeichert

hideway2

  • Administrator
  • Full Member
  • *****
  • Beiträge: 130
Re: port closed
« Antwort #3 am: März 13, 2010, 12:40:08 »

Hello,

sorry for the misleading "settings" request, just for clarification, by settings are the "IP-address" or hostname (vpn1.hideway.eu), the "Typ of VPN" and the eventually unchecked option "Challenge Handshake Authentication Protocol (CHAP)" meant. NOT your account details (username and/or password).

Please try to temporary disable your ESET Smart Security or ESET NOD32 Antivirus and check if a connection can be established.

Please double check the settings as described in the Windows 7 guide (http://www.hideway.eu/forum/windows-vista/set-up-pptp-connection-on-windows-7/msg367) once more especially the "Typ of VPN" and the unchecked "CHAP" option. You could also try to exchange the hostname "vpn1.hideway.eu" with the IP-address "83.65.30.29" to establish a connection as sometimes resolving domain names doesn't work.

Please also let us know if you can you establish a connection successfully using OpenVPN?


Kind regards,
hideway2
Gespeichert

vanish

  • Newbie
  • *
  • Beiträge: 5
Re: port closed
« Antwort #4 am: März 13, 2010, 14:43:14 »

hi
Zitat
by settings are the "IP-address" or hostname (vpn1.hideway.eu), the "Typ of VPN" and the eventually unchecked option "Challenge Handshake Authentication Protocol (CHAP)" meant




Zitat
Please try to temporary disable your ESET Smart Security or ESET NOD32 Antivirus and check if a connection can be established.
nothing changes  ???
 by the way when i change host name to (vpn2.hideway.eu) or (vpn4.hideway.eu) it works and they are faster than (vpn1.hideway.eu) !
but im afraid thay're not as secure as (vpn1.hideway.eu) !

Zitat
Please also let us know if you can you establish a connection successfully using OpenVPN?
 
no, i can't use it
Zitat
Sat Mar 13 17:06:40 2010 OpenVPN 2.1_rc13 i686-pc-mingw32 [SSL] [LZO2] [PKCS11] built on Oct  7 2008
Sat Mar 13 17:06:40 2010 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA.  OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Sat Mar 13 17:06:40 2010 WARNING: Make sure you understand the semantics of --tls-remote before using it (see the man page).
Sat Mar 13 17:06:40 2010 Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Sat Mar 13 17:06:40 2010 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Mar 13 17:06:40 2010 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Mar 13 17:06:40 2010 LZO compression initialized
Sat Mar 13 17:06:40 2010 Control Channel MTU parms [ L:1574 D:166 EF:66 EB:0 ET:0 EL:0 ]
Sat Mar 13 17:06:41 2010 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Sat Mar 13 17:06:41 2010 Local Options hash (VER=V4): '13a273ba'
Sat Mar 13 17:06:41 2010 Expected Remote Options hash (VER=V4): '360696c5'
Sat Mar 13 17:06:41 2010 Socket Buffers: R=[8192->8192] S=[8192->8192]
Sat Mar 13 17:06:41 2010 UDPv4 link local (bound): [undef]:1194
Sat Mar 13 17:06:41 2010 UDPv4 link remote: 83.65.30.29:1194
Sat Mar 13 17:07:41 2010 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sat Mar 13 17:07:41 2010 TLS Error: TLS handshake failed
Sat Mar 13 17:07:41 2010 TCP/UDP: Closing socket
Sat Mar 13 17:07:41 2010 SIGUSR1[soft,tls-error] received, process restarting
Sat Mar 13 17:07:41 2010 Restart pause, 2 second(s)
Sat Mar 13 17:07:43 2010 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA.  OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Sat Mar 13 17:07:43 2010 WARNING: Make sure you understand the semantics of --tls-remote before using it (see the man page).
Sat Mar 13 17:07:43 2010 Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Sat Mar 13 17:07:43 2010 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Mar 13 17:07:43 2010 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Mar 13 17:07:43 2010 LZO compression initialized
Sat Mar 13 17:07:43 2010 Control Channel MTU parms [ L:1574 D:166 EF:66 EB:0 ET:0 EL:0 ]
Sat Mar 13 17:07:43 2010 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Sat Mar 13 17:07:43 2010 Local Options hash (VER=V4): '13a273ba'
Sat Mar 13 17:07:43 2010 Expected Remote Options hash (VER=V4): '360696c5'
Sat Mar 13 17:07:43 2010 Socket Buffers: R=[8192->8192] S=[8192->8192]
Sat Mar 13 17:07:43 2010 UDPv4 link local (bound): [undef]:1194
Sat Mar 13 17:07:43 2010 UDPv4 link remote: 83.65.30.29:1194
Sat Mar 13 17:08:43 2010 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sat Mar 13 17:08:43 2010 TLS Error: TLS handshake failed
Sat Mar 13 17:08:43 2010 TCP/UDP: Closing socket
Sat Mar 13 17:08:43 2010 SIGUSR1[soft,tls-error] received, process restarting
Sat Mar 13 17:08:43 2010 Restart pause, 2 second(s)
Sat Mar 13 17:08:45 2010 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA.  OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Sat Mar 13 17:08:45 2010 WARNING: Make sure you understand the semantics of --tls-remote before using it (see the man page).
Sat Mar 13 17:08:45 2010 Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Sat Mar 13 17:08:45 2010 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Mar 13 17:08:45 2010 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Mar 13 17:08:45 2010 LZO compression initialized
Sat Mar 13 17:08:45 2010 Control Channel MTU parms [ L:1574 D:166 EF:66 EB:0 ET:0 EL:0 ]
Sat Mar 13 17:08:45 2010 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Sat Mar 13 17:08:45 2010 Local Options hash (VER=V4): '13a273ba'
Sat Mar 13 17:08:45 2010 Expected Remote Options hash (VER=V4): '360696c5'
Sat Mar 13 17:08:45 2010 Socket Buffers: R=[8192->8192] S=[8192->8192]
Sat Mar 13 17:08:45 2010 UDPv4 link local (bound): [undef]:1194
Sat Mar 13 17:08:45 2010 UDPv4 link remote: 83.65.30.29:1194
Sat Mar 13 17:09:45 2010 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sat Mar 13 17:09:45 2010 TLS Error: TLS handshake failed
Sat Mar 13 17:09:45 2010 TCP/UDP: Closing socket
Sat Mar 13 17:09:45 2010 SIGUSR1[soft,tls-error] received, process restarting
Sat Mar 13 17:09:45 2010 Restart pause, 2 second(s)
Sat Mar 13 17:09:47 2010 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA.  OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Sat Mar 13 17:09:47 2010 WARNING: Make sure you understand the semantics of --tls-remote before using it (see the man page).
Sat Mar 13 17:09:47 2010 Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Sat Mar 13 17:09:47 2010 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Mar 13 17:09:47 2010 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Mar 13 17:09:47 2010 LZO compression initialized
Sat Mar 13 17:09:47 2010 Control Channel MTU parms [ L:1574 D:166 EF:66 EB:0 ET:0 EL:0 ]
Sat Mar 13 17:09:47 2010 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Sat Mar 13 17:09:47 2010 Local Options hash (VER=V4): '13a273ba'
Sat Mar 13 17:09:47 2010 Expected Remote Options hash (VER=V4): '360696c5'
Sat Mar 13 17:09:47 2010 Socket Buffers: R=[8192->8192] S=[8192->8192]
Sat Mar 13 17:09:47 2010 UDPv4 link local (bound): [undef]:1194
Sat Mar 13 17:09:47 2010 UDPv4 link remote: 83.65.30.29:1194
Gespeichert

hideway2

  • Administrator
  • Full Member
  • *****
  • Beiträge: 130
Re: port closed
« Antwort #5 am: März 13, 2010, 19:33:34 »

Hello,

according to your description you cannot use port 1194/udp (used by vpn1). This is the standard port also used by the default OpenVPN configuration. The port may be blocked by your firewall or service provider.

If you can use any of the other two servers (vpn2  or vpn4) that's just fine too. There is definitely no difference regarding the security between the servers. For the most secure connection, you should definitely stick to OpenVPN as it currently provides the best encryption for your connection.

Your OpenVPN should also work if you change the port as described in the corresponding post in our forum (http://www.hideway.eu/forum/faq/port-194-is-blocked/msg62) to either 443/tcp or 443/udp.


Kind regards,
hideway2
Gespeichert

vanish

  • Newbie
  • *
  • Beiträge: 5
Re: port closed
« Antwort #6 am: März 13, 2010, 20:22:41 »

thank you
you are the best :-*
Gespeichert

vanish

  • Newbie
  • *
  • Beiträge: 5
Re: port closed
« Antwort #7 am: März 18, 2010, 18:43:34 »

hi
it's me again
i have new problem
i can connect to the server but i can't use internet
i changed the hostname but it didn't work
Gespeichert

hideway2

  • Administrator
  • Full Member
  • *****
  • Beiträge: 130
Re: port closed
« Antwort #8 am: März 19, 2010, 12:51:40 »

Hello again,

if you can connect to our server, but cannot browse the web, your account may be expired or the allowed data traffic volume has been reached.

To check whether or not your account is still active, please visit the "Statistic of data transfer" menu in the "customers area" on our homepage (https://www.hideway.eu/extranet/menu.php/traffic.html). There you can review your account for active and remaining data traffic volume.


Kind regards,
hideway2
Gespeichert