List of network ports needed for correct work game client.
If you have some problems with connection to server (data is not loaded in Port, exit to Open World is not working, empty chat or entering battles is not working) check that 7770, 8089, 5672, 5222, 8080, 21020-21036, 7401-7600 ports are available in your network and PC.
Checking network connection to game servers (using tracert)
Connection issues (login errors, random disconnects etc.) can be caused by problems with intermediate network providers between client machine and game servers. Connection can be tested using Windows tracert utility by the following steps:
Open Windows Command Prompt (press Windows + R and type cmd, press enter afterwards)
Type: tracert <server_address> and press enter (example: tracert 89.163.234.93)
Wait until command fully finishes. Presence of "*" as well as high values (300ms and more) in output result could be caused by problems with intermediate server. Note name of the server for corresponding line
You can copy results to clipboard by right-clicking on console -> Select All and pressing enter afterwards
Also could be useful to do regular ping to server, for this open Command Prompt and type: ping <server_address> -n 25 (example: ping 89.163.234.93 -n 25)
I checked the antivirus and firewall, and both have permission on Naval action and steam.
The ports seems all open, at least on the router, on the main modem is hardly to check, because the ISP program like a dog without paws, and that thing is harder to read, than an old egyptian comic.
I can play for 3 hours and don't have a problem, and then play for a single hour and get logged off to the logging menu 3 times. I simple click "log-in" and the game rejoin without problem(if there is no queue ), like he lose connection for half a second, get into panic mode and then calm down.
Compiled a test report on PvP One EU, number of it is: NAS-118652
And IP check and Tracert:
Tracert 89.163.234.93 on 30 points.
1 4 ms 3 ms 4 ms Home network Router
2 4 ms 4 ms 4 ms Home network ISP MOdem
3 7 ms 6 ms 8 ms net-2-32-40-1.cust.vodafonedsl.it
4 7 ms 7 ms 6 ms 83.224.40.121
5 6 ms 7 ms 6 ms 83.224.40.122
6 11 ms 11 ms 10 ms 85.205.14.101
7 18 ms 7 ms 14 ms atrato.mix-it.net [217.29.66.107]
8 25 ms 25 ms 27 ms ae02.edge01.zur01.ch.as5580.net [78.152.59.82]
9 * * * Request Dropped.
10 * * * Request Dropped..
11 24 ms 25 ms 25 ms ae01.edge01.dus01.de.as5580.net [80.94.64.133]
12 24 ms 23 ms 23 ms 78.152.32.59
13 35 ms 26 ms 23 ms ve531.ae10.brip-a.dus1-de.myloc.de [62.141.47.18
5]
14 20 ms 20 ms 20 ms 89.163.234.93
Tracks complete.
ping 89.163.234.93 -n 25
Execution of Ping 89.163.234.93 con 32 byte di dati:
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=22ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=21ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=19ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=21ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=22ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Technical problems. Reporting guide. Known issues and their solutions.
in Support
Posted
I checked the antivirus and firewall, and both have permission on Naval action and steam.
The ports seems all open, at least on the router, on the main modem is hardly to check, because the ISP program like a dog without paws, and that thing is harder to read, than an old egyptian comic.
I can play for 3 hours and don't have a problem, and then play for a single hour and get logged off to the logging menu 3 times. I simple click "log-in" and the game rejoin without problem(if there is no queue
), like he lose connection for half a second, get into panic mode and then calm down.
Compiled a test report on PvP One EU, number of it is: NAS-118652
And IP check and Tracert:
Tracert 89.163.234.93 on 30 points.
1 4 ms 3 ms 4 ms Home network Router
2 4 ms 4 ms 4 ms Home network ISP MOdem
3 7 ms 6 ms 8 ms net-2-32-40-1.cust.vodafonedsl.it
4 7 ms 7 ms 6 ms 83.224.40.121
5 6 ms 7 ms 6 ms 83.224.40.122
6 11 ms 11 ms 10 ms 85.205.14.101
7 18 ms 7 ms 14 ms atrato.mix-it.net [217.29.66.107]
8 25 ms 25 ms 27 ms ae02.edge01.zur01.ch.as5580.net [78.152.59.82]
9 * * * Request Dropped.
10 * * * Request Dropped..
11 24 ms 25 ms 25 ms ae01.edge01.dus01.de.as5580.net [80.94.64.133]
12 24 ms 23 ms 23 ms 78.152.32.59
13 35 ms 26 ms 23 ms ve531.ae10.brip-a.dus1-de.myloc.de [62.141.47.18
5]
14 20 ms 20 ms 20 ms 89.163.234.93
Tracks complete.
ping 89.163.234.93 -n 25
Execution of Ping 89.163.234.93 con 32 byte di dati:
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=22ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=21ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=19ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=21ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=22ms TTL=117
Answer from 89.163.234.93: byte=32 Duration=20ms TTL=117
Statics Ping for 89.163.234.93:
Packets: Send = 25, Received = 25,
Lost = 0 (0% lost),
Average Packets time in ms:
Min = 19ms, Max = 22ms, Average = 20ms