Page 1 of 1

Protocol Error-- on vpn over dns connection

Posted: Sun Aug 30, 2015 10:36 pm
by glenndale
I have setup a softether vpn server to get around my school ISP portal with via VPN over DNS to gain internet access..
The problem is that when I disconnect my vpn for a while and I initiate the connection again after about 5 minutes, I get protocol error, I am only able to connect after I have connected to a direct internet connection and then disconnect then connect to my ISP portal.
Internet connection A is blocked via ISP portal
Internet connection B is open

Client PC ------->>>UDP Hole punching and VPN over DNS---> Softether vpn server ------->> Free Internet A

as illustrated above, I am able to access the internet with vpn over DNS for free internet access with Internet A, but this only works if I do an initial connection to a working internet connection B and then disconnect and connect to my Internet A within a few minutes.

But anytime I disconnect from Internet A for several minutes, if I try to connect again I get "protocol Error" this happens until I connect to Internet connection B or a live internet before I disconnect and connect to A again.

I really need help to figure out why I am not able to connect straight away without make an initial connection.

Re: Protocol Error-- on vpn over dns connection

Posted: Thu Sep 10, 2015 7:37 am
by thisjun
I think session remains on router or VPN server. maybe maybe...
I don't have good idea.

Re: Protocol Error-- on vpn over dns connection

Posted: Tue Sep 15, 2015 9:53 pm
by lil_je4u
mclaren wrote:
> glenndale, I have this same exact problem. I'm willing to pay anyone who
> knows how to fix it. Sometimes it connects, but sometimes (more often than
> not) it gives a protocol error. I have tried everything from tweaking the
> settings on my server/client to changing pcs. Sometimes as well, the client
> will say verifying certificate and then the error 2 appears. Can someone
> please help? I'm willing to pay. I also showed it to a friend of mine and
> he said there is an SSL failure at the port of connection hence the
> failure.. (I don't know what that that means).
>
> Also, someone suggested I use iodine to solve this problem, although I have
> no idea what that is or if that's helpful. Any pointers to a solution would
> be very much appreciated.

send me a skype request @thykhin.