Bad Connection?

[A Spiral Ham]

I've had bad sever connection on the Sf servers. I've checked out my connection closed my firewalls ect... so I'm stumped. :confused: Any help is appreciated. I'll post my rig's specs later if needed. Thx in advance fellas:).

[eclyps]

getting high pings and such? Have you heard anyone else complaining about it? Kilroy told me some people were pinging high this morning, but it fixed itself. Let me know if it continues through the night. I don't see anything strange on our end, but I'll contact the datacenter if it continues

[Prosthetics]

Ya it was going on through midday too. People were talking about it on the 2fort server.

[sloppy]

Run a tracert to the IP and post it up..

[NoOdLeS<3]

yea i had it a couple of times today also..connectoin problems..

[eclyps]

yup. If you guys are still experiencing problems, please run a tracert and either PM it to me or post it here. I'll send them off to the datacenter. They always request multiple tracerts if i'm bitching about the network

[Prosthetics]

yup. If you guys are still experiencing problems, please run a tracert and either PM it to me or post it here. I'll send them off to the datacenter. They always request multiple tracerts if i'm bitching about the network

How do you do that? O_o

[eclyps]

in the command prompt type

tracert 69.13.15.17 >> tracert.txt

then copy and paste the contents of tracert.txt here :)

[A Spiral Ham]

in the command prompt type

tracert 69.13.15.17 >> tracert.txt

then copy and paste the contents of tracert.txt here :)

Thx 4 the assist fellas.:)
Update: I just did the Tracert nothing happened. any more advice?
Update V.2: my noobishness is unforgivable i found this by luck... Tracing route to 17-15-13-69.cust.propagation.net [69.13.15.17]

over a maximum of 30 hops:



1 1953 ms 1 ms 1 ms 192.168.1.1

2 1119 ms 24 ms 26 ms 10.5.49.1

3 25 ms 26 ms 26 ms so-2-0-1-0.CORE-RTR1.NWRK.verizon-gni.net [130.81.13.233]

4 26 ms 26 ms 25 ms so-7-2-0-0.BB-RTR1.NWRK.verizon-gni.net [130.81.20.160]

5 26 ms 26 ms 25 ms 0.so-5-0-0.XL1.EWR6.ALTER.NET [152.63.19.177]

6 27 ms 26 ms 26 ms 0.so-6-1-0.XL3.NYC4.ALTER.NET [152.63.16.194]

7 27 ms 27 ms * 0.ge-5-0-0.BR3.NYC4.ALTER.NET [152.63.3.110]

8 * 2575 ms * cr1-pos-0-8-2-3.NewYork.savvis.net [204.70.1.5]

9 50 ms 51 ms 53 ms cr1-tengig-0-0-5-0.chicago.savvis.net [204.70.195.113]

10 48 ms 48 ms 47 ms 204.70.195.114

11 52 ms 57 ms 52 ms ber1-vlan-241.chicagoequinix.savvis.net [204.70.196.22]

12 50 ms 51 ms 49 ms bpr1-ge-2-0-0.chicagoequinix.savvis.net [204.70.194.233]

13 57 ms 57 ms 57 ms bpr1-so-2-2-0.CWIEchq.savvis.net [208.174.226.42]

14 53 ms 51 ms 51 ms 17-15-13-69.cust.propagation.net [69.13.15.17]



Trace complete.



Tracing route to 17-15-13-69.cust.propagation.net [69.13.15.17]

over a maximum of 30 hops:



1 * 750 ms 1 ms 192.168.1.1

2 37 ms 25 ms 24 ms 10.5.49.1

3 26 ms 25 ms 26 ms so-2-0-1-0.CORE-RTR1.NWRK.verizon-gni.net [130.81.13.233]

4 25 ms 26 ms 25 ms so-7-2-0-0.BB-RTR1.NWRK.verizon-gni.net [130.81.20.160]

5 26 ms 25 ms 25 ms 0.so-5-0-0.XL1.EWR6.ALTER.NET [152.63.19.177]

