First thing to do is opend you cmd (click on the windows button and write in the text box) cmd and hit enter. New window will come up and follow the steps below.
First you want to ping 127.0.0.1. That's yourself. You should always get a response and there should be no packet loss.
C:\Windows\system32>ping 127.0.0.1
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Second step is to ping you router, most common ip to the router is 192.168.1.1
But if you are unsure its easy to find out.
C:\Windows\system32>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : home
Link-local IPv6 Address . . . . . : fe80::cc60:cfe8:706d:1eff%13
IPv4 Address. . . . . . . . . . . : 192.168.1.6
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1 (this is your router ip)
Tunnel adapter isatap.home:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : home
Tunnel adapter IP6Tunnel:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
C:\Windows\system32>
Okey, now we know our ip to the router, and it was 192.168.1.1.
Third step is to ping our ip.
Write C:\Windows\system32>ping 192.168.1.1.
Providing you haven't had issues with either of these steps then at this point your local network connections should be fine.
Fourth Step:
How do i find the server IP
Go to http://www.arrstatus.com/ hold you mouse button over that server you are on and the Ip will show.
Fifth step is to do a Traceroute:
C:\Windows\system32>pathping (and the server ip that you are playing on) hit enter
This wil show up then, uplode this to the forums. To comfirm the problem you are having.
0 PC.lan [10.0.0.1]
1 10.0.0.138
2 * ti0089a340-l100.ti.telenor.net [148.122.176.9
3 ti0050d320-ge0-1-1-10.ti.telenor.net [146.172.91.17]
4 ti0050c400-xe8-0-2.ti.telenor.net [146.172.98.173]
5 ti0024c400-ae4-0.ti.telenor.net [146.172.98.30]
6 ti0005c400-ae7-0.ti.telenor.net [146.172.98.130]
7 * ti0001c360-ae2-0.ti.telenor.net [146.172.100.
8 ti0001b400-ae1-0.ti.telenor.net [146.172.105.66]
9 te3-7.ccr01.osl01.atlas.cogentco.com [130.117.14.21]
10 te0-17-0-3.ccr41.ham01.atlas.cogentco.com [130.117.2.1
11 be2188.mpd21.ams03.atlas.cogentco.com [154.54.74.129]
12 multi-use.cogentco.com [154.54.62.145]
13 be2283.ccr21.lpl01.atlas.cogentco.com [130.117.49.34]
14 te0-4-0-3.ccr21.ymq02.atlas.cogentco.com [154.54.44.20
15 38.122.42.34
16 * * *
Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 PC.
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.138
0/ 100 = 0% |
2 31ms 0/ 100 = 0% 0/ 100 = 0% ti0089a340-l1
8.122.176.90]
0/ 100 = 0% |
3 --- 100/ 100 =100% 100/ 100 =100% ti0050d320-ge
et [146.172.91.17]
0/ 100 = 0% |
4 --- 100/ 100 =100% 100/ 100 =100% ti0050c400-xe
[146.172.98.173]
0/ 100 = 0% |
5 --- 100/ 100 =100% 100/ 100 =100% ti0024c400-ae
46.172.98.30]
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% ti0005c400-ae
46.172.98.130]
0/ 100 = 0% |
7 --- 100/ 100 =100% 100/ 100 =100% ti0001c360-ae
46.172.100.121]
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% ti0001b400-ae
46.172.105.66]
0/ 100 = 0% |
9 84ms 2/ 100 = 2% 2/ 100 = 2% te3-7.ccr01.o
om [130.117.14.21]
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% te0-17-0-3.cc
tco.com [130.117.2.177]
0/ 100 = 0% |
11 96ms 0/ 100 = 0% 0/ 100 = 0% be2188.mpd21.
com [154.54.74.129]
0/ 100 = 0% |
12 95ms 0/ 100 = 0% 0/ 100 = 0% multi-use.cog
145]
0/ 100 = 0% |
13 103ms 0/ 100 = 0% 0/ 100 = 0% be2283.ccr21.
com [130.117.49.34]
0/ 100 = 0% |
14 181ms 0/ 100 = 0% 0/ 100 = 0% te0-4-0-3.ccr
co.com [154.54.44.205]
0/ 100 = 0% |
15 176ms 0/ 100 = 0% 0/ 100 = 0% 38.122.42.34
And the last step:
- Make sure your network controller drivers are updated.
- Reset your router back to factory specifications. (contact ISP if you dont know how to do it)
- Reboot the router. Turn it off, wait about 30 to 60 seconds then turn it back on.
- Reboot your computer next.
- If you have a cable modem or are a verizon FiOS customer with verizon TV you will want to make sure all the coaxial connections are tight. This includes any connections you have to televisions, cable boxes, cable modems and splitters.
- You may also want to disable any and all firewall or internet security software temporarily before retesting your connection. Some software like Norton and McAfee will pass all internet information through themselves before passing it on to the internet or allowing it in to you. This software looks at all that information and analyzes it first.
- Finally, turn off any other programs that communicate with the internet.
Quick guide to see if the problem is on the players end or it is a server problem.