Connection to server has failed
connection error (timed out)
worked fine for two months.... sigh...
any ideas??
I got the timed out blues...
I got the timed out blues...
trying to log in I get the following:
Connection to server has failed
connection error (timed out)
worked fine for two months.... sigh...
any ideas??
Connection to server has failed
connection error (timed out)
worked fine for two months.... sigh...
any ideas??
Re: I got the timed out blues...
Have you been able to go straight though the regular game start, to the multiplayer, server list, find ns4 and join that way?
Re: I got the timed out blues...
yes he can get that far but ns4 isn't on the list
Re: I got the timed out blues...
ok... update... sry to be a pita...
it's on the list but not lit up blue and un-clickable
i can log into the other games that are blue -links
thanks man...
it's on the list but not lit up blue and un-clickable
i can log into the other games that are blue -links
thanks man...
Re: I got the timed out blues...
Click your windows button and start typing CMD. It should show up as an application for "command prompt". Click it to open.
Type in:
ipconfig /flushdns
And hit the enter key.
Then type:
ping ns4.ns4ee.com
Hit enter.
Hopefully it will show you a time in milliseconds (ms) and not a failure. If you get a valid time, no error, then you should be good to play. If not, come back and let us know!
Type in:
ipconfig /flushdns
And hit the enter key.
Then type:
ping ns4.ns4ee.com
Hit enter.
Hopefully it will show you a time in milliseconds (ms) and not a failure. If you get a valid time, no error, then you should be good to play. If not, come back and let us know!
Re: I got the timed out blues...
his ping numbers are between 630 and 750 and still can't log in
Re: I got the timed out blues...
Those are really high numbers. Most people average between 10-100 unless located in other countries... Even then they don't usually exceed 300 and that causes them a lot of lag.
Let's try to figure out why!
Windows button
CMD
Type in:
tracert ns4.ns4ee.com
It will take some time to work through this (a few minutes), but it will show your "path" to the server over the internet, with ms times for each "hop". We need to find the hop that is causing the problem.
Hopefully it's the first hop, or within the first couple.
The first hop is your computer to your home router. So if the problem (high ms time) is there, it means reboot your router (unplug for a couple seconds, then plug back in) and computer and cross your fingers (this usually works).
The next hop or two are your internet service provider... At&t or concast, xfinity, whoever. You can read the hostname to verify (something like ad1.att.net meaning at&t, etc.) If the problem is there, then call them and tell them you have issues and they should be able to fix.
If the problem is beyond 3 or 4 hops... Then we have trouble and can try some other tests. But realistically, that might not be fixable.
Try that out and let us know!
Let's try to figure out why!
Windows button
CMD
Type in:
tracert ns4.ns4ee.com
It will take some time to work through this (a few minutes), but it will show your "path" to the server over the internet, with ms times for each "hop". We need to find the hop that is causing the problem.
Hopefully it's the first hop, or within the first couple.
The first hop is your computer to your home router. So if the problem (high ms time) is there, it means reboot your router (unplug for a couple seconds, then plug back in) and computer and cross your fingers (this usually works).
The next hop or two are your internet service provider... At&t or concast, xfinity, whoever. You can read the hostname to verify (something like ad1.att.net meaning at&t, etc.) If the problem is there, then call them and tell them you have issues and they should be able to fix.
If the problem is beyond 3 or 4 hops... Then we have trouble and can try some other tests. But realistically, that might not be fixable.
Try that out and let us know!
Re: I got the timed out blues...
here's the results.. we are hughes.net and both use the same router. she has no issues....
1 <1 ms <1 ms <1 ms 192.168.42.1
2 588 ms 608 ms 608 ms host-67-45-1-65.hnremote.net [67.45.1.65]
3 635 ms 622 ms 638 ms host-67-45-5-5.hnremote.net [67.45.5.5]
4 605 ms 651 ms 641 ms 216.110.193.62
5 593 ms 638 ms 618 ms ce-0-17-0-1.r01.snjsca04.us.ce.gin.ntt.net [129.250.194.114]
6 629 ms 638 ms 638 ms ce-0-17-0-1.r01.snjsca04.us.bb.gin.ntt.net [129.250.194.113]
7 * 621 ms * ae-10.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.26]
8 663 ms 628 ms 697 ms ae-8.r23.chcgil09.us.bb.gin.ntt.net [129.250.5.16]
9 669 ms 678 ms 682 ms ae-0.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.26]
10 733 ms 698 ms 737 ms ae-6.r21.nwrknj03.us.bb.gin.ntt.net [129.250.2.167]
11 709 ms 696 ms 718 ms 129.250.3.51
12 * * * Request timed out.
13 * * 192.168.42.7 reports: Destination host unreachable.
Trace complete.
C:\Users\bobby>
1 <1 ms <1 ms <1 ms 192.168.42.1
2 588 ms 608 ms 608 ms host-67-45-1-65.hnremote.net [67.45.1.65]
3 635 ms 622 ms 638 ms host-67-45-5-5.hnremote.net [67.45.5.5]
4 605 ms 651 ms 641 ms 216.110.193.62
5 593 ms 638 ms 618 ms ce-0-17-0-1.r01.snjsca04.us.ce.gin.ntt.net [129.250.194.114]
6 629 ms 638 ms 638 ms ce-0-17-0-1.r01.snjsca04.us.bb.gin.ntt.net [129.250.194.113]
7 * 621 ms * ae-10.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.26]
8 663 ms 628 ms 697 ms ae-8.r23.chcgil09.us.bb.gin.ntt.net [129.250.5.16]
9 669 ms 678 ms 682 ms ae-0.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.26]
10 733 ms 698 ms 737 ms ae-6.r21.nwrknj03.us.bb.gin.ntt.net [129.250.2.167]
11 709 ms 696 ms 718 ms 129.250.3.51
12 * * * Request timed out.
13 * * 192.168.42.7 reports: Destination host unreachable.
Trace complete.
C:\Users\bobby>
Re: I got the timed out blues...
Awesome! It's the connection from the router that is the problem!
Hop 1 is your own computer talking to the router:
1 <1 ms <1 ms <1 ms 192.168.42.1
which it does very quickly, less than 1 ms.
Then the connection from the router to first hughes net device:
2 588 ms 608 ms 608 ms host-67-45-1-65.hnremote.net [67.45.1.65]
that is 588 ms. Which is BAAAAAAAD.
Reboot the router and the computer. (Just unplug the router for a couple seconds, then plug back in). It will take probably 3 minutes to reconnect and get everything back up.
You can try those steps again from my previous post to verify if it has solved the problem (do the tracert ns4.ns4ee.com again and check that #2 hop which is the bad one).
If that is back to a lower number, then you should be good to go!
If not, you might need to call hughes net. Also, you can run these tests on mama's computer to verify she doesn't have the same problem.
Hop 1 is your own computer talking to the router:
1 <1 ms <1 ms <1 ms 192.168.42.1
which it does very quickly, less than 1 ms.
Then the connection from the router to first hughes net device:
2 588 ms 608 ms 608 ms host-67-45-1-65.hnremote.net [67.45.1.65]
that is 588 ms. Which is BAAAAAAAD.
Reboot the router and the computer. (Just unplug the router for a couple seconds, then plug back in). It will take probably 3 minutes to reconnect and get everything back up.
You can try those steps again from my previous post to verify if it has solved the problem (do the tracert ns4.ns4ee.com again and check that #2 hop which is the bad one).
If that is back to a lower number, then you should be good to go!
If not, you might need to call hughes net. Also, you can run these tests on mama's computer to verify she doesn't have the same problem.