Jump to content
Dante Unbound: Known Issues ×
Dante Unbound: Share Bug Reports and Feedback Here! ×

Keep disconnecting due to unable to connect


(PSN)Matoic

Recommended Posts

THAT MAKES PERFECT SENSE! Okay, let's do a little testing... and CONFIRMED!

|||FIX FOUND||||
\/\/\/\/\/\/\/\/\/

So, Spectrum's Nameservers are absolutely buggered! All you have to do is change your DNS.
The best way to do this is to log into your router, go to the WAN section and look for two boxes labeled:

Primary DNS __________

Secondary DNS ________

Once you find those, all you have to do is put in the addresses of the DNS you want to use. You can use any DNS you want, but I'll tell you what worked for me.
I used Google's DNS.

Primary DNS: 8.8.8.8
Secondary DNS: 8.8.4.4

Save your settings, and BAM! You've got it!
This fix will work for both Console and PC.

PC Users, you can change this via OS Settings, but this is a far cleaner way and will work for all your devices.

SUCK IT, SPECTRUM!

Link to comment
Share on other sites

 

9 minutes ago, Chuck_Burlap said:

THAT MAKES PERFECT SENSE! Okay, let's do a little testing... and CONFIRMED!

|||FIX FOUND||||
\/\/\/\/\/\/\/\/\/

So, Spectrum's Nameservers are absolutely buggered! All you have to do is change your DNS.
The best way to do this is to log into your router, go to the WAN section and look for two boxes labeled:

Primary DNS __________

Secondary DNS ________

Once you find those, all you have to do is put in the addresses of the DNS you want to use. You can use any DNS you want, but I'll tell you what worked for me.
I used Google's DNS.

Primary DNS: 8.8.8.8
Secondary DNS: 8.8.4.4

Save your settings, and BAM! You've got it!
This fix will work for both Console and PC.

PC Users, you can change this via OS Settings, but this is a far cleaner way and will work for all your devices.

SUCK IT, SPECTRUM!

Already did this, can confirm this did not fix the issue for me

Link to comment
Share on other sites

I only did ipv4. I'm not super tech savvy so the steps I did was settings>network and internet>change adapter options>right click properties on my connection>IPV4 properties>Use the following dns server and typed in googles. So right now my preferred DNS is 8.8.8.8 and alternate DNS is 8.8.4.4. Still getting the errors.

Also I called spectrum and they said it was on Warframes end since I was getting the error from both google and spectrums dns. So now we are at the point where Warframe is saying it's spectrum's problem and spectrum is saying its Warframe's problem and nothing is getting done.

Link to comment
Share on other sites

@MikeDub The fact that it is only us, means it is Spectrum's fault and their nameserver. Here's a good way to confirm you have it set up correctly:
Go to this site: https://www.top10vpn.com/tools/what-is-my-dns-server/ and use the tool.

If you see:
 

US GOOGLE - Google LLC 172.253.7.66
US GOOGLE - Google LLC 172.253.242.34
US GOOGLE - Google LLC 172.253.242.43
US GOOGLE - Google LLC 2607:f8b0:400c:c11::111
US GOOGLE - Google LLC 2607:f8b0:400c:c0a::104
US GOOGLE - Google LLC 2607:f8b0:400c:c02::10

 

Then your DNS is set up correctly.

Link to comment
Share on other sites

57 minutes ago, Chuck_Burlap said:

THAT MAKES PERFECT SENSE! Okay, let's do a little testing... and CONFIRMED!

|||FIX FOUND||||
\/\/\/\/\/\/\/\/\/

So, Spectrum's Nameservers are absolutely buggered! All you have to do is change your DNS.
The best way to do this is to log into your router, go to the WAN section and look for two boxes labeled:

Primary DNS __________

Secondary DNS ________

Once you find those, all you have to do is put in the addresses of the DNS you want to use. You can use any DNS you want, but I'll tell you what worked for me.
I used Google's DNS.

Primary DNS: 8.8.8.8
Secondary DNS: 8.8.4.4

Save your settings, and BAM! You've got it!
This fix will work for both Console and PC.

PC Users, you can change this via OS Settings, but this is a far cleaner way and will work for all your devices.

SUCK IT, SPECTRUM!

I actually changed my DNS on my ps5 and so far so good

Link to comment
Share on other sites

I haven't changed the ipv6 yet so I just gave that a go. Maybe that will fix the issue with the disconnects. I put it as googles but whenever I refresh that website the checks your DNS I will get a random combination of google and bright house network addresses. Sometimes it'll be both google address, sometimes it will be 2 bright house and 1 google, sometimes no google address so now I have no idea what's going on.

Edit: Still getting log out error

Edit 2: after flushing dns I am only getting google to pop up on the test your dns website but am still receiving errors in Warframe. 

Link to comment
Share on other sites

@MikeDub Okay, Hail Mary play here. Run Command prompt as admin and run the following code:

wmic nicconfig where DHCPEnabled=TRUE call SetDNSServerSearchOrder ("8.8.8.8","8.8.4.4")

That will force your system to use Google's DNS.
If that doesn't work, you'll need to contact your apartment complex's tech.

Link to comment
Share on other sites

After trying the code entered I am still getting these disconnects. Ill just have to wait and see what Warframe support says. Really thought the problem was gone when I made it through the second mission of the archon hunt lol appreciate you trying to help.

Link to comment
Share on other sites

9 minutes ago, (XBOX)C11H22O11 said:

Heard it's an issue specific to Florida, not sure what's going on there.

Also is Ridiculous censored? *I guess not, you probably put a k next to the c

I don't know I am in Florida and am not experiencing any issues, not that that means a lot. But I have friends in a couple other places in Florida, and none of them seem to be having issues.

Link to comment
Share on other sites

We've been able to narrow down the issue and can confirm this is a problem with a specific ISP.

If you have a PC you can confirm that you have this problem by:

  • Opening a command prompt and typing “nslookup api.warframe.com” 
    • if it reports 23.40.172.184 as one of the addresses, your DNS server is returning stale information and is effected. 
  • Unfortunately it seems there is a pool of addresses returned and you may not see the bad one immediately (this is why the game can sometimes work but then will fail at random).
  • Tip: press the up arrow and then enter to re-run the same command a few times – in normal circumstances the addresses resolved might change every 20 seconds or so.

As others have pointed out in this thread there is a workaround: you don’t have to use the DNS servers provided by your ISP. You can switch to a free DNS server locally on your PC, console or on your home router: 

One issue we encountered with overriding your ISP’s DNS server, however, is that it appears this ISP specifies IPv6 DNS servers as well – we’re still investigating but in some cases changing the IPv4 DNS settings didn’t work until either IPv6 was disabled or the IPv6 settings were changed in tandem with the IPv4 settings.

Sadly, this is not the first time we’ve had this problem: in February we saw the same issue with this ISP. For some reason their DNS servers are returning stale addresses and ignoring the 20-second expiry we specify and have been returning a value that changed almost a week ago.

The last time our network partners were able to rearrange some equipment so that the stale address returned by the ISP’s DNS server still worked but unfortunately this is not possible this time. Our network partners are trying to reach out to this ISP to tell them about their misconfiguration but since we aren’t their customers this has not been effective.

We’re currently waiting to hear back from our network partner about their efforts to contact this ISP however if you want to try to contact your ISP yourself the key things to tell them are:

  1. Their DNS servers are sometimes returning stale addresses for api.warframe.com (and probably others)
  2. Specifically it should not resolve to 23.40.172.184
  3. This is not a problem for millions of people on connecting through different ISPs.
  4. Other customers impacted by this have successfully switched DNS servers to work around this problem.

Thank you to those who have attempted to help other Tenno to find solutions in the meantime, hopefully the issue will be fixed soon but for now this is a solution that we can use. 

Link to comment
Share on other sites

Hey there, we've identified the issue and provided a work-around while the issue is still persisting, you can find a fix here: 
 

3 minutes ago, [DE]Glen said:

We've been able to narrow down the issue and can confirm this is a problem with a specific ISP.

If you have a PC you can confirm that you have this problem by:

  • Opening a command prompt and typing “nslookup api.warframe.com” 
    • if it reports 23.40.172.184 as one of the addresses, your DNS server is returning stale information and is effected. 
  • Unfortunately it seems there is a pool of addresses returned and you may not see the bad one immediately (this is why the game can sometimes work but then will fail at random).
  • Tip: press the up arrow and then enter to re-run the same command a few times – in normal circumstances the addresses resolved might change every 20 seconds or so.

As others have pointed out in this thread there is a workaround: you don’t have to use the DNS servers provided by your ISP. You can switch to a free DNS server locally on your PC, console or on your home router: 

One issue we encountered with overriding your ISP’s DNS server, however, is that it appears this ISP specifies IPv6 DNS servers as well – we’re still investigating but in some cases changing the IPv4 DNS settings didn’t work until either IPv6 was disabled or the IPv6 settings were changed in tandem with the IPv4 settings.

Sadly, this is not the first time we’ve had this problem: in February we saw the same issue with this ISP. For some reason their DNS servers are returning stale addresses and ignoring the 20-second expiry we specify and have been returning a value that changed almost a week ago.

The last time our network partners were able to rearrange some equipment so that the stale address returned by the ISP’s DNS server still worked but unfortunately this is not possible this time. Our network partners are trying to reach out to this ISP to tell them about their misconfiguration but since we aren’t their customers this has not been effective.

We’re currently waiting to hear back from our network partner about their efforts to contact this ISP however if you want to try to contact your ISP yourself the key things to tell them are:

  1. Their DNS servers are sometimes returning stale addresses for api.warframe.com (and probably others)
  2. Specifically it should not resolve to 23.40.172.184
  3. This is not a problem for millions of people on connecting through different ISPs.
  4. Other customers impacted by this have successfully switched DNS servers to work around this problem.

Thank you to those who have attempted to help other Tenno to find solutions in the meantime, hopefully the issue will be fixed soon but for now this is a solution that we can use. 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...