new cable modem connection problems?
-
cableguy2k7
- Member
- Posts: 64
- Joined: Mon Mar 19, 2007 1:02 am
new cable modem connection problems?
i have a new motorola surfboard sb5101 it keeps not sure if its a discconect its where the pci activity light stop blinking and get solid and blinks very very very slowly at about 1 blink every 5 mins no connection ither its a brand new modem i just got it payed 79.99 for it its connected thru ethernet anybody know whats wrong and does motorola have configuration webpages like dlink has since my old modem was a dlink wich just fried out on me
call your ISP and have it provisionedcableguy2k7 wrote:i have a new motorola surfboard sb5101 it keeps not sure if its a discconect its where the pci activity light stop blinking and get solid and blinks very very very slowly at about 1 blink every 5 mins no connection ither its a brand new modem i just got it payed 79.99 for it its connected thru ethernet anybody know whats wrong and does motorola have configuration webpages like dlink has since my old modem was a dlink wich just fried out on me
-
cableguy2k7
- Member
- Posts: 64
- Joined: Mon Mar 19, 2007 1:02 am
-
alex_barringer
- Member
- Posts: 66
- Joined: Sun Apr 08, 2007 8:43 pm
Memory leaks in poorly designed TCP/IP stacks or Ethernet / USB / Firewire drivers with memory leaks can cause some wild results like what you have encountered. It's most likely at one time you have had your computer running and all of sudden you crashed or had malware on your system but didn't know it. Some of that malware will dig it's claws into those drivers listed above, but it's a rare instance, as it's quite hard to do, when the authors of the software want you to stay connected to the net so they can watch you from a distance, not keep you off the net.
That's good that you decided to get a newer version of the Ethernet driver, most of the drivers that Microsoft Update site, I will admit, I don't trust them for that stuff. I manually install what I want from the manufacturers web site, if I don't make the hardware myself.
That's good that you decided to get a newer version of the Ethernet driver, most of the drivers that Microsoft Update site, I will admit, I don't trust them for that stuff. I manually install what I want from the manufacturers web site, if I don't make the hardware myself.
-
cableguy2k7
- Member
- Posts: 64
- Joined: Mon Mar 19, 2007 1:02 am
-
cableguy2k7
- Member
- Posts: 64
- Joined: Mon Mar 19, 2007 1:02 am
-
cableguy2k7
- Member
- Posts: 64
- Joined: Mon Mar 19, 2007 1:02 am
any body see anything wrong here 1970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-07-14 20:59:49 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-14 20:59:16 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-07-14 19:22:49 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-14 19:22:17 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:08 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:07 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:15 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:08 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:07 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-07-10 22:28:45 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-10 22:28:13 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:13 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:08 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:07 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-07-10 22:19:43 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-10 22:19:10 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-07-10 17:31:26 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-10 17:30:54 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:10 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-07-10 16:21:51 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-10 16:21:19 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:10 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:07 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-07-10 12:11:45 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-10 12:11:12 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-07-08 23:58:04 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-08 23:57:32 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:21 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:15 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:09 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-07-08 23:40:26 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-08 23:39:53 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-07-08 19:40:48 3-Critical T005.0 SYNC Timing Synchronization failure - Loss of Sync
1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-07-08 19:39:08 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-08 19:38:35 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:07 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:06 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:10 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:07 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:13 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:07 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-07-08 05:52:24 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:13 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:08 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:07 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-07-08 05:47:45 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:10 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:07 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:15 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:07 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-07-07 22:20:33 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-07 22:20:01 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:16 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:12 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:01:40 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:01:32 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:31 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:23 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:21 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:19 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:08 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:07 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:56 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:55 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:19 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:18 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
©2004 Motorola All rights reserved.
2007-07-14 20:59:49 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-14 20:59:16 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-07-14 19:22:49 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-14 19:22:17 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:08 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:07 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:15 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:08 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:07 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-07-10 22:28:45 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-10 22:28:13 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:13 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:08 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:07 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-07-10 22:19:43 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-10 22:19:10 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-07-10 17:31:26 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-10 17:30:54 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:10 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-07-10 16:21:51 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-10 16:21:19 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:10 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:07 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-07-10 12:11:45 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-10 12:11:12 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-07-08 23:58:04 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-08 23:57:32 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:21 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:15 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:09 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-07-08 23:40:26 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-08 23:39:53 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-07-08 19:40:48 3-Critical T005.0 SYNC Timing Synchronization failure - Loss of Sync
1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-07-08 19:39:08 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-08 19:38:35 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:07 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:06 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:10 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:07 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:13 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:07 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-07-08 05:52:24 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:13 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:08 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:07 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-07-08 05:47:45 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:10 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:07 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:15 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:07 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-07-07 22:20:33 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-07 22:20:01 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:16 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:12 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:01:40 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:01:32 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:31 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:23 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:21 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:19 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:08 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:07 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:56 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:55 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:19 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:18 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
©2004 Motorola All rights reserved.
-
cableguy2k7
- Member
- Posts: 64
- Joined: Mon Mar 19, 2007 1:02 am
what about my power levelsFrequency 117000000 Hz
Signal To Noise Ratio 35.8 dB
Power Level 0.9 dBmV
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
Upstream Value
Channel ID 21
Frequency 33000000 Hz
Power 34.5 dBmV
Signal To Noise Ratio 35.8 dB
Power Level 0.9 dBmV
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
Upstream Value
Channel ID 21
Frequency 33000000 Hz
Power 34.5 dBmV
-
cableguy2k7
- Member
- Posts: 64
- Joined: Mon Mar 19, 2007 1:02 am
- YARDofSTUF
- Posts: 70006
- Joined: Sat Nov 11, 2000 12:00 am
- Location: USA
sounds like wallgarden is what I'm seein he's connecting since its to the line which I've seen many times just without it provisioned he won't get the results or the speeds like he's paying for.YARDofSTUF wrote:Sounds like hes done that.
Without calling and giving them the modems MAC he shouldnt be able to get net access.
-
cableguy2k7
- Member
- Posts: 64
- Joined: Mon Mar 19, 2007 1:02 am
umm yea duh its allready been activated the modem has like i said i have net acesss ii only have one pc not connected with a router just modem str8 to pc with ethernet gigabit ethernet that is its 10/100/1000 what its doing is the pci activity light will become solid and stop blinking and i will loose my connection but ther lights on the modem are fine green and solid they are supposed to be it only does it about every 3 days you know the orange light that blinks
sounds like you have packetloss and need to get your ISP on the phone and have a tech sent out...cableguy2k7 wrote:umm yea duh its allready been activated the modem has like i said i have net acesss ii only have one pc not connected with a router just modem str8 to pc with ethernet gigabit ethernet that is its 10/100/1000 what its doing is the pci activity light will become solid and stop blinking and i will loose my connection but ther lights on the modem are fine green and solid they are supposed to be it only does it about every 3 days you know the orange light that blinks
- YARDofSTUF
- Posts: 70006
- Joined: Sat Nov 11, 2000 12:00 am
- Location: USA
Wow your posts are tough to read.cableguy2k7 wrote:umm yea duh its allready been activated the modem has like i said i have net acesss ii only have one pc not connected with a router just modem str8 to pc with ethernet gigabit ethernet that is its 10/100/1000 what its doing is the pci activity light will become solid and stop blinking and i will loose my connection but ther lights on the modem are fine green and solid they are supposed to be it only does it about every 3 days you know the orange light that blinks
Have you had a router in the mix before? after switiching from a router to a direct connection you should unplug the modem for a few mins.
Otherwise it sounds like you need to call your ISP and have a tech come out.
-
cableguy2k7
- Member
- Posts: 64
- Joined: Mon Mar 19, 2007 1:02 am
how many time have i told you guys its been unplugged so much my modem started talking and said jeez replace me allready damit lol jk yea ill call time warner it hasnt happend for a few days its not that the modem is getting knocked it seems as my network card wich is biult into my motherboard on pc since i built my pc with amd 64fx 55 3.4ghz 1 gig of ram windows xp pro oem copy and i just reformated my system like about a week ago and it seems like my network card is the prob cuz the modem light stay on specualy the online light please bare with me as im disabled person ok
-
cableguy2k7
- Member
- Posts: 64
- Joined: Mon Mar 19, 2007 1:02 am
here is my tcp ip analyzer this is everything on page my speed is ok the 15mb im supposed to get there nothing wrong with speed. SpeedGuide.net TCP/IP Analyzer
TCP properties for IP = 76.189.121.22 (76.189.121.22)
Browser/OS = Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30)
Notes: Read the Analyzer FAQ if the above is not your IP address.
TCP options string = 020405b401010402
MTU = 1500
MTU is fully optimized for broadband.
MSS = 1460
Maximum useful data in each packet = 1460, which equals MSS.
Default TCP Receive Window (RWIN) = 65535
RWIN Scaling (RFC1323) = 0 bits
Unscaled TCP Receive Window = 65535
Note: TCP 1323 Options need to be enabled for RWIN over 2^16 (65535). Windows 9x might also need the MS Vtcp386 fix.
For optimum performance, consider changing RWIN to a multiple of MSS.
Other RWIN values that might work well with your current MTU/MSS:
513920 (MSS x 44 * scale factor of 8)
256960 (MSS x 44 * scale factor of 4)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)
bandwidth * delay product (Note this is not a speed test):
Your TCP Window limits you to: 2621 kbps (328 KBytes/s) @ 200ms
Your TCP Window limits you to: 1049 kbps (131 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 113 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349) = 00000000 (0)
TCP properties for IP = 76.189.121.22 (76.189.121.22)
Browser/OS = Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30)
Notes: Read the Analyzer FAQ if the above is not your IP address.
TCP options string = 020405b401010402
MTU = 1500
MTU is fully optimized for broadband.
MSS = 1460
Maximum useful data in each packet = 1460, which equals MSS.
Default TCP Receive Window (RWIN) = 65535
RWIN Scaling (RFC1323) = 0 bits
Unscaled TCP Receive Window = 65535
Note: TCP 1323 Options need to be enabled for RWIN over 2^16 (65535). Windows 9x might also need the MS Vtcp386 fix.
For optimum performance, consider changing RWIN to a multiple of MSS.
Other RWIN values that might work well with your current MTU/MSS:
513920 (MSS x 44 * scale factor of 8)
256960 (MSS x 44 * scale factor of 4)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)
bandwidth * delay product (Note this is not a speed test):
Your TCP Window limits you to: 2621 kbps (328 KBytes/s) @ 200ms
Your TCP Window limits you to: 1049 kbps (131 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 113 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349) = 00000000 (0)
Dude, you really need to take your time in typing, cause its very hard to understand a lick of that.cableguy2k7 wrote:how many time have i told you guys its been unplugged so much my modem started talking and said jeez replace me allready damit lol jk yea ill call time warner it hasnt happend for a few days its not that the modem is getting knocked it seems as my network card wich is biult into my motherboard on pc since i built my pc with amd 64fx 55 3.4ghz 1 gig of ram windows xp pro oem copy and i just reformated my system like about a week ago and it seems like my network card is the prob cuz the modem light stay on specualy the online light please bare with me as im disabled person ok
Post back the results after TW has come out and looked over everything and fixed the problem.