Author Topic: TS cant connect to server RESOLVED (Read 12575 times)

Truscott · « **Reply #15 on:** March 06, 2016, 05:15:38 PM »

Cpl Bingham, have you tried resetting your modem?

Bingham · « **Reply #16 on:** March 06, 2016, 05:17:29 PM »

Neg, was just thinking about it. Probably wont be able to do it today though.

Bingham · « **Reply #17 on:** March 07, 2016, 05:58:03 PM »

So I've been scouring the internet because its not ISP and i heard something about traceroute and pinging a server??? so i did it and here are the results, if anyone can read it
Traceroute

traceroute to 66.85.14.60 (66.85.14.60), 30 hops max, 38 byte packets
1 192.168.100.1 (192.168.100.1) 111.413 ms 0.632 ms 0.343 ms
2 10.12.2.1 (10.12.2.1) 2.203 ms 3.535 ms 4.275 ms
3 172.20.7.193 (172.20.7.193) 5.148 ms 30.014 ms 101.438 ms
4 172.17.10.9 (172.17.10.9) 103.852 ms 36.858 ms 61.360 ms
5 172.20.8.217 (172.20.8.217) 51.267 ms 21.879 ms 26.528 ms
6 172.20.105.1 (172.20.105.1) 32.766 ms 12.613 ms 22.099 ms
7 172.31.31.50 (172.31.31.50) 30.865 ms 11.282 ms 22.473 ms
8 172.31.31.49 (172.31.31.49) 20.856 ms 19.259 ms 13.186 ms
9 172.31.31.34 (172.31.31.34) 22.975 ms 18.193 ms 17.515 ms
10 205.197.253.1 (205.197.253.1) 15.456 ms 25.024 ms 11.802 ms
11 ip65-46-225-101.z225-46-65.customer.algx.net (65.46.225.101) 24.610 ms 11.177 ms 20.959 ms
12 vb1511.rar3.denver-co.us.xo.net (216.156.0.157) 71.917 ms 80.043 ms 76.242 ms
13 te-4-1-0.rar3.chicago-il.us.xo.net (207.88.12.21) 67.060 ms 67.007 ms 67.578 ms
14 207.88.14.6.ptr.us.xo.net (207.88.14.6) 64.288 ms 68.278 ms 217.214 ms
15 207.88.184.146.ptr.us.xo.net (207.88.184.146) 66.584 ms 67.625 ms 64.885 ms
16 border5.po2-bbnet2.chg.pnap.net (64.94.32.74) 70.174 ms border5.po1-bbnet1.chg.pnap.net (64.94.32.10) 62.518 ms border6.po2-bbnet2.chg.pnap.net (64.94.32.75) 210.799 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

and pinging with a 9 count
PING 66.85.14.60 (66.85.14.60): 56 data bytes

--- 66.85.14.60 ping statistics ---
9 packets transmitted, 0 packets received, 100% packet loss

SSG (Ret) McAllister · « **Reply #18 on:** March 07, 2016, 07:02:49 PM »

I don't know much about networking but by the looks of it something at that last address is blocking you from sending traffic through it.

I did some very quick looking and it may have something to do with how your ISP sends it's traffic or how the server receives your traffic.

I did a quick google search on that last address and found this post on a Canadian ISP's website. https://community.shaw.ca/thread/12899

Not sure if anything useful is in there but the one thing that is kinda interesting is that a similar address was the last address they hit before getting to nfo's servers. My guess is that there is a communication / connection issue between nfo's servers and that last server you hit.

Not sure if any of this helps or is even correct but I figured I'd give it a try.

Worse comes to worse it might be beneficial to call NFO and see if they know anything?

Hope this helps.

Bingham · « **Reply #19 on:** March 07, 2016, 08:00:58 PM »

Yes something very interesting about that is that i cant access NFO servers website, It is very interesting.

Hito · « **Reply #20 on:** March 07, 2016, 08:43:58 PM »

CPL Bingham,

I found this on the NFO Servers website:

"If you (whether as our customer or not) have problems with any of our Internap or Premium bandwidth, let us know! We and Internap can often resolve lag issues by actively changing the outgoing path from the server, and sometimes even from your client to the server. "

Email
We provide customer service through support@nfoservers.com. We respond very quickly to all email, which goes into the same unified support request system that our control panel uses. Please check your account's spam folder to make sure you catch our reply."

I suggest that you contact them and ask about your problem.

Bingham · « **Reply #21 on:** March 07, 2016, 08:48:24 PM »

Awesome thanks guys!

Bingham · « **Reply #22 on:** March 07, 2016, 09:33:37 PM »

So contacted them.... their response after a little digging.

"> I have not tried connecting to other NFO servers, but I can connect to
> regular public servers.
>

It appears that your IP address was blocked on 3/5 for participating in an attack against us. This is generally a sign that a device on your home network is compromised.

Before we can unblock your IP address, we'll need you to perform some basic tasks to attempt to secure your home network to some degree:

* Update the firmware on your router and/or modem
* Change the credentials to log into the router and/or modem
* If possible, disable WAN-side administration of the router and/or modem
* Scan your PC and home network for malicious software and viruses
* Update the firmware and change the passwords on other internet-connected devices -- particularly video surveillance devices

Cody
Customer Support Agent"

So yeah.... ahha

Truscott · « **Reply #23 on:** March 07, 2016, 10:14:04 PM »

It's possible that someone used a device on your network as an exit node in an attack (which would show your IP as an attacker). It's also possible that (assuming they have an automated system) you were unintentionally caught as an attacker when connecting/disconnecting several times, something that has been happening to a few users with the new TS when the server drops their connection.

Bingham · « **Reply #24 on:** March 07, 2016, 10:17:14 PM »

Yeah they it said most likely someone used my IP to attack them, but anyways their in the process of unblocking me now, i hope that fixes it.

Bingham · « **Reply #25 on:** March 08, 2016, 08:07:58 PM »

Fixed now. for future reference if anyone has the same issue, most likely NFO. they blocked my IP address for reason stated above, but they fixed it as fast as they could and had wonderful customer service.

News: