Networks·41,456 discussions

Netgear unmanaged fs524 Speed KILL

Tags: Networking

HARDWARE INFO

Modem TP Link TC-7610
Hardware Version 1.1
Software Version v1.1.0 Build 20160920 Rel371550

TP Link Archer C5 AC1200 Router
Hardware Version: Archer C5 v1 00000000
Firmware Version: 3.13.34 Build 140424 Rel.59644n

Netgear fs524 Unmanaged Switch

Connection = Comcast – 120Mbps/6Mbps

First, thanks to anyone who throws in on this. I appreciate your time.

Being an addition/new network setup (adding the FS524), of course everything was receiving the full 120Mbps/6Mbps prior to changes. So i have ruled out any cabling issues.
I did however use cat6 cables between these when testing, so there’s that.
ALL other hardware/devices were disconnected while setting up, so no other influence is present.
I have done complete (reset to factory default)- power cycle with the hardware in this order. 1-Modem on/2-(factory default reset) router on/3-plug in Netgear switch.
Speed tests show a momentary spike to like 40-45 Mbps, then drop to 20-25 Mbps.
The Netgear is obviously a dirt cheap $20 purchase, and I’m not ruling out it being at fault.

Maybe an Auto-Negotiation issue (full duplex – half duplex mismatch), which i cannot find a setting on the router to force the full duplex/100 instead of Auto-Negotiate.

Here is a ping from a PC connected to the router/through the switch/to another PC.

C:\Users\ShopX64THEDUDE>ping 192.168.0.104

Pinging 192.168.0.104 with 32 bytes of data:
Reply from 192.168.0.104: bytes=32 time<1ms TTL=128
Reply from 192.168.0.104: bytes=32 time<1ms TTL=128
Reply from 192.168.0.104: bytes=32 time<1ms TTL=128
Reply from 192.168.0.104: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Now reversed. From PC/through switch/through router/to PC

C:\Windows\system32>ping 192.168.0.102

Pinging 192.168.0.102 with 32 bytes of data:
Reply from 192.168.0.102: bytes=32 time<1ms TTL=128
Reply from 192.168.0.102: bytes=32 time<1ms TTL=128
Reply from 192.168.0.102: bytes=32 time<1ms TTL=128
Reply from 192.168.0.102: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Ping through switch to 8.8.8.8 = 33/18/18/19ms-no loss-TTL=117

Those look pretty flawless.

Topic