Jump to content

Recommended Posts

Sooo.....how should i say this. I can't connect anymore to the Zombie Escape server. I was able to do so a few days ago, but now i can't anymore. I can't add it to the favorites, i can't connect with the console. After 30 retries, it stops. i tryed to fix it with the run as administrator and in cmd.exe to reset my ip and such, reboot of the pc and steam, and.........NOTHING. i must say I tried to add a different server, and added the surf one, and that one works.

 

Can you guys help me please? Any suggestions.

Share this post


Link to post
Share on other sites

I wish it was that. But it doesn't even appear anymore in the favorites, I can't connect to it directly through console. After 30 retries, it stops. I can connect to the surf one, but not ze. I even deleted and installed Cs go again, checked the file integrity...... Nothing. 

Share this post


Link to post
Share on other sites

Sometimes the server null routes certain groups of IPs to protect itself from things like DDOS. Other times, it might be your Internet Service Provider preventing you from connecting to this IP. When this happens, it is completely out of our hands.

 

You could always try and restart your router first to see if that may help. If not, then the only other thing you can do is wait until it clears up. 

  • Thanks 1

Share this post


Link to post
Share on other sites

Along with what @reduct said, have you tried running a trace route to the Zombie Escape server yet? You can run a trace route by using

tracert 216.52.148.47

in windows command prompt. It should give you a idea if it's NFO (our host for ze) or your ISP responsible for the connection issue you're having.

  • Thanks 1

Share this post


Link to post
Share on other sites

Microsoft Windows [Version 10.0.17134.765]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\Andy>tracert 216.52.148.47

Tracing route to c-216-52-148-47.managed-ded.premium-chicago.nfoservers.com [216.52.148.47]
over a maximum of 30 hops:

  1    <1 ms     6 ms     1 ms  192-168-0-1.rdsnet.ro [192.168.0.1]
  2     4 ms     1 ms     3 ms  10.0.0.1
  3    12 ms     4 ms     5 ms  10.52.1.9
  4    36 ms    48 ms    38 ms  xr01.londra.rdsnet.ro [10.220.134.206]
  5    36 ms    37 ms    40 ms  ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]
  6    43 ms    42 ms    41 ms  zayo-ntt.mpr1.lhr15.uk.zip.zayo.com [64.125.12.102]
  7    37 ms    36 ms    36 ms  ae-3.r24.londen12.uk.bb.gin.ntt.net [129.250.4.23]
  8   105 ms   106 ms   104 ms  ae-5.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.18]
  9   114 ms   113 ms   117 ms  ae-1.r25.nycmny01.us.bb.gin.ntt.net [129.250.3.207]
 10   128 ms   139 ms   131 ms  ae-1.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
 11   130 ms   128 ms   129 ms  ae-12.r08.chcgil09.us.bb.gin.ntt.net [129.250.2.190]
 12   127 ms   123 ms   126 ms  ae-31.a00.chcgil09.us.bb.gin.ntt.net [129.250.3.159]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 

And this what it shows me....i will try to reset the router now and come back with an edit...

 

EDIT. After the router reset, i did the tracert again, and after 14 hops it finished. And the server works again for me. Now i will know what to do in case it happens again.

Thanks again for the help. See on guys on.

 

 

Edited by PhySx
  • Thanks 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...