I'm pretty sure this isn't TP-Links fault.
I have an ASUS X370 Prime Pro board here. It shut down my 2210P, so I plugged it into a Cisco/Linksys SRW2008P. It shut that down the same way, but not before letting the magic smoke out of the NIC on the motherboard. Even after the motherboard was fried (ie no carrier on the NIC no matter what it was plugged into), it would still shut down the PoE switches. I wasn't game to plug it into an old Cisco 3550 I have here, and I'm sure as heck not plugging the replacement board into a PoE switch!
These ASUS boards with "LANGUARD" on them seem to have some surge protection devices to GND wired in such a fashion to cause this issue, and as I found out if you plug them into a beefy enough switch that is set up "just wrong", you'll smoke the network adapter on the motherboard.
"I have an ASUS X370 Prime Pro board here. It shut down my 2210P"
I have the exact same problem . I thought I was going mad , Asked around with a few of my techie mates and they had no idea .
Is there a work around yet ?
Yep. Don't plug them into a PoE switch. This work-around of cutting the earth pin off, or the use of a floating power supply is insane. The problem is with the ASUS board, and unless a song and dance gets made they'll never do anything about it. Unfortunately it's generally only on their "ricer" grade boards with "surge suppression" on the Ethernet port for marketing reasons :
Originally Posted by troyww
"ROG engineers modernized the design with advanced signal-coupling technology and premium surface-mount components, which, add protection from power spikes and keep the (Gigabit) Ethernet signal cleaner, reducing the chance of errors. These are normally corrected by error checking mechanisms, but this requires CPU time that could be devoted to your game!"
So, basic twaddle saying our custom circuits make your game less laggy because you won't get errors. Marketing fluff that breaks stuff and has no basis in reality. Unfortunately they also put it on a non-ROG board (the X370 Prime), so those of us that are not into bright red boards with flashy buits get to suffer as well.
If my local store was amenable to it, I'd happily plug board after board into my Cisco switch and flood ASUS with RMAs. Unfortunately I don't think that'll win me any favours.
The work around is to buy a non-ASUS board. Again, this is not TP-Links fault.
Thanks for the the simple reply . I do not ever expect a response from either TP-Link or Asus from past experience ...
Do other better quality POE switches work with "Lan Guard"
Given my Cisco switch made the "Lan Guard" components go up in smoke rendering the entire on-board NIC useless, I'd suggest the answer is *no*. I have some other nice switches here but there's no way I'm risking another motherboard to try it.
Originally Posted by troyww
When I get a moment I'll have a closer look at what the ASUS board is doing. I have an idea it's not properly isolated and is doing something funky, but again I don't want to risk damaging working hardware with potentially risky tests. Not nice when a $250 motherboard goes "phut" and emits a puff of smoke when you plug the NIC in.
You are wrong. The problem is both with TP-Link and Asus. This is their official reply to me:
Originally Posted by BradC
Originally Posted by TP Link
So these Asus boards will work with what POE switch ?
Originally Posted by xonacs
Really don't want to experiment and kill the motherboard .
Please, don't destroy this fine switch. Send it to me, I love PoE, have lots of devices powered through PoE and I'm not using crappy ASUS boards.
Originally Posted by kangaroo72