Jump to content
 Share

OxideTM

Can't connect to CS:GO ZE

Recommended Posts

Hey,

 

So I can't connect to CS:GO ZE. I haven't tried it out before so I was thinking to try it now but the server isn't responding. Tried to connect manually through console but failed to reconnect after 30 retries. I don't know why but for 2  3 days I can't also connect to a CS 1.6 server where I play. I can't even access that server's site. By the way, that 1.6 server and site is hosted on nfo. 

 

I will appreciate if someone helps me out with this.

 

Thank you,

Share this post


Link to post
Share on other sites


Can you try performing a trace route to the server's IP with the following command (Windows Command Prompt):

 

tracert 216.52.148.47

 

Paste the results back here. With that said, can you private message me your IPv4 address which can be found here. I'd like to perform a trace route from the NFO server to your IP.

 

If it does time out, try pinging another IP from NFO's Chicago location. Example:

 

ping 74.91.119.54

 

Please let me know how it goes.

 

Thanks.

Share this post


Link to post
Share on other sites


In addition to my last reply, we had a case recently where NFO blocked a player's IP on the firewall level due to something on their network/device performing port scans on NFO's IPs. This isn't allowed.

 

This may be the same case depending on the results and I would have to open a ticket with NFO to confirm.

 

I would recommend performing scans for viruses, malware, etc. on your device if possible. There is a possibility you have a virus doing this behind the scenes.

 

Thanks.

Share this post


Link to post
Share on other sites


On 11/15/2018 at 10:21 AM, Roy said:

tracert 216.52.148.47

 

C:\Windows\system32>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          8 ms        4 ms        5 ms       192.168.0.1
  2      118 ms        13 ms     32 ms       172.19.63.255
  3        10 ms        7 ms             *        202.163.100.85
  4         3 ms         3 ms       4 ms      202.163.100.66
  5         4 ms         3 ms        3 ms      119.159.240.53
  6         6 ms         5 ms        9 ms      khi77.pie.net.pk [221.120.251.205]
  7         9 ms         3 ms        5 ms      static.khi77.pie.net.pk [202.125.128.171]
  8     108 ms     108 ms    109 ms      te0-4-0-27.ccr21.mrs01.atlas.cogentco.com [149.14.126.1]
  9     108 ms       111 ms     114 ms      be3092.ccr41.par01.atlas.cogentco.com [130.117.49.153]
 10      116 ms      115 ms     116 ms      prs-b2-link.telia.net [213.155.141.226]
 11     224 ms     224 ms    235 ms     prs-bb3-link.telia.net [62.115.122.4]
 12     222 ms           *                  *        nyk-bb3-link.telia.net [213.155.135.5]
 13     237 ms     238 ms    240 ms    nyk-bb4-link.telia.net [62.115.142.222]
 14     218 ms     224 ms     217 ms    det-b1-link.telia.net [62.115.113.35]
 15      221 ms      221 ms     221 ms    chi-b21-link.telia.net [62.115.141.222]
 16    248 ms     240 ms    238 ms    chi-b22-link.telia.net [62.115.141.170]
 17            *                *                *          Request timed out.
 18            *                *                *          Request timed out.
 19            *                *                *          Request timed out.
 20           *                *                *          Request timed out.
 21            *                *                *          Request timed out.
 22           *                *                *          Request timed out.
 23           *                *                *          Request timed out.
 24           *                *                *          Request timed out.
 25           *                *                *          Request timed out.
 26           *                *                *          Request timed out.
 27           *                *                *          Request timed out.
 28           *                *                *          Request timed out.
 29           *                *                *          Request timed out.
 30           *                *                *          Request timed out.

Trace complete.

 

On 11/15/2018 at 10:21 AM, Roy said:

ping 74.91.119.54

 

C:\Windows\system32>ping 74.91.119.54

Pinging 74.91.119.54 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 74.91.119.54

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

