Ichinisan
Lifer
I work for a local cable ISP. Recently, multiple cases have been escalated where customers playing Ubisoft's "The Division" on PS4 cannot connect. They get a vague error code that doesn't provide any useful information: "Delta C-1-198"
Our network engineer goes on a week-long Christmas vacation starting tomorrow. I'm also taking a vacation day tomorrow (a use-it-or-lose-it situation). I hoped to have this resolved today since it has been going on for over a week.
The issue started when players installed an update to version 1.5, but here's where it gets strange: Affected players can switch the same console to a different ISP (mobile hotspot, friend/family/neighbor) and the game works online.
Ubisoft suggested the customers call us and perform a trace-route, but they didn't tell us where we should trace a route to. I would need a server hostname or IP address. I agree that a trace-route test should be performed to determine why our customers can't reach Ubisoft's server.
I have tried contacting Ubisoft tech support myself, but they tell me they cannot provide that information. A later update said a trace-route would not help (I disagree). They are trying to close the ticket without providing any suggestion on how we should proceed. Ubisoft will keep referring customers to their ISP and they will keep getting escalated to me.
I found a thread on Ubisoft's forums about this error and confirmed that a significant portion of the thread participants live in my city and use my employer for their ISP -- including the OP of that thread.
So I plan to bring my new PS4 Pro to the office tomorrow (even though it's a vacation day for me). A call center supervisor will bring his copy of The Division. We'll probably need to create a PS4 user for him and sign-in to his Playstation Plus account (I don't have one). Then we'll need to rig up a PC with 2 network interfaces and a software tool to analyze data packets. We'll connect it all through a cable modem (same CMTS as one of the affected users I've been helping).
Can someone suggest a software package for Windows to help analyze traffic that is simple enough to figure out?
Hopefully such a tool can show failed DNS look-ups and TCP/IP client-server connections (or UDP).
Thanks!
[2016-12-26 EDIT]
Holidays have delayed any further progress on this. I'm fairly certain there is a BGP issue with a route upstream from us, affecting some (but not all) other ISPs. I suspect this other inaccessible host could be related...
A couple people have contacted me because they are unable to reach a server on nfoservers.com and one confirmed it works when he uses a VPN tunnel, which would force a different route to the server. When speaking with the other affected customer, I mentioned that I've had 2 couple similar issues in the past (a customer was unable to reach a particular server that was reachable via another ISP), each around 1 year apart. Those were found to be caused by another network, upstream from us, advertising BGP routes incorrectly. In both of those previous cases, the operator of the offending network was notified and the issue was resolved. When I mentioned BGP, he perked-up and confirmed that an nfoservers.com support rep said it could be a BGP issue causing connection problems in the south-east. The nfoservers.com rep had also suggested he should try "TunnelBear" free VPN service. I told him I'd pass along anything our network engineers find, but I expect their response to be delayed due to holidays. He said he would try getting TunnelBear to work.
I had an angry voicemail from Saturday, Christmas Eve. He seemed to think I had suggested TunnelBear, but it was actually the nfoservers.com rep that suggested it to him. He was frustrated because he couldn't get the TunnelBear software to install (requires some version of .NET framework and he doesn't know where/how to get that).
While I have to wait for a response from our network engineers to determine if there is a BGP / routing issue with any of the hosts I've listed, I thought I might be able to look into it.
I found this article:
http://www.techrepublic.com/article/how-to-use-ip-and-bgp-to-troubleshoot-internet-connectivity/
Well, it's not much help. The example looking glass server they suggest (BBC) is "down for maintenance," but I used another and found our ASN.
Then, it suggests using telnet to route-views.oregon-ix.net -- but it prompts for authentication credentials, which the article does not provide. I tried using "anonymous" with a blank password and it fails.
Our network engineer goes on a week-long Christmas vacation starting tomorrow. I'm also taking a vacation day tomorrow (a use-it-or-lose-it situation). I hoped to have this resolved today since it has been going on for over a week.
The issue started when players installed an update to version 1.5, but here's where it gets strange: Affected players can switch the same console to a different ISP (mobile hotspot, friend/family/neighbor) and the game works online.
Ubisoft suggested the customers call us and perform a trace-route, but they didn't tell us where we should trace a route to. I would need a server hostname or IP address. I agree that a trace-route test should be performed to determine why our customers can't reach Ubisoft's server.
I have tried contacting Ubisoft tech support myself, but they tell me they cannot provide that information. A later update said a trace-route would not help (I disagree). They are trying to close the ticket without providing any suggestion on how we should proceed. Ubisoft will keep referring customers to their ISP and they will keep getting escalated to me.
I found a thread on Ubisoft's forums about this error and confirmed that a significant portion of the thread participants live in my city and use my employer for their ISP -- including the OP of that thread.
So I plan to bring my new PS4 Pro to the office tomorrow (even though it's a vacation day for me). A call center supervisor will bring his copy of The Division. We'll probably need to create a PS4 user for him and sign-in to his Playstation Plus account (I don't have one). Then we'll need to rig up a PC with 2 network interfaces and a software tool to analyze data packets. We'll connect it all through a cable modem (same CMTS as one of the affected users I've been helping).
Can someone suggest a software package for Windows to help analyze traffic that is simple enough to figure out?
Hopefully such a tool can show failed DNS look-ups and TCP/IP client-server connections (or UDP).
Thanks!
[2016-12-26 EDIT]
Holidays have delayed any further progress on this. I'm fairly certain there is a BGP issue with a route upstream from us, affecting some (but not all) other ISPs. I suspect this other inaccessible host could be related...
A couple people have contacted me because they are unable to reach a server on nfoservers.com and one confirmed it works when he uses a VPN tunnel, which would force a different route to the server. When speaking with the other affected customer, I mentioned that I've had 2 couple similar issues in the past (a customer was unable to reach a particular server that was reachable via another ISP), each around 1 year apart. Those were found to be caused by another network, upstream from us, advertising BGP routes incorrectly. In both of those previous cases, the operator of the offending network was notified and the issue was resolved. When I mentioned BGP, he perked-up and confirmed that an nfoservers.com support rep said it could be a BGP issue causing connection problems in the south-east. The nfoservers.com rep had also suggested he should try "TunnelBear" free VPN service. I told him I'd pass along anything our network engineers find, but I expect their response to be delayed due to holidays. He said he would try getting TunnelBear to work.
I had an angry voicemail from Saturday, Christmas Eve. He seemed to think I had suggested TunnelBear, but it was actually the nfoservers.com rep that suggested it to him. He was frustrated because he couldn't get the TunnelBear software to install (requires some version of .NET framework and he doesn't know where/how to get that).
While I have to wait for a response from our network engineers to determine if there is a BGP / routing issue with any of the hosts I've listed, I thought I might be able to look into it.
I found this article:
http://www.techrepublic.com/article/how-to-use-ip-and-bgp-to-troubleshoot-internet-connectivity/
Well, it's not much help. The example looking glass server they suggest (BBC) is "down for maintenance," but I used another and found our ASN.
Then, it suggests using telnet to route-views.oregon-ix.net -- but it prompts for authentication credentials, which the article does not provide. I tried using "anonymous" with a blank password and it fails.
Last edited: