Arrakis wrote:Check this screenshot. It's this line: Protect against port scan (Blocks for one day any devices characterized as performing a port-scan on the WAN interface)
Alternatively, it could be a combination of modifications we've done to the router firewall.
Arrakis wrote:There's a possible solution for this issue.
We have performed an experiment - disabled specific features in the firewall while enabling others. We believe that we have isolated the issue, and it may have something to do with United States networking companies routers.
Check this screenshot. It's this line: Protect against port scan (Blocks for one day any devices characterized as performing a port-scan on the WAN interface)
Alternatively, it could be a combination of modifications we've done to the router firewall.
Zimr wrote:Arrakis wrote:There's a possible solution for this issue.
We have performed an experiment - disabled specific features in the firewall while enabling others. We believe that we have isolated the issue, and it may have something to do with United States networking companies routers.
Check this screenshot. It's this line: Protect against port scan (Blocks for one day any devices characterized as performing a port-scan on the WAN interface)
Alternatively, it could be a combination of modifications we've done to the router firewall.
yeah this don't work try again
Leez wrote:Zimr wrote:Arrakis wrote:There's a possible solution for this issue.
We have performed an experiment - disabled specific features in the firewall while enabling others. We believe that we have isolated the issue, and it may have something to do with United States networking companies routers.
Check this screenshot. It's this line: Protect against port scan (Blocks for one day any devices characterized as performing a port-scan on the WAN interface)
Alternatively, it could be a combination of modifications we've done to the router firewall.
yeah this don't work try again
Of course its not that. Its server side issue. For some reason server keeps your character connection even after You log out, so its stuck somewhere in between and it wont let You connect until your last connection is dropped. SERVER RESTART always helped this issue as a workaround until they fix the problem....
or just hope Your server number will restart by itself
Arrakis wrote:There's a possible solution for this issue.
We have performed an experiment - disabled specific features in the firewall while enabling others. We believe that we have isolated the issue, and it may have something to do with United States networking companies routers.
Check this screenshot. It's this line: Protect against port scan (Blocks for one day any devices characterized as performing a port-scan on the WAN interface)
Alternatively, it could be a combination of modifications we've done to the router firewall.
Arrakis wrote:Most of the connectivity issues are, unfortunately, on our side. This one was present before, and we are very sorry that we still have not managed to completely fix it yet We'll resolve this issue as soon as possible. You can help us do that by sending your dxdiag and game logs to helpmmo@lifeisfeudal.com
Thank you.
Irahim wrote:that's your responsability
Arrakis wrote:Irahim wrote:that's your responsability
And we are taking it very seriously. The purpose of those closed beta test is to determine the cause of those connectivity issues so we can actually fix them. So instead of threatening us with your lawyer, you could actually try to help us by sending your game logs to helpmmo@lifeisfeudal.com if you don't mind
Thank you very much.
Ishamael wrote:Why is everyone acting like this is release? The shit you are dealing with in early access is the same shit you are going to brag about going through to other players that did not suffer through this 2 years from now.
Vets now are already telling tales of times when there were no personal claims and you had to make a warehouse to store your shit.
You thought alpha tester and true believers were just titles???? There's real suffering in there lol.