Serious network lock issue... again

[MaciejB 0]

Hi there,

 

 

I know that this topic has already been tackled a bunch of times, but as Im still in dire straits, I'm opening it again.

I've been using Airvpn for a few months and it works splendidly, though I've learned only recently, while trying to connect to a public wifi at the Uni, that something's wrong. I cannot obtain connection othrwise than via Airvpn and honestly, I am already quite exhausted. I think I tried everything : turning off firewalls (both Windows and Avast), going back to previous configs, turning off networck lock, uninstalling Airvpn... nothing. If it's relevant, note that I'm using Windows 10, though I had Airvpn installed on Win 8 which I upgraded to the newest vrsion a few weeks ago.

 

 

Please, have pity, I really need to fix it.

 

Cordially,

Maciej

 

[Staff 10014]

Hello,

 

probably it has nothing to do with Network Lock feature. It's not unusual that public WiFi hot spots block UDP. Maybe that's the cause of the problem. Try a connection in TCP, or even "SSL Tunnel - Port 443" to see whether it solves the problem.

 

In Eddie you can change connection mode in "AirVPN" -> "Preferences" -> "Protocols".

 

Kind regards

[Valerian 20]

I thought the OP's problem is that he can't connect *without* going via AirVPN.

[Staff 10014]

I thought the OP's problem is that he can't connect *without* going via AirVPN.

 

In this case there is a pinned topic on this very same forum.

 

Kind regards

[rickjames 106]

I thought the OP's problem is that he can't connect *without* going via AirVPN.

Had to re-read it myself to catch that. I think you're correct.

 

 

In this case there is a pinned topic on this very same forum.

 

Kind regards

This ^ link -> https://airvpn.org/topic/14829-can-only-connect-to-the-internet-browser-through-airvpn/

 

And here's the link from that thread regarding resetting the windows firewall.

http://windows.microsoft.com/en-us/windows7/restore-windows-firewall-settings

 

 

This could also be an unforeseen issue caused by a bug created in windows due to running both the windows firewall and Avast. Might want to pick just one firewall.

Otherwise you've got avast and the win firewall screaming THIS IS SPARTA both trying to protect your packets.

[me.moo@posteo.me 80]

This could also be an unforeseen issue caused by a bug created in windows due to running both the windows firewall and Avast. Might want to pick just one firewall.

Otherwise you've got avast and the win firewall screaming THIS IS SPARTA both trying to protect your packets.

Is it really a bug created by Microsoft? I was told off big time by 'Staff' for using Comodo and Network Lock simultaneously. I assumed that that was across the board

[rickjames 106]

 

This could also be an unforeseen issue caused by a bug created in windows due to running both the windows firewall and Avast. Might want to pick just one firewall.

Otherwise you've got avast and the win firewall screaming THIS IS SPARTA both trying to protect your packets.

Is it really a bug created by Microsoft? I was told off big time by 'Staff' for using Comodo and Network Lock simultaneously. I assumed that that was across the board

 

I never said a bug created by Microsoft, I said a bug created in windows due to running 2 different firewalls / firewall software at the same time.

 

Tbh I have no idea if its a bug. I only know that windows is unpredictable, especially when dealing with 2 bits of code trying to do similar things on one interface. One may try and take priority over the other, they might fight causing errors or they may both get along fine. I just don't know because I can't predict the unpredictable.

 

Windows should start a casino, booting up is like rolling the dice lol.

[me.moo@posteo.me 80]

I never said a bug created by Microsoft, I said a bug created in windows due to running 2 different firewalls / firewall software at the same time.

 

Tbh I have no idea if its a bug. I only know that windows is unpredictable, especially when dealing with 2 bits of code trying to do similar things on one interface. One may try and take priority over the other, they might fight causing errors or they may both get along fine. I just don't know because I can't predict the unpredictable.

 

Windows should start a casino, booting up is like rolling the dice lol.

errm, who else wrote Windows? Anyway Rick I wasn't having a go - that Casino is one I would certainly keep away from. Fancy not being able to predict the unpredictable !"£$%^&, you need to buck your ideas up 

[me.moo@posteo.me 80]

oh and what happens when two programs fight for system resources - in the old days you might get what was called the deadly handshake/embrace - if that is impossible these days I have no idea since I am well out of all that now!

[rickjames 106]

errm, who else wrote Windows? Anyway Rick I wasn't having a go - that Casino is one I would certainly keep away from. Fancy not being able to predict the unpredictable !"£$%^&, you need to buck your ideas up 

 

A bug created from apps running inside the windows environment, not necessarily because of the windows environment, but something new created when two apps interact in an unforeseen fashion.

[MaciejB 0]

Hey guys,

 

 

Sorry for my very tardy response but actually the problem persisted, I tried everything what you said and it didn't work. Eventually I came up with an idea so obvious that I'm angry I haven't though abut it at the very outset. I download drivers for my network card, then I uninstalled the apparently affected onces and installed them again. It worked immediately and finally the problem is solved. I hope it may be of some help for others.

 

All the best,

Maciej