|
|
| Author |
Thread Statistics | Show CCP posts - 3 post(s) |
StuckToon
Caldari
Science and Trade Institute
   |
Posted - 2008.10.09 02:43:00 -
[1]
Ok... so since the latest patch I couldn't stay connected more than 5 minutes and blamed lag for awhile, it has since escalated to where even attempting to connect to the server takes my modem offline and power flashing. I am using this connection to do anything else I need to online four hours at a time and no issue. What is it about eve that my cable modem shuts down instantly with no exception? I completely removed eve last week before heading to vacation. Upon return I installed it to a new location and have not successfully connected once.
10/9/2008 2:29 17000100 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
10/9/2008 2:30 13000300 5 DHCP WARNING - Non-critical field invalid in response
10/9/2008 2:30 12020600 4 Improper Configuration File CVC Format
10/9/2008 2:30 20000400 3 Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
10/9/2008 2:30 17000100 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
10/9/2008 2:31 13000300 5 DHCP WARNING - Non-critical field invalid in response
System: ARRIS DOCSIS 1.1 Touchstone Cable Modem HW_REV: 05
VENDOR: Arris Interactive, L.L.C.
BOOTR: 4.00
SW_REV: CM.05.00.08.020904
MODEL: CM450A
Product Type 10c3980
Product Release 00000005
Flash Part MBM29LV160BE
Download Revision 2
Software Version: CM.05.00.08.020904
Serial Number 467BG322350074C
Software Build and Revisions
Firmware Name CM050008_020904_TCM
Firmware Build Time Mon Feb 9 16:27:05 EST 2004
Downstream
Freq/Power: 705.000 MHz -9 dBmV
Signal to Noise Ratio: 32 dB
Modulation: QAM256
--------------------------------------------------------------------------------
Upstream
Freq/Power: 22.000 MHz 43 dBmV
Channel Type: DOCSIS 1.x (TDMA)
Symbol Rate: 1280 kSym/sec
Modulation: QPSK
System Uptime: 0 days 0h:50m:47s
Computers Detected: 1
CM Status: Docsis-AC Power Iso OFF Data Reg Complete
WAN Isolation: OFF-Access to WAN is allowed
Time and Date: THU OCT 09 02:42:23 2008
|
StuckToon
Caldari
Science and Trade Institute
|
Posted - 2008.10.10 02:26:00 -
[2]
Still testing in the very little time off I have, hopefully results this weekend. Telnet succeeds *~¦♠♦Φ+☻┬º[
q=
╫·p¦@♦├√LIVE@ccp♥
I ran latest version of WinSock XP Fix http://www.snapfiles.com/get/winsockxpfix.html and now can actually get server status, though enterring my password still turns off my internet untill I connect to 192.168.100.1. I am running the pingplotter and failing miserably. Hopefully results soon. |
StuckToon
Caldari
Science and Trade Institute
|
Posted - 2008.10.10 02:32:00 -
[3]
Target Name: N/A
IP: 87.237.38.200
Date/Time: 10/9/2008 7:26:45 PM to 10/9/2008 7:30:23 PM
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 88 0 0.0 0 2 0 [192.168.1.1]
2 88 72 81.8 6 30 13 [10.16.24.1]
3 88 73 83.0 26 51 35 c66-235-63-18.sea2.cablespeed.com [66.235.63.18]
4 88 73 83.0 8 66 19 c66-235-63-113.sea2.cablespeed.com [66.235.63.113]
5 88 73 83.0 9 27 13 207.88.189.5.ptr.us.xo.net [207.88.189.5]
6 88 74 84.1 26 47 32 207.88.12.189.ptr.us.xo.net [207.88.12.189]
7 88 74 84.1 26 67 35 207.88.12.190.ptr.us.xo.net [207.88.12.190]
8 88 74 84.1 26 71 35 sjo-bb1-link.telia.net [213.248.86.93]
9 88 74 84.1 103 123 109 ash-bb1-link.telia.net [80.91.248.189]
10 35 25 71.4 174 184 177 ldn-bb1-link.telia.net [213.248.65.97]
11 33 24 72.7 172 180 175 ldn-b4-link.telia.net [80.91.249.78]
12 88 74 84.1 173 298 198 ccp-ic-124901-ldn-thon-s2.c.telia.net [213.248.90.90]
13 88 74 84.1 173 186 177 [87.237.38.200]
|
StuckToon
Caldari
Science and Trade Institute
|
Posted - 2008.10.10 03:11:00 -
[4]
1000 samples
Target Name: N/A
IP: 87.237.38.200
Date/Time: 10/9/2008 7:26:45 PM to 10/9/2008 8:08:55 PM
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 1013 0 0.0 0 2 0 [192.168.1.1]
2 1012 843 83.3 6 62 15 [10.16.24.1]
3 1011 864 85.5 19 87 40 c66-235-63-18.sea2.cablespeed.com [66.235.63.18]
4 1011 863 85.4 8 119 22 c66-235-63-113.sea2.cablespeed.com [66.235.63.113]
5 1011 862 85.3 8 193 21 207.88.189.5.ptr.us.xo.net [207.88.189.5]
6 1011 864 85.5 25 96 36 207.88.12.189.ptr.us.xo.net [207.88.12.189]
7 1011 866 85.7 26 92 37 207.88.12.190.ptr.us.xo.net [207.88.12.190]
8 1011 864 85.5 25 138 39 sjo-bb1-link.telia.net [213.248.86.93]
9 1011 866 85.7 102 174 114 ash-bb1-link.telia.net [80.91.248.189]
10 490 421 85.9 173 228 183 ldn-bb1-link.telia.net [213.248.65.97]
11 479 421 87.9 172 253 186 ldn-b4-link.telia.net [80.91.254.22]
12 1011 869 86.0 173 411 192 ccp-ic-124901-ldn-thon-s2.c.telia.net [213.248.90.90]
13 1011 868 85.9 173 232 183 [87.237.38.200] |
StuckToon
Caldari
Science and Trade Institute
|
Posted - 2008.10.10 04:40:00 -
[5]
Edited by: StuckToon on 10/10/2008 04:40:35
yes other mmo's work.. no issue, infact i've left them on overnight and all day at work
|
StuckToon
Caldari
Science and Trade Institute
|
Posted - 2008.10.10 18:46:00 -
[6]
Ah... that eases the pain a bit to see a Goon on this thread. |
StuckToon
Caldari
Science and Trade Institute
|
Posted - 2008.10.11 03:06:00 -
[7]
C:\>ping -t 10.16.24.1
Pinging 10.16.24.1 with 32 bytes of data:
Reply from 10.16.24.1: bytes=32 time=29ms TTL=254
Reply from 10.16.24.1: bytes=32 time=36ms TTL=254
Reply from 10.16.24.1: bytes=32 time=10ms TTL=254
Reply from 10.16.24.1: bytes=32 time=21ms TTL=254
Reply from 10.16.24.1: bytes=32 time=18ms TTL=254
Ping statistics for 10.16.24.1:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 36ms, Average = 22ms
Control-C
^C
C:\>tracert 10.16.24.1
Tracing route to 10.16.24.1 over a maximum of 30 hops
1 7 ms <1 ms <1 ms 192.168.1.1
2 23 ms 21 ms 27 ms 10.16.24.1
Trace complete.
C:\>ping -t 66.235.63.18
Pinging 66.235.63.18 with 32 bytes of data:
Reply from 66.235.63.18: bytes=32 time=59ms TTL=62
Reply from 66.235.63.18: bytes=32 time=20ms TTL=62
Reply from 66.235.63.18: bytes=32 time=11ms TTL=62
Reply from 66.235.63.18: bytes=32 time=16ms TTL=62
Ping statistics for 66.235.63.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 59ms, Average = 26ms
Control-C
^C
C:\>tracert 66.235.63.18
Tracing route to c66-235-63-18.sea2.cablespeed.com [66.235.63.18]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 11 ms 8 ms 18 ms 10.16.24.1
3 * 41 ms * c66-235-63-18.sea2.cablespeed.com [66.235.63.18]
4 28 ms 24 ms 24 ms c66-235-63-18.sea2.cablespeed.com [66.235.63.18]
Trace complete.
C:\>tracert 66.235.63.18
Tracing route to c66-235-63-18.sea2.cablespeed.com [66.235.63.18]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 13 ms 12 ms 16 ms 10.16.24.1
3 38 ms 36 ms 24 ms c66-235-63-18.sea2.cablespeed.com [66.235.63.18]
Trace complete.
C:\>tracert 66.235.63.18
Tracing route to c66-235-63-18.sea2.cablespeed.com [66.235.63.18]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 9 ms 7 ms 10.16.24.1
3 18 ms 22 ms 26 ms c66-235-63-18.sea2.cablespeed.com [66.235.63.18]
Trace complete.
C:\>ping -t 66.235.63.113
Pinging 66.235.63.113 with 32 bytes of data:
Request timed out.
Reply from 66.235.63.113: bytes=32 time=13ms TTL=252
Request timed out.
Reply from 66.235.63.113: bytes=32 time=18ms TTL=252
Reply from 66.235.63.113: bytes=32 time=20ms TTL=252
Reply from 66.235.63.113: bytes=32 time=33ms TTL=252
Reply from 66.235.63.113: bytes=32 time=13ms TTL=252
Reply from 66.235.63.113: bytes=32 time=19ms TTL=252
Reply from 66.235.63.113: bytes=32 time=26ms TTL=252
Reply from 66.235.63.113: bytes=32 time=26ms TTL=252
Reply from 66.235.63.113: bytes=32 time=9ms TTL=252
Reply from 66.235.63.113: bytes=32 time=24ms TTL=252
Reply from 66.235.63.113: bytes=32 time=27ms TTL=252
Reply from 66.235.63.113: bytes=32 time=14ms TTL=252
Reply from 66.235.63.113: bytes=32 time=23ms TTL=252
Reply from 66.235.63.113: bytes=32 time=13ms TTL=252
Reply from 66.235.63.113: bytes=32 time=28ms TTL=252
Reply from 66.235.63.113: bytes=32 time=35ms TTL=252
Reply from 66.235.63.113: bytes=32 time=51ms TTL=252
Reply from 66.235.63.113: bytes=32 time=9ms TTL=252
Reply from 66.235.63.113: bytes=32 time=21ms TTL=252
Reply from 66.235.63.113: bytes=32 time=20ms TTL=252
Ping statistics for 66.235.63.113:
Packets: Sent = 22, Received = 20, Lost = 2 (9% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 51ms, Average = 22ms
Control-C
^C
|
StuckToon
Caldari
Science and Trade Institute
|
Posted - 2008.10.11 03:06:00 -
[8]
Tracing route to 87.237.38.200 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 28 ms 27 ms 16 ms 10.16.24.1
3 78 ms 821 ms 61 ms c66-235-63-18.sea2.cablespeed.com [66.235.63.18]
4 84 ms * 90 ms c66-235-63-113.sea2.cablespeed.com [66.235.63.11
3]
5 13 ms 13 ms 23 ms 207.88.189.5.ptr.us.xo.net [207.88.189.5]
6 27 ms 29 ms 32 ms 207.88.12.189.ptr.us.xo.net [207.88.12.189]
7 29 ms 29 ms 46 ms 207.88.12.190.ptr.us.xo.net [207.88.12.190]
8 63 ms 70 ms 95 ms sjo-bb1-link.telia.net [213.248.86.93]
9 106 ms 115 ms 125 ms ash-bb1-link.telia.net [80.91.248.189]
10 186 ms 193 ms 184 ms ldn-bb1-link.telia.net [213.248.65.97]
11 197 ms 177 ms 182 ms ldn-b4-link.telia.net [80.91.249.78]
12 189 ms 174 ms 175 ms ccp-ic-124901-ldn-thon-s2.c.telia.net [213.248.9
0.90]
13 202 ms 205 ms 187 ms 87.237.38.200
Trace complete.
C:\>tracert 87.237.38.200
Tracing route to 87.237.38.200 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 15 ms 16 ms 13 ms 10.16.24.1
3 36 ms 32 ms 38 ms c66-235-63-18.sea2.cablespeed.com [66.235.63.18]
4 38 ms 32 ms 25 ms c66-235-63-113.sea2.cablespeed.com [66.235.63.11
3]
5 28 ms 21 ms 26 ms 207.88.189.5.ptr.us.xo.net [207.88.189.5]
6 43 ms 45 ms 38 ms 207.88.12.189.ptr.us.xo.net [207.88.12.189]
7 48 ms 41 ms 50 ms 207.88.12.190.ptr.us.xo.net [207.88.12.190]
8 41 ms 54 ms 47 ms sjo-bb1-link.telia.net [213.248.86.93]
9 126 ms 113 ms 109 ms ash-bb1-link.telia.net [80.91.248.189]
10 181 ms 200 ms 193 ms ldn-bb2-pos6-0-0.telia.net [213.248.65.209]
11 199 ms 187 ms 186 ms ldn-b4-link.telia.net [80.91.254.22]
12 206 ms 189 ms 192 ms ccp-ic-124901-ldn-thon-s2.c.telia.net [213.248.9
0.90]
13 192 ms 209 ms 194 ms 87.237.38.200
Trace complete.
C:\>ping -t 87.237.38.200
Pinging 87.237.38.200 with 32 bytes of data:
Reply from 87.237.38.200: bytes=32 time=254ms TTL=113
Reply from 87.237.38.200: bytes=32 time=190ms TTL=113
Reply from 87.237.38.200: bytes=32 time=178ms TTL=113
Reply from 87.237.38.200: bytes=32 time=176ms TTL=113
Reply from 87.237.38.200: bytes=32 time=205ms TTL=113
Reply from 87.237.38.200: bytes=32 time=200ms TTL=113
Reply from 87.237.38.200: bytes=32 time=190ms TTL=113
Reply from 87.237.38.200: bytes=32 time=185ms TTL=113
Reply from 87.237.38.200: bytes=32 time=187ms TTL=113
Reply from 87.237.38.200: bytes=32 time=177ms TTL=113
Reply from 87.237.38.200: bytes=32 time=192ms TTL=113
Reply from 87.237.38.200: bytes=32 time=181ms TTL=113
Reply from 87.237.38.200: bytes=32 time=184ms TTL=113
Reply from 87.237.38.200: bytes=32 time=198ms TTL=113
Reply from 87.237.38.200: bytes=32 time=174ms TTL=113
Reply from 87.237.38.200: bytes=32 time=192ms TTL=113
Request timed out.
Reply from 87.237.38.200: bytes=32 time=178ms TTL=113
Reply from 87.237.38.200: bytes=32 time=197ms TTL=113
Reply from 87.237.38.200: bytes=32 time=189ms TTL=113
Reply from 87.237.38.200: bytes=32 time=174ms TTL=113
Reply from 87.237.38.200: bytes=32 time=193ms TTL=113
Reply from 87.237.38.200: bytes=32 time=175ms TTL=113
Reply from 87.237.38.200: bytes=32 time=183ms TTL=113
Reply from 87.237.38.200: bytes=32 time=176ms TTL=113
Reply from 87.237.38.200: bytes=32 time=187ms TTL=113
Reply from 87.237.38.200: bytes=32 time=204ms TTL=113
Reply from 87.237.38.200: bytes=32 time=176ms TTL=113
Reply from 87.237.38.200: bytes=32 time=197ms TTL=113
Reply from 87.237.38.200: bytes=32 time=175ms TTL=113
Reply from 87.237.38.200: bytes=32 time=174ms TTL=113
Reply from 87.237.38.200: bytes=32 time=175ms TTL=113
Reply from 87.237.38.200: bytes=32 time=177ms TTL=113
Reply from 87.237.38.200: bytes=32 time=174ms TTL=113
Reply from 87.237.38.200: bytes=32 time=199ms TTL=113
Request timed out.
Reply from 87.237.38.200: bytes=32 time=177ms TTL=113
Reply from 87.237.38.200: bytes=32 time=175ms TTL=113
Reply from 87.237.38.200: bytes=32 time=181ms TTL=113
Reply from 87.237.38.200: bytes=32 time=179ms TTL=113
Reply from 87.237.38.200: bytes=32 time=205ms TTL=113
Ping statistics for 87.237.38.200:
Packets: Sent = 41, Received = 39, Lost = 2 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 174ms, Maximum = 254ms, Average = 186ms
Control-C
^C
C:\>
|
StuckToon
Caldari
Science and Trade Institute
|
Posted - 2008.10.11 03:08:00 -
[9]
Target Name: N/A
IP: 87.237.38.200
Date/Time: 10/10/2008 6:53:07 PM to 10/10/2008 7:55:35 PM
Hop Sent Err PL% Min Max Avg Host Name / [IP]
2 1500 1256 83.7 5 70 17 [10.16.24.1]
3 1500 1287 85.8 11 86 41 c66-235-63-18.sea2.cablespeed.com [66.235.63.18]
4 1500 1289 85.9 8 109 21 c66-235-63-113.sea2.cablespeed.com [66.235.63.113]
5 1500 1289 85.9 7 199 21 207.88.189.5.ptr.us.xo.net [207.88.189.5]
6 1500 1288 85.9 26 96 38 207.88.12.189.ptr.us.xo.net [207.88.12.189]
7 1500 1287 85.8 26 85 36 207.88.12.190.ptr.us.xo.net [207.88.12.190]
8 1500 1286 85.7 25 189 38 sjo-bb1-link.telia.net [213.248.86.93]
9 1500 1287 85.8 102 157 113 ash-bb1-link.telia.net [80.91.248.189]
10 637 546 85.7 172 230 183 ldn-bb1-link.telia.net [213.248.65.97]
11 638 549 86.1 173 279 187 ldn-b4-link.telia.net [80.91.254.22]
12 1500 1303 86.9 173 411 195 ccp-ic-124901-ldn-thon-s2.c.telia.net [213.248.90.90]
13 1500 1292 86.1 172 259 184 [87.237.38.200]
now I am doubting the worthiness of this pingplotter as a troubleshooting tool... where the hell are the drops. What is it using to calculate 84%
|
StuckToon
Caldari
Science and Trade Institute
|
Posted - 2008.10.11 03:28:00 -
[10]
o nice... now here's another thing... so what if another port is not supported... if it might work GREAT. Now the only place I can find a port specified is in the start.ini NOT prefs.ini AND eveoffline throws an error if you attempt to change the port in that file, not allowing you to continue, the only thing to do is change the port back to 26000. Good times *bow *wave* yes you all can have my 45 Billion wallet *lolz* IF I could ever regain a connection to send it. Good Game
|
|
|
StuckToon
Caldari
Science and Trade Institute
|
Posted - 2008.10.11 15:58:00 -
[11]
Edited by: StuckToon on 11/10/2008 15:59:59
FIXED. Netgear wgr61v9 router. Searches for firmware update, nothing new found. OK... ISP said to update it. Owell download and forced the same version firmware. Something must have been hoarked.
Edit: thing I don't get is I couldn't connect even bypassing it earlier, could have been a compound problem something else was fixed along the way.
|
StuckToon
Caldari
Science and Trade Institute
|
Posted - 2008.10.11 16:09:00 -
[12]
Heh, I speak too soon. Must have been just one lucky connection for 3 minutes. It is back to resetting the modem even without the router.
|
|
|
| |
|