Netonix Forums

We are seeing approximately 80% packet loss to 192.168.1.20 on a WS-12-250-DC and WS-12-DC. Both switches are straight out of the box and have never been touched before today. Already verified port on laptop is good and another laptop with an IP on the same range is doing the exact same thing. We have already tried doing the "hold reset while plugging in" factory default. It completes successfully but both switches still retain 80% packet loss.

Please help.

Did you upgrade the firmware to v1.4.4 or preferably v1.4.5rc2 as all v1.4.5rc2 is over v1.4.4 is bug fixes reported in v1.4.4
Download firmware here: viewtopic.php?f=17&t=240


There was a piece of paper on top of the switch that instructs you to upgrade the firmware before you do anything.

Make sure there is no other device on your network with the same IP address.

Preferably just have your laptop and no other device other than the switch when you first attach and test the switch (NOT ON YOUR NETWORK).

Obviously there is some sort of network related issue because we test all switches manually before we ship and the odds of you getting 2 defective units that we missed in testing across 2 different models is like super astronomically impossible.

Can't upgrade firmware as I cannot log into the switch via web GUI or CLI. These devices are totally off the network. Just laptop direct to switch.

Chris, it's me, Tyler. We've spoken on the phone several times. We have about 20+ of your switches. This is the very first time we've ever encountered this.

techboss wrote:Chris, it's me, Tyler. We've spoken on the phone several times. We have about 20+ of your switches. This is the very first time we've ever encountered this.

Hey Tyler!

Stupid question but have you tried another cable?

Do you have a console cable?

techboss wrote:Can't upgrade firmware as I cannot log into the switch via web GUI or CLI. These devices are totally off the network. Just laptop direct to switch.

What version is the firmware? Not sure if my recollection is right but ISTR there was an issue where things went turtle if there was no DNS resolution.

I might be aff base and that only applies to SMTP.

So, REALLY weird resolution...just for laughs we tried using a USB-to-ethernet adapter and pinging 192.168.1.20, and much to our surprise, it WORKED!

Now before you go and accuse both laptops of having bad ethernet cards, we tried connecting both laptops to other network devices (including 2 UBNT devices which are also 192.168.1.20 by default) and were able to ping with no issues whatsoever. I use my laptop daily so I can say with 100000000% certainty that nothing is wrong with my NIC.

Both laptops could only ping the switches when using the USB-to-ethernet adapter...I know, I know...it's WEIRD. I still refuse to believe it myself but multiple reboots of both the switches and laptops confirm it. Connecting to the switch using the adapter works 100% of the time while as using the onboard NICs results in about 80% packet loss.

techboss wrote:So, REALLY weird resolution...just for laughs we tried using a USB-to-ethernet adapter and pinging 192.168.1.20, and much to our surprise, it WORKED!

Now before you go and accuse both laptops of having bad ethernet cards, we tried connecting both laptops to other network devices (including 2 UBNT devices which are also 192.168.1.20 by default) and were able to ping with no issues whatsoever. I use my laptop daily so I can say with 100000000% certainty that nothing is wrong with my NIC.

Both laptops could only ping the switches when using the USB-to-ethernet adapter...I know, I know...it's WEIRD. I still refuse to believe it myself but multiple reboots of both the switches and laptops confirm it. Connecting to the switch using the adapter works 100% of the time while as using the onboard NICs results in about 80% packet loss.

Well, are the other devices you connect to 1G devices or 10/100 devices?

I would also assume you tried multiple ports in the switch with each laptop?

When you use the USB dongle are you 100M or 1G?

I have seen people damage laptop NICs plugging them into live PASSIVE POE ports, but not saying this is the issue.

I look forward to your further investigating this very weird issue and reporting back more info.