On 11/15/2018 at 10:28 AM, Roy said:

I would recommend performing scans for viruses, malware, etc. on your device if possible. There is a possibility you have a virus doing this behind the scenes.

 

I haven't done a scan till now but I will perform one today over night and wil let you know the results. However, I have just performed a clean installation of windows last week and till then I haven't done any unusual online activity or connected any external storage with my laptop so I highly doubt I'll have anything fishy in my computer.

 

Just as I said, everything happened over night. I was playing over an NFO hosted server whose IP I will communicate if you want here. I disconnected from the server. Shut down the computer. Went to sleep. The other day I tried connecting, I saw the server's status as not responding. I tried accessing that community's site and still couldn't access to it till date. Not with my current internet connection.

 

One more thing I might add here is that I had a similar issue like this before 2015. I couldn't connect to nfo servers at that place. I contacted NFO's technical staff and didn't get a satisfying response. I think I met Soja or you there as well when I referred GFL's CSS ZE server back then. Back then, I was able to access NFO's site. Now, I can't even access NFO's site. Their page is not even opening so that I may file a complaint.

No idea what happened in a matter of days. Is it possible that my windows might be blocked my access to NFO as whole. If that's the case, can I be assisted in this matter like where to check? etc.

 

Adding further, I can't access NFO from my mobile phone as well (same network)
 

Share this post


Link to post
Share on other sites


11 hours ago, OxideTM said:

 

C:\Windows\system32>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          8 ms        4 ms        5 ms       192.168.0.1
  2      118 ms        13 ms     32 ms       172.19.63.255
  3        10 ms        7 ms             *        202.163.100.85
  4         3 ms         3 ms       4 ms      202.163.100.66
  5         4 ms         3 ms        3 ms      119.159.240.53
  6         6 ms         5 ms        9 ms      khi77.pie.net.pk [221.120.251.205]
  7         9 ms         3 ms        5 ms      static.khi77.pie.net.pk [202.125.128.171]
  8     108 ms     108 ms    109 ms      te0-4-0-27.ccr21.mrs01.atlas.cogentco.com [149.14.126.1]
  9     108 ms       111 ms     114 ms      be3092.ccr41.par01.atlas.cogentco.com [130.117.49.153]
 10      116 ms      115 ms     116 ms      prs-b2-link.telia.net [213.155.141.226]
 11     224 ms     224 ms    235 ms     prs-bb3-link.telia.net [62.115.122.4]
 12     222 ms           *                  *        nyk-bb3-link.telia.net [213.155.135.5]
 13     237 ms     238 ms    240 ms    nyk-bb4-link.telia.net [62.115.142.222]
 14     218 ms     224 ms     217 ms    det-b1-link.telia.net [62.115.113.35]
 15      221 ms      221 ms     221 ms    chi-b21-link.telia.net [62.115.141.222]
 16    248 ms     240 ms    238 ms    chi-b22-link.telia.net [62.115.141.170]
 17            *                *                *          Request timed out.
 18            *                *                *          Request timed out.
 19            *                *                *          Request timed out.
 20           *                *                *          Request timed out.
 21            *                *                *          Request timed out.
 22           *                *                *          Request timed out.
 23           *                *                *          Request timed out.
 24           *                *                *          Request timed out.
 25           *                *                *          Request timed out.
 26           *                *                *          Request timed out.
 27           *                *                *          Request timed out.
 28           *                *                *          Request timed out.
 29           *                *                *          Request timed out.
 30           *                *                *          Request timed out.

Trace complete.

 

 

C:\Windows\system32>ping 74.91.119.54

Pinging 74.91.119.54 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 74.91.119.54

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

 

I haven't done a scan till now but I will perform one today over night and wil let you know the results. However, I have just performed a clean installation of windows last week and till then I haven't done any unusual online activity or connected any external storage with my laptop so I highly doubt I'll have anything fishy in my computer.

 

