Bad Port?

[johanh13]

I just configured my new WS-12-250a and port #2 will only do 100Mbps.... what to do?

[wayneorack]

You have tested with an know good cable? Some old cables only have 2 pairs of wires and will not do Gigabit.
You have tested with a know good Gigabit Device?

[johanh13]

tried it with three different radios and a computer on four different ethernet wires (also, all devices show gigabit in the rest of the ports)

[sirhc]

What were/are you powering on this port?

It is possible the unit has a bad port?

Would you like to RMA the unit?

[johanh13]

Yes, will probably need RMA.... I tried powering a Ligowave Pro, which is the same I did on port one (port one works great). Also, I tried with 48V on a Rocket Titanium (several brand new units). I also tried my computer and Mik router, without power, of course. Again, let me stress, port one works with all the same gear, flawless, it's only port two that has this problem. Also, when I plug in the Titanium, it stays on for a few minutes, then shows no connection, even though the radio stays on... Just so you know, on the Ligo I used 48VH and 48V on Titanium... With the Ligo it works, but only at 100Mbps....

[sirhc]

Yea the reason I ask is if people select 48V when they should select 48VH the connected device will try and pull too much current across a single pair and through the Ethernet transformer which could damage the Ethernet transformer taking out that 1 wire or pair which will render the port only capable of at most a 10/100 link and even that link would be flaky if at all.

Please fill this out and PM it to me:
RMA #: NRMA0008
Name:
Company Name:
Address 1:
Address 2:
City, State/Province:
Postal Code:
Country:
Notes: Port 2 Flaky / Fails
Returning Mac:
Forum name: Johanh13
Cell:
Email:

Also Print a copy out and include with your switch when you ship it back. we do NOT accept USPS shipment:
Netonix
c/o NRMA0008
154 Earland Drive
Building 5C
New Holland, PA 17557

[johanh13]

OK, so I got the replacement switch and all is working well! Also, I did upgrade to 1.2.0rc11 firmware...