- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
ATT packet loss only on certain servers while gaming
Posted on 3/8/23 at 12:56 pm
Posted on 3/8/23 at 12:56 pm
I have ATT gigabit and I only get packet loss on some servers. I know it's an ATT thing bc I have a buddy in Lake Charles while I'm in BR and we both get packet loss in the exact same matches and the other two don't while having different ISP. Is there anything we can do? I already port forward.
3
Posted on 3/8/23 at 1:47 pm to Hu_Flung_Pu
quote:
I have ATT gigabit and I only get packet loss on some servers. I know it's an ATT thing bc I have a buddy in Lake Charles while I'm in BR and we both get packet loss in the exact same matches and the other two don't while having different ISP. Is there anything we can do? I already port forward.
Do some tracert commands to see all the connection segments between you and the game servers with packet loss. Then one by one, do packet loss tests to each step of the path until you find where in the run the packet loss is happening.
If the connection segment with packet loss is on at&t's network, then at&t can fix it. If the packet loss is happening on a segment outside of at&t's network, nothing you can do about it.
This post was edited on 3/8/23 at 1:48 pm
Posted on 3/8/23 at 2:22 pm to notsince98
The problem is, we don't know the IP of the server we're connected to in Call of Duty. Netstat could help, but Multiplayer is user based hosting so that could continually change depending on who is the host.
Also, ATT turns off ICMP on most of their devices so you wouldn't see the latency between each hop with tracert.
Also, ATT turns off ICMP on most of their devices so you wouldn't see the latency between each hop with tracert.
Posted on 3/8/23 at 2:36 pm to 9th Green At 9
quote:
Also, ATT turns off ICMP on most of their devices so you wouldn't see the latency between each hop with tracert.
I'm on At&t fiber. Tracert commands work just fine.
They will commonly disable echo requests on residential gateways but that wont matter in this case.
This post was edited on 3/8/23 at 2:37 pm
Posted on 3/8/23 at 2:39 pm to notsince98
quote:He has a residential gateway
They will commonly disable echo requests on residential gateways but that wont matter in this case.
Posted on 3/8/23 at 2:43 pm to notsince98
quote:
If the packet loss is happening on a segment outside of at&t's network, nothing you can do about it.
If there's an upstream problem, they will follow it up with those providers (if it's causing enough problems).
He may have to hound them a bit, but eventually they should get it fixed if he's providing tracert and ping data (when I've had such issues, I made sure to provide the date/time of my pings as well).
Posted on 3/8/23 at 2:45 pm to 9th Green At 9
quote:
He has a residential gateway
The residential gateway does not block echo requests going out to the internet. It wont respond to echo requests that originate from the internet (unless you enable response in the gateway settings).
Regardless, even if the server resides on an end user with echo response disabled, tracert will still provide all the data for each segment up to the last segment to the server. Most likely the packet loss isn't due to the server's internet connection anyway. It won't matter that you dont get a response for the very last hop.
This post was edited on 3/8/23 at 2:47 pm
Posted on 3/8/23 at 2:59 pm to notsince98
quote:That's exactly what I'm saying. They seem to have ICMP disabled on the hops immediately preceding his gateway, as they continuously time out.
(unless you enable response in the gateway settings).
quote:See the example below to google dns...
tracert will still provide all the data for each segment up to the last segment to the server.
Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 222.222.222.222
2 1 ms 1 ms 1 ms 222.com [222.22.22.22]
3 1 ms 1 ms 1 ms 222.223.223.223
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 10 ms 10 ms 10 ms dns.google [8.8.8.8]
Trace complete.
This post was edited on 3/8/23 at 3:00 pm
Posted on 3/8/23 at 4:26 pm to Hu_Flung_Pu
Happened to me many years ago on Cox. Traced to an ATT site in Dallas. People at Cox had no idea what the F I was talking about and didn't care. Good luck.
Posted on 3/8/23 at 4:41 pm to 9th Green At 9
i'm in a different area but at&t isn't blocking any echos for any hops to 8.8.8.8
for me, I think everything 12.xxxxxxx is at&t's network and 108. is the first hop off at&t network.
quote:
Tracing route to 8.8.8.8 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.68.1
2 1 ms 1 ms <1 ms 192.168.1.254
3 2 ms 2 ms 2 ms x.x.x.x
4 2 ms 2 ms 2 ms 71.150.19.34
5 16 ms 14 ms 15 ms 12.122.116.206
6 13 ms 14 ms 15 ms 12.122.28.57
7 15 ms 15 ms 15 ms 12.122.1.210
8 13 ms 12 ms 12 ms 12.123.18.125
9 15 ms 15 ms 15 ms 12.255.10.118
10 14 ms 14 ms 13 ms 108.170.225.147
11 13 ms 13 ms 13 ms 142.251.60.47
12 12 ms 12 ms 12 ms 8.8.8.8
Trace complete.
for me, I think everything 12.xxxxxxx is at&t's network and 108. is the first hop off at&t network.
This post was edited on 3/8/23 at 4:44 pm
Posted on 3/9/23 at 9:05 am to Hu_Flung_Pu
Anytime you have internet problems, let the FCC complaints fly out. Corporate gets involved. Not saying they resolve everything but you get better customer service.
Page 1 of 1
Popular
Back to top
Follow TigerDroppings for LSU Football News