Just as I said, everything happened over night. I was playing over an NFO hosted server whose IP I will communicate if you want here. I disconnected from the server. Shut down the computer. Went to sleep. The other day I tried connecting, I saw the server's status as not responding. I tried accessing that community's site and still couldn't access to it till date. Not with my current internet connection.

 

One more thing I might add here is that I had a similar issue like this before 2015. I couldn't connect to nfo servers at that place. I contacted NFO's technical staff and didn't get a satisfying response. I think I met Soja or you there as well when I referred GFL's CSS ZE server back then. Back then, I was able to access NFO's site. Now, I can't even access NFO's site. Their page is not even opening so that I may file a complaint.

No idea what happened in a matter of days. Is it possible that my windows might be blocked my access to NFO as whole. If that's the case, can I be assisted in this matter like where to check? etc.

 

Adding further, I can't access NFO from my mobile phone as well (same network)
 

Thank you for those results.

 

From the looks of it, either NFO/Internap is blocking your connection or your ISP/network is blocking connections to NFO/Internap servers. Considering it's timing out after getting to a hop in Chicago (where the server is located).

 

I will be creating a ticket with NFO to confirm. I will also be performing a trace route from the server to your IP address to see if I can gain additional information.

 

I'm glad you were able perform a virus/malware scan on your computer. Though, it is possible another device including the router/modem itself could be performing port scans. This is assuming that NFO/Internap is blocking your IP for ports scans. We won't know until it's confirmed on their end.

 

From the sounds of it, your computer wouldn't be blocking the connection. It's possible your router/modem could be blocking the connection. Though, it all depends on the type of router/modem you have. I'd say log into the admin portal and see if you can find a section with blocked hosts. Sadly, I don't believe this'll help because you appear to be unable to connect to any NFO/Internap servers in Chicago.

 

I will create the ticket either tonight or early tomorrow.

 

P.S. Sorry for any grammar mistakes, really tired right now lol.

 

Thanks.

Share this post


Link to post
Share on other sites


Sometimes I have issues connecting to community servers, one thing that might help and it's pretty easy is to change the clientport on cs:go.

To do so follow these steps:

4k58TTq.png

 

H5NSvwx.png

 

TvmmfUG.png

 

Slcpqlm.png

 

 

 

Type that in there and press OK.

The default clientport is 27005, so whenever I have issues, I just swap to 27006/27007 back and forth.

I don't expect this to fix it, but maybe it could work.

 

 

 


yeah.gif

Share this post


Link to post
Share on other sites


4 hours ago, Leks said:

Sometimes I have issues connecting to community servers, one thing that might help and it's pretty easy is to change the clientport on cs:go.

To do so follow these steps:

4k58TTq.png

 

H5NSvwx.png

 

TvmmfUG.png

 

Slcpqlm.png

 

 

 

Type that in there and press OK.

The default clientport is 27005, so whenever I have issues, I just swap to 27006/27007 back and forth.

I don't expect this to fix it, but maybe it could work.

 

 

 

I have a habit of flushing dns and doing a full power cycle and clearing all cookies and cache's and removing a lot of roaming files regularly

which I have noticed in my recently devices it appears to be whole new devices and flags it as the such yet it is the same one but just in well another form.

M0Yxj-x9RCerOB5Q-AAYog.png

the list goes on from well that shown in the above picture :L

Share this post


Link to post
Share on other sites

Achievements

While changing the client's connect port is worth a try in some cases, I highly doubt it'd have any effect in this case considering @OxideTM cannot ping any NFO servers.

 

@OxideTM I've created a ticket with NFO just now. I will get back to you with the results via PM.

 

Thanks.

Share this post


Link to post
Share on other sites


@OxideTM Got a quick reply back and NFO did block your IP on their end. I have PM'd you some additional information. Please respond back in the PM.

 

Thanks.

Share this post


Link to post
Share on other sites




×
×
  • Create New...