Off topic, but don't go too far overboard - after all, we are watching...heh.
Mon Jul 05, 2004 8:23 pm
Originally posted by Slayer
I have no idea what language you guys are speaking......
traceroutes, checking for latency and packetloss along the way
Mon Jul 05, 2004 8:24 pm
Originally posted by Buliwyf
traceroutes, checking for latency and packetloss along the way
Ah. I'm not the best with networking anyways....
Mon Jul 05, 2004 10:28 pm
My ISP blocks pings and traceroutes. Meh
Mon Jul 05, 2004 10:59 pm
Originally posted by Jeffro
Charles...I have a quick question.
Why does your post count show up as 0?
I was wondering the same thing.....
Fri Jul 09, 2004 8:44 pm
I reloaded my comp with a ghosted image and it's still horribly unplayable on #1 and #1 only. It's hop #12 now timing out and I don't know if it's the problem. I can say though that it's only on #1. Ah poop.
Fri Jul 09, 2004 9:21 pm
Here is my Tracetroute (I'm in New Hampshire).
Tracing route to ecgn20.ecgnetwork.com [205.177.13.8]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 12 ms 12 ms 13 ms 10.20.1.1
3 14 ms 13 ms 15 ms at-0-3-0-1710.CORE-RTR1.MAN.verizon-gni.net [130
.81.10.65]
4 14 ms 14 ms 14 ms so-1-0-0-0.CORE-RTR2.MAN.verizon-gni.net [130.81
.9.166]
5 23 ms 22 ms 22 ms as1-0.BB-RTR1.NY5030.verizon-gni.net [130.81.4.2
53]
6 23 ms 25 ms 23 ms so-6-0-0-0.BB-RTR1.NY325.verizon-gni.net [130.81
.7.89]
7 30 ms 30 ms 29 ms so-5-0-0-0.BB-RTR1.RES.verizon-gni.net [130.81.8
.253]
8 29 ms 29 ms 29 ms so-6-0-0-0.PEER-RTR1.ASH.verizon-gni.net [130.81
.10.90]
9 30 ms 30 ms 29 ms ge4-2.3.cr02.ash01.pccwbtn.net [63.218.94.21]
10 29 ms 29 ms 29 ms ge5-1.colo01.ash01.pccwbtn.net [63.216.0.89]
11 29 ms 30 ms 29 ms ecgn20.ecgnetwork.com [205.177.13.8]
Fri Jul 09, 2004 9:23 pm
Are u on DSL slog?
Fri Jul 09, 2004 9:40 pm
Yes, Verizon DSL.
Fri Jul 09, 2004 9:49 pm
rt.
Fri Jul 09, 2004 9:58 pm
Try this and post results
ping 205.177.13.8 -l 500 -t
Fri Jul 09, 2004 10:05 pm
Well maybe it's my box. Slog and I took a closer look and the connection seems to be fine. Maybe it's just the 64 man servers. But I've been on here for years without the issue.
Fri Jul 09, 2004 10:29 pm
Well I just played on an NFORCE DC server at 64 players and the lag is there. Must be 64 man servers. I've done the following to no avail.
1. removed my router and switch
2. brought my vid and sound card settings down
3. checked all of my cooling in the case
4. updated my vid card drivers
5. reloaded my machine with a ghosted image
6. changed the AGP aperture siz from 64 to 128
7. removed a suspect IBM deskstar HD
I have a P4 2.53, 1gb of corsair XMS 2700, IBM mobo with 533 bus, TI4600 with 128, SB Audigy ZS.
Maybe a bare bones install or maybe my vid card is dying. A vid card is an issue though because if I remember right my AGP 8X slot is 1.5 volts. I think they changed the volts midstream for 8X. I'll keep working on it.
Sat Jul 10, 2004 12:50 am
Originally posted by -HaVoC-
Maybe a bare bones install or maybe my vid card is dying. A vid card is an issue though because if I remember right my AGP 8X slot is 1.5 volts. I think they changed the volts midstream for 8X. I'll keep working on it.
What model # and revision mobo?
Sat Jul 10, 2004 8:49 am
The mobo is an Intel D845PEBT2. I just reseated the memory, the vid card and the proc with a new dose of artic silver.
I have an Antec 430watt true power power supply and I am not experiencing blue screens or random lockups or reboots. So I would have to rule out heat or a failing power supply.
I guess next I can abort the ghost image and try a freshy install from scratch running just BF, but damn I shouldn't have to take it that far.
Sat Jul 10, 2004 8:50 am
Did you try unhooking your router yet?
Powered by phpBB © phpBB Group.
phpBB Mobile / SEO by Artodia.