I'm having trouble with packet loss with my internet connection. I was wondering what this might be from? Is it an ISP problem? (I Have Road Runner), or is it a conflict with the Hub to the Cable Modem? I've been having this packet loss problem since last week. I've contacted road runner, and they made me do tests, like from the ms-dos prompt, "ping -n 50 www.yahoo.com" , I've tested many times, 1) rj-45 cable from my computer, to hub, to cable modem 2) usb cable from my computer, to cable modem. 3) rj-45 cable from computer to cable modem. None seem to solve any problem, but the packet loss (since last week) has been gettin better. I ran the test for like 2000 hops, and it timed out only 200 times. Then again I tested 50 hops, timed out once. Tried it again, timed out 12 times. It's very inconsistent, and it's very hard to play games with. Anybody know what I should do? Ethernet Card: NETGEAR FA311 Cable Modem: Toshiba PCX1100U Hub: NETGEAR EN104TP

Did you try pinging your LAN. Try ping -n 50 127.0.0.1 If that times out then it is your Ethernet card at fault. Ttry pinging your own IP address. It that times out then it your modem at fault. I take it that as you are using a Hub you have a LAN. Try pinging a computer on your LAN. That should work fine. If you have your Modem plugged into your HUB, then that could be your problem. It would mean that two computers on the network are trying to use the same IP address. That's not possible. Stuart

I pinged 127.0.0.1, no packet loss I pinged my IP address (24.169.242.2) and it had 100% Packet Loss. Tried the same thing on the other computer connected to the HUB, same result. I pinged the other computers IP address, and it gave me 100% packet loss. So both computers have different IP's so I don't think they're trying to use the same IP. Do you think I should ask my ISP for a new cable modem?

The computers will have different Lan addresses but both will have the same Internet IP address, 24.169.242.2. What address did you ping on the other computer? The only way to share an internet connection through a hub is via a router. Plugging a modem directly into a hub is going to cause problems becasue of the was a hub works. If you want to share the internet between the two computer you will need to install another network card in one of the computers and connect the modem to that. You then need to set up Internet Connection Sharing. Try taking the hub out of the loop and connecting modem directly to the network card. I would bet that works. Stuart

Let's not get to far away with my problem, I'm getting packet loss. I'm not worried with any sharing internet crap. This problem had just started last week. I still get packet loss when I connect either computer with RJ-45 to cable modem. So I don't think the HUB is interefering with anything. Do I have a cable modem problem? I've had the modem for about 3 years, I got it for free with the signup with Road Runner. I don't know what to do?

I:\DOCUME~1\JARODG~1\DESKTOP>ping -n 50 www.google.com Pinging www.google.akadns.net [216.239.41.99] with 32 bytes of data: Reply from 216.239.41.99: bytes=32 time=59ms TTL=52 Reply from 216.239.41.99: bytes=32 time=72ms TTL=52 Reply from 216.239.41.99: bytes=32 time=50ms TTL=52 Reply from 216.239.41.99: bytes=32 time=53ms TTL=52 Reply from 216.239.41.99: bytes=32 time=52ms TTL=52 Reply from 216.239.41.99: bytes=32 time=51ms TTL=52 Reply from 216.239.41.99: bytes=32 time=56ms TTL=52 Reply from 216.239.41.99: bytes=32 time=53ms TTL=52 Reply from 216.239.41.99: bytes=32 time=73ms TTL=52 Reply from 216.239.41.99: bytes=32 time=53ms TTL=52 Reply from 216.239.41.99: bytes=32 time=60ms TTL=52 Reply from 216.239.41.99: bytes=32 time=50ms TTL=52 Reply from 216.239.41.99: bytes=32 time=50ms TTL=52 Reply from 216.239.41.99: bytes=32 time=51ms TTL=52 Reply from 216.239.41.99: bytes=32 time=50ms TTL=52 Reply from 216.239.41.99: bytes=32 time=50ms TTL=52 Reply from 216.239.41.99: bytes=32 time=59ms TTL=52 Reply from 216.239.41.99: bytes=32 time=71ms TTL=52 Reply from 216.239.41.99: bytes=32 time=177ms TTL=52 Reply from 216.239.41.99: bytes=32 time=276ms TTL=52 Reply from 216.239.41.99: bytes=32 time=141ms TTL=52 Reply from 216.239.41.99: bytes=32 time=298ms TTL=52 Reply from 216.239.41.99: bytes=32 time=318ms TTL=52 Reply from 216.239.41.99: bytes=32 time=266ms TTL=52 Reply from 216.239.41.99: bytes=32 time=299ms TTL=52 Reply from 216.239.41.99: bytes=32 time=56ms TTL=52 Reply from 216.239.41.99: bytes=32 time=51ms TTL=52 Reply from 216.239.41.99: bytes=32 time=163ms TTL=52 Reply from 216.239.41.99: bytes=32 time=49ms TTL=52 Request timed out. Request timed out. Reply from 216.239.41.99: bytes=32 time=50ms TTL=52 Reply from 216.239.41.99: bytes=32 time=52ms TTL=52 Reply from 216.239.41.99: bytes=32 time=51ms TTL=52 Reply from 216.239.41.99: bytes=32 time=50ms TTL=52 Reply from 216.239.41.99: bytes=32 time=49ms TTL=52 Request timed out. Request timed out. Request timed out. Reply from 216.239.41.99: bytes=32 time=51ms TTL=52 Reply from 216.239.41.99: bytes=32 time=58ms TTL=52 Reply from 216.239.41.99: bytes=32 time=47ms TTL=52 Reply from 216.239.41.99: bytes=32 time=52ms TTL=52 Reply from 216.239.41.99: bytes=32 time=54ms TTL=52 Reply from 216.239.41.99: bytes=32 time=51ms TTL=52 Reply from 216.239.41.99: bytes=32 time=81ms TTL=52 Reply from 216.239.41.99: bytes=32 time=49ms TTL=52 Reply from 216.239.41.99: bytes=32 time=66ms TTL=52 Request timed out. Reply from 216.239.41.99: bytes=32 time=49ms TTL=52 Ping statistics for 216.239.41.99: Packets: Sent = 50, Received = 44, Lost = 6 (12% loss), Approximate round trip times in milli-seconds: Minimum = 47ms, Maximum = 318ms, Average = 89ms This Is What It Looks Like