6 26 ms 26 ms 26 ms 0.so-6-1-0.XL3.NYC4.ALTER.NET [152.63.16.194]

7 28 ms 29 ms 26 ms 0.ge-5-0-0.BR3.NYC4.ALTER.NET [152.63.3.110]

8 27 ms 28 ms 28 ms cr1-pos-0-8-2-3.NewYork.savvis.net [204.70.1.5]

9 51 ms 51 ms 53 ms cr1-tengig-0-0-5-0.chicago.savvis.net [204.70.195.113]

10 50 ms 48 ms 48 ms 204.70.195.114

11 52 ms 53 ms 51 ms ber1-vlan-241.chicagoequinix.savvis.net [204.70.196.22]

12 50 ms 51 ms 50 ms bpr1-ge-2-0-0.chicagoequinix.savvis.net [204.70.194.233]

13 224 ms 212 ms 237 ms bpr1-so-2-2-0.CWIEchq.savvis.net [208.174.226.42]

14 54 ms 55 ms 52 ms 17-15-13-69.cust.propagation.net [69.13.15.17]



Trace complete.

[ditship]

The first two hops (your end) are way too high. Your second log is a little better, but still kind of high. 192.168.1.1 is your router, the 10.5.49.1 is a gateway address. If you have another router handy, I'd try switching it out. Here is my tracert for comparison...


Tracing route to 17-15-13-69.cust.propagation.net [69.13.15.17]
over a maximum of 30 hops:

1 5 ms 5 ms 5 ms 10.30.0.1
2 11 ms 30 ms 10 ms 216-229-80-185-empty.fidnet.com [216.229.80.185]

3 12 ms 12 ms 13 ms 66.236.121.133.ptr.us.xo.net [66.236.121.133]
4 12 ms 13 ms 14 ms p4-3-0.mar2.marylandheights-mo.us.xo.net [207.88
.84.77]
5 20 ms 19 ms 19 ms 71.5.171.9.ptr.us.xo.net [71.5.171.9]
6 18 ms 19 ms 18 ms p1-0.IR1.Chicago2-IL.us.xo.net [65.106.6.138]
7 20 ms 19 ms 20 ms bpr1-so-2-1-0.ChicagoEquinix.savvis.net [208.174
.226.21]
8 21 ms 21 ms 20 ms bpr1-so-2-2-0.CWIEchq.savvis.net [208.174.226.42
]
9 19 ms 19 ms 20 ms 17-15-13-69.cust.propagation.net [69.13.15.17]

Trace complete.

[eclyps]

The first two hops (your end) are way too high. Your second log is a little better, but still kind of high. 192.168.1.1 is your router, the 10.5.49.1 is a gateway address. If you have another router handy, I'd try switching it out. Here is my tracert for comparison...


Tracing route to 17-15-13-69.cust.propagation.net [69.13.15.17]
over a maximum of 30 hops:

1 5 ms 5 ms 5 ms 10.30.0.1
2 11 ms 30 ms 10 ms 216-229-80-185-empty.fidnet.com [216.229.80.185]

3 12 ms 12 ms 13 ms 66.236.121.133.ptr.us.xo.net [66.236.121.133]
4 12 ms 13 ms 14 ms p4-3-0.mar2.marylandheights-mo.us.xo.net [207.88
.84.77]
5 20 ms 19 ms 19 ms 71.5.171.9.ptr.us.xo.net [71.5.171.9]
6 18 ms 19 ms 18 ms p1-0.IR1.Chicago2-IL.us.xo.net [65.106.6.138]
7 20 ms 19 ms 20 ms bpr1-so-2-1-0.ChicagoEquinix.savvis.net [208.174
.226.21]
8 21 ms 21 ms 20 ms bpr1-so-2-2-0.CWIEchq.savvis.net [208.174.226.42
]
9 19 ms 19 ms 20 ms 17-15-13-69.cust.propagation.net [69.13.15.17]

Trace complete.
that's the kinda tracert i like to see :)