any advise helpful mediacom 8meg
- wishbone420
- New Member
- Posts: 11
- Joined: Sun Feb 24, 2008 11:34 am
any advise helpful mediacom 8meg
« SpeedGuide.net TCP Analyzer Results »
Tested on: 02.24.2008 11:42
IP address: 12.208.xx.xx
TCP options string: 020405b40103030201010402
MSS: 1460
MTU: 1500
TCP Window: 259880 (multiple of MSS)
RWIN Scaling: 2
Unscaled RWIN : 64970
Reccomended RWINs: 64240, 128480, 256960, 513920
BDP limit (200ms): 10395kbps (1299KBytes/s)
BDP limit (500ms): 4158kbps (520KBytes/s)
MTU Discovery: ON
TTL: 51
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)
Ping Results:
--- ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3996ms
rtt min/avg/max/mdev = 39.452/43.161/50.219/3.865 ms
Traceroute Results:
traceroute to 12.***.30.** (), 30 hops max, 40 byte packets
1 66.230.216.1 (66.230.216.1) 0.256 ms 0.233 ms 0.221 ms
2 e1f.dr5.as30217.net (84.40.24.45) 0.546 ms 0.773 ms 1.018 ms
3 e3-1.co2.as30217.net (84.40.24.81) 0.334 ms 0.395 ms 0.477 ms
4 te-1-4.car4.Tampa1.Level3.net (4.71.2.13) 0.465 ms 0.512 ms 0.566 ms
5 ae-14-14.car1.Tampa1.Level3.net (4.69.133.57) 0.654 ms 0.706 ms 0.759 ms
6 ae-5-5.ebr2.Atlanta2.Level3.net (4.69.133.50) 18.545 ms 23.666 ms 26.901 ms
7 ae-22-56.car2.Atlanta1.Level3.net (4.68.103.163) 68.309 ms ae-22-54.car2.Atlanta1.Level3.net (4.68.103.99) 68.642 ms ae-22-52.car2.Atlanta1.Level3.net (4.68.103.35) 68.505 ms
8 192.205.34.57 (192.205.34.57) 19.518 ms 19.859 ms 19.503 ms
9 tbr2.attga.ip.att.net (12.122.96.70) 21.174 ms 21.146 ms 21.139 ms
10 12.122.96.73 (12.122.96.73) 23.531 ms 23.736 ms *
11 12-215-1-77.client.mchsi.com (12.215.1.77) 28.891 ms 29.364 ms 29.087 ms
12 12-215-10-42.client.mchsi.com (12.215.10.42) 32.055 ms 32.045 ms 31.735 ms
13 12-***-30-**.client.mchsi.com (12.***.30.**) 58.257 ms 50.262 ms 54.337 ms
[URL=http://www.speedguide.net/speedtest/results.php?test=16
Tested on: 02.24.2008 11:42
IP address: 12.208.xx.xx
TCP options string: 020405b40103030201010402
MSS: 1460
MTU: 1500
TCP Window: 259880 (multiple of MSS)
RWIN Scaling: 2
Unscaled RWIN : 64970
Reccomended RWINs: 64240, 128480, 256960, 513920
BDP limit (200ms): 10395kbps (1299KBytes/s)
BDP limit (500ms): 4158kbps (520KBytes/s)
MTU Discovery: ON
TTL: 51
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)
Ping Results:
--- ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3996ms
rtt min/avg/max/mdev = 39.452/43.161/50.219/3.865 ms
Traceroute Results:
traceroute to 12.***.30.** (), 30 hops max, 40 byte packets
1 66.230.216.1 (66.230.216.1) 0.256 ms 0.233 ms 0.221 ms
2 e1f.dr5.as30217.net (84.40.24.45) 0.546 ms 0.773 ms 1.018 ms
3 e3-1.co2.as30217.net (84.40.24.81) 0.334 ms 0.395 ms 0.477 ms
4 te-1-4.car4.Tampa1.Level3.net (4.71.2.13) 0.465 ms 0.512 ms 0.566 ms
5 ae-14-14.car1.Tampa1.Level3.net (4.69.133.57) 0.654 ms 0.706 ms 0.759 ms
6 ae-5-5.ebr2.Atlanta2.Level3.net (4.69.133.50) 18.545 ms 23.666 ms 26.901 ms
7 ae-22-56.car2.Atlanta1.Level3.net (4.68.103.163) 68.309 ms ae-22-54.car2.Atlanta1.Level3.net (4.68.103.99) 68.642 ms ae-22-52.car2.Atlanta1.Level3.net (4.68.103.35) 68.505 ms
8 192.205.34.57 (192.205.34.57) 19.518 ms 19.859 ms 19.503 ms
9 tbr2.attga.ip.att.net (12.122.96.70) 21.174 ms 21.146 ms 21.139 ms
10 12.122.96.73 (12.122.96.73) 23.531 ms 23.736 ms *
11 12-215-1-77.client.mchsi.com (12.215.1.77) 28.891 ms 29.364 ms 29.087 ms
12 12-215-10-42.client.mchsi.com (12.215.10.42) 32.055 ms 32.045 ms 31.735 ms
13 12-***-30-**.client.mchsi.com (12.***.30.**) 58.257 ms 50.262 ms 54.337 ms
[URL=http://www.speedguide.net/speedtest/results.php?test=16
Try the following with TCP Optimizer:
General Settings tab:
Custom settings - check
Modify All Network Adapters - check
network adapter selection - your NIC
MTU - 1500
TTL - 64
TCP Receive Window - 128480
MTU Discovery - Yes
Black Hole Detect - No
Selective Acks - Yes
Max Duplicate ACKs - 2
TCP 1323 Options:
Windows Scaling - checked
Timestamps - uncheck
Advanced Settings tab:
Max Connections per Server - 10
Max Connections per 1.0 Server - 20
LocalPriority - 1
Host Priority - 1
DNSPriority - 1
NetbtPriority - 1
Lan Browsing speedup - optimized
QoS: NonBestEffortLimit - 0
ToS: DisableUserTOSSetting - 0
ToS: DefaultTOSValue - 80
MaxNegativeCacheTtl - 0
NetFailureCacheTime - 0
NegativeSOACache Time - 0
LAN Request Buffer Size - 32768
Then select "Apply Changes" and reboot to take effect
General Settings tab:
Custom settings - check
Modify All Network Adapters - check
network adapter selection - your NIC
MTU - 1500
TTL - 64
TCP Receive Window - 128480
MTU Discovery - Yes
Black Hole Detect - No
Selective Acks - Yes
Max Duplicate ACKs - 2
TCP 1323 Options:
Windows Scaling - checked
Timestamps - uncheck
Advanced Settings tab:
Max Connections per Server - 10
Max Connections per 1.0 Server - 20
LocalPriority - 1
Host Priority - 1
DNSPriority - 1
NetbtPriority - 1
Lan Browsing speedup - optimized
QoS: NonBestEffortLimit - 0
ToS: DisableUserTOSSetting - 0
ToS: DefaultTOSValue - 80
MaxNegativeCacheTtl - 0
NetFailureCacheTime - 0
NegativeSOACache Time - 0
LAN Request Buffer Size - 32768
Then select "Apply Changes" and reboot to take effect
"Contentment is not the fulfillment of what you want, but is the realisation of how much you already have" - anon
I have some questions for you trodgers.trogers wrote:Try the following with TCP Optimizer:
Have you ever had bad TCP/IP settings cause latency? I ask because my experience with tweaking TCP settings has been you might get a little more throughput but thats about it, and that it never actually fixes/causes connection problems other than not getting that extra tweaked speed.
- Rollingstone
- Senior Member
- Posts: 3161
- Joined: Wed Jan 23, 2008 5:50 am
- Location: HoChiMinh, Vietnam
Hardware + Software + Luck = 90-99% Speed
Hardware : Good ISP Network, Modem/router, NIC...
Software : Proper TCP Settings for Hardware.
Luck : thanks God if you're near ISP Server
@Wishbone 420 :
Do a tracert yahoo.com
Hardware : Good ISP Network, Modem/router, NIC...
Software : Proper TCP Settings for Hardware.
Luck : thanks God if you're near ISP Server
@Wishbone 420 :
Do a tracert yahoo.com
What makes you: "...waking up in the morning so excited about & wanna FLY out of the door ?"
I personally have had no bad experiences when changing TCP settings, but there were some cases from other members who had, usually due to using the wrong MTU value or that their ISP does not accept the tweak value for Default ToS value.helter wrote:I have some questions for you trodgers.
Have you ever had bad TCP/IP settings cause latency? I ask because my experience with tweaking TCP settings has been you might get a little more throughput but thats about it, and that it never actually fixes/causes connection problems other than not getting that extra tweaked speed.
But in many cases, members found they have had no improvement after applying tweaks. The reason for this is mostly either poor signal quality or presence of malware or some undesireable program in the comp.
Tweaks alone cannot solve problem caused by other factors. These factors have to be isolated and addressed directly in order to get an overall improvment either in ping times or speed or both.
Sometimes the problem is not at our end and this have to raised up to our ISP for correction.
"Contentment is not the fulfillment of what you want, but is the realisation of how much you already have" - anon
To check signal quality, do a tracert (not traceroute) to http://www.yahoo.com and post.
"Contentment is not the fulfillment of what you want, but is the realisation of how much you already have" - anon
I was just wondering, never seen a tcp stack tweak cause a loss of connection, packet loss, or increased latency, but I have seen people try to suggest it can elsewhere. I've had a couple trouble calls recently where I could prove it was customer EQ by bringing in my laptop, but never could figure out exactly what they had going on, one was a mac and I just don't know macs, the other I suspected was bad ethernet card, but was wondering if it was TCP setting for the ethernet card. In either case, putting drivers and connection in USB fixed the issue, but if it was a setting I'd rather know that. Thanks.trogers wrote:I personally have had no bad experiences when changing TCP settings, but there were some cases from other members who had, usually due to using the wrong MTU value or that their ISP does not accept the tweak value for Default ToS value.
But in many cases, members found they have had no improvement after applying tweaks. The reason for this is mostly either poor signal quality or presence of malware or some undesireable program in the comp.
Tweaks alone cannot solve problem caused by other factors. These factors have to be isolated and addressed directly in order to get an overall improvment either in ping times or speed or both.
Sometimes the problem is not at our end and this have to raised up to our ISP for correction.
- wishbone420
- New Member
- Posts: 11
- Joined: Sun Feb 24, 2008 11:34 am
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner.YOUR-CDAA84ABC7>tracert http://www.yahoo.com
Tracing route to http://www.yahoo-ht3.akadns.net [69.147.114.210]
over a maximum of 30 hops:
1 9 ms 7 ms 8 ms
2 11 ms 11 ms 15 ms 12-215-10-41.client.mchsi.com [12.215.10.41]
3 21 ms 22 ms 21 ms 12-215-1-78.client.mchsi.com [12.215.1.78]
4 42 ms 42 ms 42 ms tbr2.attga.ip.att.net [12.122.96.74]
5 40 ms 41 ms 41 ms tbr1.dlstx.ip.att.net [12.122.2.89]
6 47 ms 45 ms 45 ms 12.122.100.17
7 42 ms 42 ms 41 ms 12.86.20.18
8 70 ms 69 ms 69 ms vl156.pat2.sjc.yahoo.com [216.115.96.61]
9 75 ms 73 ms 71 ms vl146.pat2.sjc.yahoo.com [216.115.96.57]
10 74 ms 72 ms 75 ms ge-1-1-0.pat2.dce.yahoo.com [216.115.102.115]
11 148 ms 74 ms 73 ms ge-2-1-0-p141.msr1.re1.yahoo.com [216.115.108.19
]
12 72 ms 73 ms 74 ms gi1-22.bas-a2.re3.yahoo.com [66.196.112.27]
13 74 ms 72 ms 82 ms f1.http://www.vip.re3.yahoo.com [69.147.114.210]
Trace complete.
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner.YOUR-CDAA84ABC7>tracert http://www.yahoo.com
Tracing route to http://www.yahoo-ht3.akadns.net [69.147.114.210]
over a maximum of 30 hops:
1 9 ms 7 ms 8 ms
2 11 ms 11 ms 15 ms 12-215-10-41.client.mchsi.com [12.215.10.41]
3 21 ms 22 ms 21 ms 12-215-1-78.client.mchsi.com [12.215.1.78]
4 42 ms 42 ms 42 ms tbr2.attga.ip.att.net [12.122.96.74]
5 40 ms 41 ms 41 ms tbr1.dlstx.ip.att.net [12.122.2.89]
6 47 ms 45 ms 45 ms 12.122.100.17
7 42 ms 42 ms 41 ms 12.86.20.18
8 70 ms 69 ms 69 ms vl156.pat2.sjc.yahoo.com [216.115.96.61]
9 75 ms 73 ms 71 ms vl146.pat2.sjc.yahoo.com [216.115.96.57]
10 74 ms 72 ms 75 ms ge-1-1-0.pat2.dce.yahoo.com [216.115.102.115]
11 148 ms 74 ms 73 ms ge-2-1-0-p141.msr1.re1.yahoo.com [216.115.108.19
]
12 72 ms 73 ms 74 ms gi1-22.bas-a2.re3.yahoo.com [66.196.112.27]
13 74 ms 72 ms 82 ms f1.http://www.vip.re3.yahoo.com [69.147.114.210]
Trace complete.
- wishbone420
- New Member
- Posts: 11
- Joined: Sun Feb 24, 2008 11:34 am
There is no IP address at hop 1 and so I do not know if the ping times there are those of a router or modem.wishbone420 wrote:Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner.YOUR-CDAA84ABC7>tracert http://www.yahoo.com
Tracing route to http://www.yahoo-ht3.akadns.net [69.147.114.210]
over a maximum of 30 hops:
1 9 ms 7 ms 8 ms
2 11 ms 11 ms 15 ms 12-215-10-41.client.mchsi.com [12.215.10.41]
3 21 ms 22 ms 21 ms 12-215-1-78.client.mchsi.com [12.215.1.78]
4 42 ms 42 ms 42 ms tbr2.attga.ip.att.net [12.122.96.74]
5 40 ms 41 ms 41 ms tbr1.dlstx.ip.att.net [12.122.2.89]
6 47 ms 45 ms 45 ms 12.122.100.17
7 42 ms 42 ms 41 ms 12.86.20.18
8 70 ms 69 ms 69 ms vl156.pat2.sjc.yahoo.com [216.115.96.61]
9 75 ms 73 ms 71 ms vl146.pat2.sjc.yahoo.com [216.115.96.57]
10 74 ms 72 ms 75 ms ge-1-1-0.pat2.dce.yahoo.com [216.115.102.115]
11 148 ms 74 ms 73 ms ge-2-1-0-p141.msr1.re1.yahoo.com [216.115.108.19
]
12 72 ms 73 ms 74 ms gi1-22.bas-a2.re3.yahoo.com [66.196.112.27]
13 74 ms 72 ms 82 ms f1.http://www.vip.re3.yahoo.com [69.147.114.210]
Trace complete.
If they are those of a router (IP address format 192.168.xx.xx), then the ping times are high, due probably to bad wireless signals or too long an ethernet cable.
If they are those of a modem, then there may be malware in your comp causing the uneven ping times.
Clean comp registry with CCleaner. Scan for malware with AVG antivirus, SpyBot and Ad-Aware 2007.
"Contentment is not the fulfillment of what you want, but is the realisation of how much you already have" - anon
- wishbone420
- New Member
- Posts: 11
- Joined: Sun Feb 24, 2008 11:34 am
- wishbone420
- New Member
- Posts: 11
- Joined: Sun Feb 24, 2008 11:34 am
- wishbone420
- New Member
- Posts: 11
- Joined: Sun Feb 24, 2008 11:34 am
Wed Mar 05 17:29:53 2008 Error (4) ToD request sent- No Response received
Wed Mar 05 17:29:53 2008 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Wed Mar 05 17:27:00 2008 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Wed Mar 05 17:29:34 2008 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Wed Mar 05 17:29:53 2008 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Wed Mar 05 17:27:00 2008 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Wed Mar 05 17:29:34 2008 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
- wishbone420
- New Member
- Posts: 11
- Joined: Sun Feb 24, 2008 11:34 am
- wishbone420
- New Member
- Posts: 11
- Joined: Sun Feb 24, 2008 11:34 am
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner.YOUR-CDAA84ABC7>tracert yahoo.com
Tracing route to yahoo.com [216.109.112.135]
over a maximum of 30 hops:
1 7 ms 7 ms 7 ms 10.24.61.1
2 9 ms 9 ms 11 ms 12-215-10-41.client.mchsi.com [12.215.10.41]
3 19 ms 19 ms 19 ms 12-215-1-78.client.mchsi.com [12.215.1.78]
4 42 ms 41 ms 41 ms tbr2.attga.ip.att.net [12.122.96.74]
5 40 ms 41 ms 40 ms tbr1.dlstx.ip.att.net [12.122.2.89]
6 45 ms 46 ms 46 ms gar8.dlstx.ip.att.net [12.122.100.21]
7 42 ms 41 ms 42 ms 12.86.20.18
8 68 ms 69 ms 68 ms vl156.pat2.sjc.yahoo.com [216.115.96.61]
9 87 ms 81 ms 71 ms vl146.pat2.sjc.yahoo.com [216.115.96.57]
10 74 ms 71 ms 71 ms ge-1-1-0.pat2.dce.yahoo.com [216.115.102.115]
11 72 ms 74 ms 73 ms ge-1-0-0-p101.msr1.dcn.yahoo.com [216.115.108.43
]
12 74 ms 71 ms 71 ms ge7-2.bas2-m.dcn.yahoo.com [216.109.120.197]
13 75 ms 83 ms 72 ms w2.rc.vip.dcn.yahoo.com [216.109.112.135]
Trace complete.
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner.YOUR-CDAA84ABC7>tracert yahoo.com
Tracing route to yahoo.com [216.109.112.135]
over a maximum of 30 hops:
1 7 ms 7 ms 7 ms 10.24.61.1
2 9 ms 9 ms 11 ms 12-215-10-41.client.mchsi.com [12.215.10.41]
3 19 ms 19 ms 19 ms 12-215-1-78.client.mchsi.com [12.215.1.78]
4 42 ms 41 ms 41 ms tbr2.attga.ip.att.net [12.122.96.74]
5 40 ms 41 ms 40 ms tbr1.dlstx.ip.att.net [12.122.2.89]
6 45 ms 46 ms 46 ms gar8.dlstx.ip.att.net [12.122.100.21]
7 42 ms 41 ms 42 ms 12.86.20.18
8 68 ms 69 ms 68 ms vl156.pat2.sjc.yahoo.com [216.115.96.61]
9 87 ms 81 ms 71 ms vl146.pat2.sjc.yahoo.com [216.115.96.57]
10 74 ms 71 ms 71 ms ge-1-1-0.pat2.dce.yahoo.com [216.115.102.115]
11 72 ms 74 ms 73 ms ge-1-0-0-p101.msr1.dcn.yahoo.com [216.115.108.43
]
12 74 ms 71 ms 71 ms ge7-2.bas2-m.dcn.yahoo.com [216.109.120.197]
13 75 ms 83 ms 72 ms w2.rc.vip.dcn.yahoo.com [216.109.112.135]
Trace complete.
- wishbone420
- New Member
- Posts: 11
- Joined: Sun Feb 24, 2008 11:34 am
- wishbone420
- New Member
- Posts: 11
- Joined: Sun Feb 24, 2008 11:34 am
happy to report
man i hate this
- wishbone420
- New Member
- Posts: 11
- Joined: Sun Feb 24, 2008 11:34 am
more errors any guess
Time Priority Description
Tue Mar 11 15:03:27 2008 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Tue Mar 11 01:08:14 2008 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Mon Mar 10 20:43:43 2008 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Mar 09 19:11:31 2008 Warning (5) DHCP RENEW WARNING - Field invalid in response
Sun Mar 09 18:26:00 2008 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sat Mar 08 11:04:37 2008 Error (4) ToD request sent- No Response received
Sat Mar 08 11:04:36 2008 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Sat Mar 08 11:04:36 2008 Critical (3) DHCP FAILED - Request sent, No response
Sat Mar 08 11:04:09 2008 Critical (3) DHCP FAILED - Discover sent, no offer received
Sat Mar 08 11:04:03 2008 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sat Mar 08 11:03:48 2008 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Sat Mar 08 11:03:14 2008 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sat Mar 08 11:02:46 2008 Critical (3) DHCP FAILED - Discover sent, no offer received
Sat Mar 08 11:02:31 2008 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sat Mar 08 11:01:41 2008 Critical (3) DHCP FAILED - Discover sent, no offer received
Sat Mar 08 11:00:34 2008 Critical (3) No Ranging Response received - T3 time-out
Sat Mar 08 11:00:21 2008 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Sat Mar 08 10:59:48 2008 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Time Not Established Error (4) ToD request sent- No Response received
Time Not Established Critical (3) DHCP WARNING - Non-critical field invalid in response.
Thu Mar 06 17:02:16 2008 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Tue Mar 11 15:03:27 2008 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Tue Mar 11 01:08:14 2008 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Mon Mar 10 20:43:43 2008 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Mar 09 19:11:31 2008 Warning (5) DHCP RENEW WARNING - Field invalid in response
Sun Mar 09 18:26:00 2008 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sat Mar 08 11:04:37 2008 Error (4) ToD request sent- No Response received
Sat Mar 08 11:04:36 2008 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Sat Mar 08 11:04:36 2008 Critical (3) DHCP FAILED - Request sent, No response
Sat Mar 08 11:04:09 2008 Critical (3) DHCP FAILED - Discover sent, no offer received
Sat Mar 08 11:04:03 2008 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sat Mar 08 11:03:48 2008 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Sat Mar 08 11:03:14 2008 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sat Mar 08 11:02:46 2008 Critical (3) DHCP FAILED - Discover sent, no offer received
Sat Mar 08 11:02:31 2008 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sat Mar 08 11:01:41 2008 Critical (3) DHCP FAILED - Discover sent, no offer received
Sat Mar 08 11:00:34 2008 Critical (3) No Ranging Response received - T3 time-out
Sat Mar 08 11:00:21 2008 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Sat Mar 08 10:59:48 2008 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Time Not Established Error (4) ToD request sent- No Response received
Time Not Established Critical (3) DHCP WARNING - Non-critical field invalid in response.
Thu Mar 06 17:02:16 2008 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
