Protocol error occurred error was returned from the destination server vpn что делать
Обновлено: 02.07.2024
Post by matt.sayers » Sun Jun 08, 2014 2:13 am
I have recently upgraded my SoftEther VPN server to version 4.07 (Build 9448) to take fixes for OpenSSL.
I am able to successfully connect to the VPN from a computer using the 4.04 (Build 9412) client.
If I attempt to also update my vpn client to version 4.07 (Build 9448), I get errors any time I connect. The errors says "Error 2: Protocol Error." This happens on any port I try to connect with. I tried 443, 992 and 5555. And yes, I do have the server listening to those ports.
Here is an error entry from the client log:
2014-06-07 21:20:02.456 VPN Connection Setting "[real server name removed]": The connection has been either disconnected or it failed. Cause: Protocol error occurred. Error was returned from the destination server. (code 2)
I ended up uninstalling the 4.07 client and reinstalling 4.04 client which works.
Is this a known issue or configuration change that I am missing? If not, can you look into this. If you need more details to reproduce this error I will be happy to provide those.
Thanks in advance.
gavinlee Posts: 8 Joined: Thu Jun 05, 2014 3:06 amPost by gavinlee » Sun Jun 08, 2014 2:23 am
matt.sayers wrote:
> I have recently upgraded my SoftEther VPN server to version 4.07 (Build
> 9448) to take fixes for OpenSSL.
>
> I am able to successfully connect to the VPN from a computer using the 4.04
> (Build 9412) client.
>
> If I attempt to also update my vpn client to version 4.07 (Build 9448), I
> get errors any time I connect. The errors says "Error 2: Protocol
> Error." This happens on any port I try to connect with. I tried 443,
> 992 and 5555. And yes, I do have the server listening to those ports.
>
> Here is an error entry from the client log:
> 2014-06-07 21:20:02.456 VPN Connection Setting "[real server name
> removed]": The connection has been either disconnected or it failed.
> Cause: Protocol error occurred. Error was returned from the destination
> server. (code 2)
>
> I ended up uninstalling the 4.07 client and reinstalling 4.04 client which
> works.
>
> Is this a known issue or configuration change that I am missing? If not,
> can you look into this. If you need more details to reproduce this error I
> will be happy to provide those.
>
> Thanks in advance.
95
Hi Matt:
I have met the same problem like you did, I can't able to connect any one of VPN in the list. Even I connected teporary,it will be disconnected in a few minutes.My version is also 4.07(9448). This is the newest version which the official website updated. Did you solve this problem now? or do the old version before 4.07 still work successfully?
thank you
BR
Post by matt.sayers » Sun Jun 08, 2014 2:31 am
I am able to successfully connect to a server on version 4.07 (Build 9488) with the 4.04 client. I had to uninstall the 4.07 Client (Build 9488) then install the older 4.04 Client (Build 9412). This seems to preserve your settings OK between uninstall/reinstall which is nice.
To be clear, I never had an issue with the server versions.
Server is on 4.07.
4.04 client will successfully connect.
4.07 client will throw protocol errors.
I would try downgrading your client version to 4.04 and see if that helps. It did for me. I hope the issue can be fixed in a newer version of the client though because now I have to warn my users not to download the suggested client update.
dnobori Posts: 228 Joined: Tue Mar 05, 2013 10:04 amPost by dnobori » Sun Jun 08, 2014 2:47 am
I am a developer of SoftEther VPN programs.
To analyze your problem, I need to reproduce the problem.
Could you please give me the IP address and the port number of actual running SoftEther VPN Server which occurs your problem? If so, I am going to check whether there are certainly protocol-error when the connection attempt will be made from the latest version of VPN Client. If that is positive, I will try to identify which VPN Client version begins to cause the problem.
I am going to check whether the "protocol error" occurs or not during the SSL connection phase. This step needs no login attempts because the protocol error occurs before the user authentication phase. No username and login credentials are needed. Please provide us just IP address and port number.
Please keep the VPN Server up to date (Ver 4.07).
matt.sayers Posts: 7 Joined: Sun Jun 08, 2014 2:02 amPost by matt.sayers » Sun Jun 08, 2014 2:54 am
Thank you for your assistance.
I have uploaded a text file to the URL you provided named "network info.txt" so that you may test. Let me know if you need anything else.
matt.sayers Posts: 7 Joined: Sun Jun 08, 2014 2:02 amPost by matt.sayers » Sun Jun 08, 2014 2:56 am
dnobori Posts: 228 Joined: Tue Mar 05, 2013 10:04 amPost by dnobori » Sun Jun 08, 2014 2:57 am
Thank you. I am going to start the actual check of protocol errors, trying all versions of VPN Client between 4.04 and 4.07. matt.sayers Posts: 7 Joined: Sun Jun 08, 2014 2:02 amPost by matt.sayers » Sun Jun 08, 2014 3:04 am
dnobori Posts: 228 Joined: Tue Mar 05, 2013 10:04 amPost by dnobori » Sun Jun 08, 2014 3:15 am
I found the problem.
The IP address and the port number (443) which you speficied is occupied by the another program, which might be a LinkSys router.
Please check your router setting to transfer the public TCP port "443" to the internal private IP address of the VPN Server.
openssl s_client -connect *.*.*.*:443
CONNECTED(00000003)
depth=0 /CN=Linksys_RVS4000/OU=RVS4000/O=Linksys/C=US
verify error:num=18:self signed certificate
verify return:1
depth=0 /CN=Linksys_RVS4000/OU=RVS4000/O=Linksys/C=US
verify return:1
---
Certificate chain
0 s:/CN=Linksys_RVS4000/OU=RVS4000/O=Linksys/C=US
i:/CN=Linksys_RVS4000/OU=RVS4000/O=Linksys/C=US
---
Post by matt.sayers » Sun Jun 08, 2014 3:33 am
Thank you for the update.
Did something change in version 4.07 which no longer can ignore/bypass this issue as version 4.04 did?
I will give your suggestion a try on Monday when I am back in the office. I will post back next week and let you know how it goes.
gavinlee Posts: 8 Joined: Thu Jun 05, 2014 3:06 amPost by gavinlee » Sun Jun 08, 2014 4:14 am
dnobori wrote:
> I found the problem.
> The IP address and the port number (443) which you speficied is occupied by
> the another program, which might be a LinkSys router.
>
> Please check your router setting to transfer the public TCP port
> "443" to the internal private IP address of the VPN Server.
>
> openssl s_client -connect *.*.*.*:443
> CONNECTED(00000003)
> depth=0 /CN=Linksys_RVS4000/OU=RVS4000/O=Linksys/C=US
> verify error:num=18:self signed certificate
> verify return:1
> depth=0 /CN=Linksys_RVS4000/OU=RVS4000/O=Linksys/C=US
> verify return:1
> ---
> Certificate chain
> 0 s:/CN=Linksys_RVS4000/OU=RVS4000/O=Linksys/C=US
> i:/CN=Linksys_RVS4000/OU=RVS4000/O=Linksys/C=US
> ---
Dnobori:
Thank you for your help. Could you tell me the detial of how to check the router setting to transfer the public TCP port"443" to the internal private IP address of the VPN Server? Honestly I am not good at computer.
Thank you again
Post by gavinlee » Sun Jun 08, 2014 4:23 am
matt.sayers wrote:
> Hi Gavin.
>
> I am able to successfully connect to a server on version 4.07 (Build 9488)
> with the 4.04 client. I had to uninstall the 4.07 Client (Build 9488) then
> install the older 4.04 Client (Build 9412). This seems to preserve your
> settings OK between uninstall/reinstall which is nice.
>
> To be clear, I never had an issue with the server versions.
> Server is on 4.07.
> 4.04 client will successfully connect.
> 4.07 client will throw protocol errors.
>
> I would try downgrading your client version to 4.04 and see if that helps.
> It did for me. I hope the issue can be fixed in a newer version of the
> client though because now I have to warn my users not to download the
> suggested client update.
>
> Matt
Hi,Matt:
thank you for your help. I just unist the 4.07 client and reinstall the 4.04 client. Then I am able to connect temporary. but I don't know how long I can maintain this.
hope the developer will fix this soon
Post by dnobori » Sun Jun 08, 2014 7:47 am
I wrote a patch to work around the NAT-T issue for the enviroment which is like your network.
** Work around the NAT traversal problem.
Adjusted the priority between TCP/IP Direct Connection and UDP-based NAT-Traversal. On this version (Ver 4.08), NAT-Traversal will always be used if the client program detects that the specified TCP destination port on the destination server is occupied by non-SoftEther VPN Server. Anyone who faces to the connection problem on the VPN Server which is behind the NAT-box should install this update.
In the previous version (Ver 4.07), when the VPN Client attempts to connect to the VPN Server, the client firstly establish the connection via the TCP/IP direct protocol. If the TCP connection establishes successfully (in the layer-3) but the TCP port returns non-VPN protocol data (in the layer-7), the protocol error occurs immediately even if the NAT-Traversal connection attempt is still pending. This phenomenon often occurs when the VPN Server is behind the NAT-box, and the NAT-box has a listening TCP-443 port by itself. In that condition, the VPN Client attempts to connect to that TCP-443 port firstly, and the protocol error occurs immediately NAT-box returns non-VPN protocol (e.g. HTML-based administration page).
In order to work around that, this version (Ver 4.08) of VPN Client changed the behavior. On this version, if the VPN Client detects that the destination TCP Port is occupied by a non-VPN program, then the client will always use NAT-Traversal socket. This minor change will fix the connection problem to VPN servers behind the NATs.
VPN GATE. Error code 2. Помогите решить проблему!
Частая ошибка, после переустановки, не настраиваете дату и время, в этом и вся проблема с вашим VPN
да это я уже поняла, в этот раз даже не сообразила проверить)) была уверена что число именно такое . просто потерялась в днях)
Выполните в командной строке tracert .
И покажите скриншот результата.
проблема была в неверно установленной дате на компьютере, уже исправлено. в остальном не критично все.. работает и ок.
Попробуй подключиться к русским серверам, или переустанови прогу! У меня она тоже стояла раньше.
зачем мне русские сервера? я использую программу для доступа на яп. на русские я итак могу заходить без VPN и без проблем.. =)
Protocol error occurred error was returned from the destination server vpn что делать
Post by LordBadon » Thu Sep 25, 2014 5:00 am
Originally posted in the VPN Gate Discussion forum, but since nobody helped me there I'll post things here instead and see how they go.
Hi, I am running the latest version of SoftEther VPN Client on my Windows 8 PC. It was working fine until about a week ago when I started getting an error saying this:
"Error (Error Code 2):
Protocol error occurred. Error was returned from the destination server."
I have ran the application as an administrator and I still get the error. I have tried allowing SoftEther access to port 443 in my firewall settings and I still get the error. I have tried reinstalling and I still get the error.
I checked my network activity in Kaspersky and closed all applications using port 443 other than SoftEther (in this case, I closed Skype, LINE, Flash, and FireFox). I still got the error.
The only thing that seems to allow me to connect to a VPN is using UDP instead of TCP, and even that only allows the connection to last 5 minutes before I am suddenly disconnected for no apparent reason at all.
At this point I am at a loss, I don't know what else to try. Could anybody help me?
Required Info:
OS: Windows 8.1 64-bit
SoftEther version 4.1 build 9473
I do have a firewall, but I've done everything I can think of for changing the rules to allow connections through (though it was that way in the first place) and it still did not work.
Daniel Sokolowski's Blog
Protocol error occurred. Error was returned from the destination server.
When you run `vpncmd` it attempts to connect, find an active port, but of course fails with 'Protocol error occurred. Error was returned from the destination server.' because it's not actually connecting to the vpn server.
By default Softether also listens on 992 , 1194 , and 5555 so the sollution is to modify specify `localhost:5555` when executing the `vpncmnd`. If this has helped you feel free to comment or follow me on twitter @danielsokolows.
Читайте также: