Jump to content
The Lotus Eaters: Share Bug Reports and Feedback Here! ×
  • 0

Eternal Network not Responding


RBGJoe
 Share

Question

I have yet to see anyone but some southamerican players complain about this and I see no information about this anywhere (Twitter, Facebook, Forums, etc).

As far as anyone would know, servers are fine, but something IS wrong. None of the players from Chile can play or can barely play (I can play in solo mode with a lot of ping, even in the orbiter, public would just get me kicked in about 30 seconds) Game is unplayeable for me and almost a whole southamerican Warframe Facebook community that has about 5.000 members, but it seems chilean players are experiencing the most problems along with a big chunk of Argentina.

Is this happening to everyone? Is it region related? Server related? I'm I trapped in some sort of time-loop jutsu?

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

UPDATE

I've talked and researched the whole weekend and this is a Latam issue but the situation here in Chile is unbearable.
-This started with update 22.19.0 for everyone with network issues. 
-Seems to be aggravated in southamerican regions.
-It's not ISP related as people with different providers and countries are having the same problem.
-Playing through Steam solved (kinda) the problem for me but not for anyone else as far as I know.
-Keeps getting worse every day, I can't even go past the loading of the regular launcher now.
-Cleaning all files, fresh-installing, using a new hhd/ssd or even a new PC has no impact at all.
-Steam forums are also presenting this kind of threads.
-I can play heavy network and hardware demanding games just fine, as everyone else, Warframe keeps not responding.
-Some people (like 30%) can't even update.
-Rewards from relics, leveling, mission progress in general is being lost when "network not responding" pops at extraction.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

UPDATE 2.0

