• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Horrible Packet Loss on RT314: Suggestions NEEDED

her209

her209

No Lifer
Sup Yo

I built my 2nd computer to hookup to my RT314 yesternight and here's the story.

1. Fresh install of Windows 2K on both machines and latest drivers for Netgear FA311 NICs.
2. Uninstalled File and Print Sharing for Microsoft Networks, Client for Microsoft Networks, and TCP/IP.
3. Rebooted.
4. Reinstalled File and Print Sharing for Microsoft Networks, Client for Microsoft Networks, and TCP/IP.
5. Rebooted.
6. Setup RT314 as DHCP Server and computers as DHCP Clients.
7. Pinged each computer from other computer. 50% packet loss.
8. Pinged computer itself. 0% packet loss.
9. Internet access from both computers is fine.

I've read all the suggestion I found on this forum regarding File and Print Sharing using RT314. None have remedied the problem. I'm beginning to think its the Router's fault. I've even remove the the active filter in the Advanced Menu Options found through Telneting to the the Router. Also, I cannot get into Network Neighborhood > Computers Near Me. The computers are in the same workgroup.

Please post your suggestions for me and other RT314 owners with similar problems.
 
What it sounds like is either a cable issue or a NIC/Switch issue. If you do not get any packet loss from pinging the local IP address of the machine, the traffic is going through the Loopback adapter rather than through the NIC. That is why you are getting 0% packet loss.

Now, does this happen on both machines, or just 1?
 
I hesitate to even ask, but do you have 2 hubs connected by external tranceivers?

If so, I know whats wrong.

I know its a long shot ...
 
Ran some more tests.

Here are the tests and their results.

With the RT314 connected:
1. Manually configured the IP addresses (outside of the DHCP address pool) of the two computers.
2. Pinged each computer from other computer. 50% packet loss.
3. Pinged computer itself. 0% packet loss on both.
4. Repeated with different ports on the RT314. Same results.

Replaced the RT314 with XOver cable. IP address unchanged.
5. Pinged each computer from other computer. 0% packet loss.
6. Pinged computer itself. 0% packet loss on both.
7. Opened Network Neighborhood > Computers Near Me. Works!

Replaced the XOver cable with RT314. IP address DHCP Enabled.
1. Pinged each computer from other computer. 50% packet loss.
2. Pinged computer itself. 0% packet loss on both.
3. Breakthrough. Pinged RT314 from both computers.
a. Packet loss about 25% - 50% on new computer.
b. 0% packet loss on older computer.
c. Horrible Internet connection speed on new computer. WTF
d. No change in Internet connection speed on older computer.

My conclusions:
1. NIC Problem? Possible remedy: Replace Netgear FA311 with 3Com 905B-TX.
2. Cable Problem? Possible remedy: Replace with different cable.
 
Results from tests:

Switched Cat5 cables.
Weird. All of a sudden there are no more problems. 0% packet loss from Pings. 🙂
Even the "problematic" cable/NIC has gone away. Weird

Thanks to all those that replied.
 
Then, if you get no packet los with a XOver cable, then the problem lies with the Netgear RT311 device. I would replace it either with another one from Netgear or return the Netgear and get another brand. However, I would contact Netgear and get it replaced.
 


<< Then, if you get no packet los with a XOver cable, then the problem lies with the Netgear RT311 device. I would replace it either with another one from Netgear or return the Netgear and get another brand. However, I would contact Netgear and get it replaced. >>



Actually, it could be bad cable OR a bad switch.. He switched the cable, and everything worked.

There might be something silly wrong, like one of the NIC's has a pin that's not all the way bent down and making contact with one cable but not the other.

To test this, plug one computer into the router and try to ping it.
Move that same cable to the other computer and try to ping it.
Do the same with the other cable.

If one gives ANY bad results, chuck it - Cables are cheap.

- G
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top