-Warframe in my personal and gaming networks are trying to run through stealthed ports that ISPs won't open (I don't know why, I would have released them as they pose no threat) they'll just trigger TCP 80 to UDP 8080 and tell you it's done.
-Nothing is running under 4950 and 4955, as stablished by me in-game (as default). Warframe actively avoid ports specified by players in-game and if you try and run other games trough there, they have no problems at all, only Warframe.
-DMZ has no effect nor does stripping your computer and network naked and vulnerable.
-Range of Warframe's active ports is way to high to run like it should.
-DHCP messes up the network even more (it shouldn't).
-Forced Warframe back to the ports it was using before Kohra's realease and now I have 0 issues, even with regular launcher, which would not go past the "checking for new content" before this workaround.

I made it but this is not a solution. Most people won't even know what I'm talking about, they still need an answer and I can't do this to 5.000 computers nor should I (and that's just the guys from the Facebook community I'm talking about, there are many more). Hope you guys can help them out so I can release your .exe back into the wild and play like I used to before Khora.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


I Believe this dates back to Khora's release, because ever since I've yet to play for an hour without seeing that message but it had no impact on gameplay at all. Now... now it's different.

I've lost 4 days of proper boosters that I hope to get back.

I thank everyone in this thread and DE as a whole and really wish to get an answer soon 🙂 see you on monday, have a great day, everyone.

Edited by RBGJoe
Link to comment
Share on other sites

Recommended Posts

  • 0

I checked with netstat -ab and got this resuts for warframe.

 

Spoiler

 [Warframe.x64.exe]
  TCP    192.168.0.16:53707     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53708     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53709     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53710     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53711     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53712     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53713     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53714     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53715     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53716     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53719     a104-114-237-110:https  ESTABLISHED
 [Warframe.x64.exe]
  TCP    192.168.0.16:53720     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53721     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53722     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53723     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53724     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53725     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53726     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53727     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53728     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53732     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53733     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53734     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53735     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53736     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53737     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53738     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53739     192.168.0.1:5000       TIME_WAIT
 TCP    192.168.0.16:53740     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53741     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53742     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53743     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53744     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53745     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53746     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53747     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53748     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53749     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53750     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53751     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53752     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53753     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53754     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53755     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53756     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53757     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53758     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53759     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53760     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53761     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53762     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53763     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53764     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53765     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53766     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53767     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53768     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53769     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53770     192.168.0.1:5000       TIME_WAIT
  

Then i checked some of the ports on https://www.yougetsignal.com/tools/open-ports/ and the result are this

Spoiler

Port 53707 is closed

 Port 53720 is closed

Port 53747 is closed

Seems that the whole range of ports used by warframe is closed.

 

Link to comment
Share on other sites

  • 0
hace 14 minutos, Neoluzbell dijo:

I checked with netstat -ab and got this resuts for warframe.

 

  Revelar contenido oculto

 [Warframe.x64.exe]
  TCP    192.168.0.16:53707     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53708     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53709     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53710     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53711     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53712     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53713     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53714     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53715     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53716     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53719     a104-114-237-110:https  ESTABLISHED
 [Warframe.x64.exe]
  TCP    192.168.0.16:53720     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53721     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53722     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53723     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53724     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53725     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53726     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53727     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53728     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53732     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53733     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53734     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53735     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53736     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53737     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53738     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53739     192.168.0.1:5000       TIME_WAIT
 TCP    192.168.0.16:53740     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53741     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53742     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53743     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53744     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53745     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53746     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53747     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53748     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53749     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53750     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53751     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53752     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53753     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53754     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53755     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53756     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53757     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53758     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53759     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53760     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53761     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53762     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53763     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53764     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53765     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53766     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53767     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53768     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53769     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53770     192.168.0.1:5000       TIME_WAIT
  

Then i checked some of the ports on https://www.yougetsignal.com/tools/open-ports/ and the result are this

  Ocultar contenido

Port 53707 is closed

 Port 53720 is closed

Port 53747 is closed

Seems that the whole range of ports used by warframe is closed.

 

Test using the same web with ur open ports xddd

Link to comment
Share on other sites

  • 0
hace 21 minutos, Neoluzbell dijo:

I checked with netstat -ab and got this resuts for warframe.

 

  Ocultar contenido

 [Warframe.x64.exe]
  TCP    192.168.0.16:53707     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53708     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53709     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53710     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53711     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53712     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53713     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53714     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53715     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53716     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53719     a104-114-237-110:https  ESTABLISHED
 [Warframe.x64.exe]
  TCP    192.168.0.16:53720     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53721     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53722     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53723     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53724     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53725     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53726     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53727     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53728     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53732     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53733     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53734     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53735     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53736     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53737     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53738     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53739     192.168.0.1:5000       TIME_WAIT
 TCP    192.168.0.16:53740     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53741     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53742     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53743     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53744     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53745     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53746     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53747     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53748     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53749     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53750     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53751     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53752     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53753     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53754     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53755     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53756     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53757     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53758     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53759     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53760     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53761     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53762     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53763     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53764     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53765     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53766     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53767     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53768     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53769     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53770     192.168.0.1:5000       TIME_WAIT
  

Then i checked some of the ports on https://www.yougetsignal.com/tools/open-ports/ and the result are this

  Ocultar contenido

Port 53707 is closed

 Port 53720 is closed

Port 53747 is closed

Seems that the whole range of ports used by warframe is closed.

 

I just called my ex-boss (yes, I worked at VTR as a backoffice IT [I also worked at Movistar, which is not working either for me]) He assures that there is no problem originating from their side.

As the guy above says, I must be on some havy stuff then.

Anyway, I'll just wait 'till tomorrow.

Edited by RBGJoe
Link to comment
Share on other sites

  • 0
hace 2 minutos, RBGJoe dijo:

I just called my ex-boss (yes, I worked at VTR as a backoffice IT [I also worked at Movistar, which is not working ether for me]) He assures that there is no problem originating from their side.

As the guy above says, I must be on some havy stuff then.

Anyway, I'll just wait 'till tomorrow.

 

it's better to wait, I dont think the hackerman fix the problem

Link to comment
Share on other sites

  • 0
2 hours ago, Dark_Salamander said:

If this is true, then, the people from another companies with other companies OR in other countries are just mad or maybe in drugs? xD

Bro, the "Network Not Responding" Issue is Regional, not from a country or a specific zone in that country.

Im not claiming that the whole problem is just VTR Chile, neither am I saying that the solution is to change ISP or open ports on our end.

Im just stating, as comprehensible as possible, my experience in the hopes that we can reach a solution ASAP

 

My personal experience so far says

 - VTR doesn't work on multiple pcs and 2 different houses (1 located in reñaca and the other in valparaiso)

 - Trying to log in (with the same laptop that cant log) from work, using movistar wifi, works fine

 - Trying to log in, from the same laptop, using my cellphone's dataplan (WOM) works fine, although a little laggy,but no network/dcs issues and no crashes or frozen launcher.

 

Obviously this leads me to think that VTR is the source of the issue, I just spoke with a friend who also has VTR (from Valdivia) and he can log in just fine, also, I'm not trying to say the people from other regions/ISPs are lying, I'm just stating my personal situation.

 

If you can help giving information regarding this issue, it would be appreciated, otherwise there's no point in quoting me.

Link to comment
Share on other sites

  • 0
Hello, I'm from Chile and I want to inform you that I have connection problems with Warframe days ago, the problem is not the ISP since everything else works very well, and now even if the game does not start, please do something
Link to comment
Share on other sites

  • 0
hace 4 horas, peter4078 dijo:

it's better to wait, I dont think the hackerman fix the problem

I'm sorry if I made a mistake, I still have so much to learn. On the other hand, you should not shame yourself with your poor english in a forum like this. Try google translator 😉

Link to comment
Share on other sites

  • 0
hace 5 horas, Neoluzbell dijo:

I checked with netstat -ab and got this """resuts"""" for warframe.

 

  Revelar contenido oculto

 [Warframe.x64.exe]
  TCP    192.168.0.16:53707     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53708     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53709     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53710     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53711     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53712     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53713     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53714     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53715     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53716     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53719     a104-114-237-110:https  ESTABLISHED
 [Warframe.x64.exe]
  TCP    192.168.0.16:53720     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53721     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53722     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53723     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53724     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53725     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53726     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53727     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53728     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53732     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53733     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53734     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53735     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53736     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53737     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53738     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53739     192.168.0.1:5000       TIME_WAIT
 TCP    192.168.0.16:53740     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53741     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53742     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53743     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53744     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53745     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53746     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53747     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53748     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53749     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53750     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53751     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53752     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53753     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53754     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53755     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53756     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53757     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53758     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53759     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53760     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53761     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53762     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53763     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53764     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53765     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53766     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53767     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53768     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53769     192.168.0.1:5000       TIME_WAIT
  TCP    192.168.0.16:53770     192.168.0.1:5000       TIME_WAIT
  

Then i checked some of the ports on https://www.yougetsignal.com/tools/open-ports/ and the result are this

  Revelar contenido oculto

Port 53707 is closed

 Port 53720 is closed

Port 53747 is closed

Seems that the whole range of ports used by warframe is closed.

 

oks

Edited by peter4078
Link to comment
Share on other sites

  • 0

Hi guys! Well I ll tell you my own experience: 
ISP: Movistar 300 mb/ fiber optic
No problems at all. One of my friends come to my house and could play as well without any issue.

Link to comment
Share on other sites

  • 0

Hi everyone, i have the same issue. Im from Chile too and have VTR.

 

Edit: My friends have the same issue (they have VTR at home), one of them tried with Movistar and had the same issues.

Edited by ReinAxefury
Link to comment
Share on other sites

  • 0
7 hours ago, Dyoku said:

Hi guys! Well I ll tell you my own experience: 
ISP: Movistar 300 mb/ fiber optic
No problems at all. One of my friends come to my house and could play as well without any issue.

same here, Btw Brazil Sao Paulo, it's being a long time since i had any network problems.
ISP - Life Telecom - 100mbps

we around here, me and my friends from another towns around, also have not being getting any errors or problems with that at all. 

Edited by -.SP.-G43riel
Link to comment
Share on other sites

  • 0
5 minutes ago, Dark_Salamander said:

Guys, just stop #*!%ing arround with "I have VTR/Movistar/any provider of net". The companies doesn't have anything to do here. In the first post is the reason (Yes, he updated the post to give you all the info)

Gotcha, i just read the update from OP. Then what's next? just wait? Is there any way to draw DE's attention to this issue?

Link to comment
Share on other sites

  • 0

Hi been having this problem last 2 week Network not Responding DE told me it was my Antivirus which its not, the worst time is when i go to Trading and enter the dojo Network Not Responding comes up ang logs me out the game and some Times when i log in to Warframe iam from New Zealand 

Edited by Freelancerxx
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...