So, just to close this off, the condo builder sent a technician from the telecommunications company to my unit, and he determined that the jack was, in fact, defective. The jack has now been replaced, and everything seems to be working.
I think the moral of this story is, if you suspect a defective jack, procure a network tester, and test the ...
Okay, here I am with a workaround for this persistent issue. Some more browsing through the internet led me to this solution. I wasn't sure if it would exactly work or not, but I went to the registry editor (made a backup first), and then started applying the workaround.
After logging in to the registry editor as Administrator, went to this adress:
1) You have predictable settings to each ISP
2) Don't need to use 2 labels to each ISP settings
3) Replace find /i ... errorlevel to findstr && || (operators)
4) Replace your labels to if...() else ()...
@echo off && setlocal enabledelayedexpansion
cls & echo/ & for %%i in (1,2
)do "%__APPDIR__%ping.exe" -n 1 dns.ser.ver.%%~...
It depends which category cable you have. CAT5E and higher will support PoE on all voltages. CAT5 will support lower voltages too. Anything lower is not recommended.
Given that CAT5E is a standard for a long time now, chances are high that you currently have CAT5E cables.
That said, PoE have 3 classes.
Class1 has 4 Watt available.
Class2 has 7 Watt ...
Here's some pseudocode to illustrate how to check, brought to you by Crude Hacks 'R Us:
ping DNS.SER.VER.1 | find /I "TTL"
if not errorlevel 1 echo DNS ISP-1 UP
if not errorlevel 1 GOTO CHANGE-ISP-1
ping DNS.SER.VER.2 | find /I "TTL"
if not errorlevel 1 echo DNS ISP-2 UP
if not errorlevel 1 GOTO CHANGE-ISP-2
echo BOTH ISP CONNECTIONS ...
You are correct that symmetric bandwidth on a full duplex connection will give you the ability to have 1Gbps up and down. However, that doesn't mean you will get 1Gbps to all destinations. While it is highly probable that your cloud backup provider has a multi-gigabit connection to the Internet, that doesn't mean they will provide 1Gbps connections to their ...
I know this is from a long time ago - but I just had this same thing happen to me so I figured I'd let you know what the issue was for me. When I added a graphics card my machine would boot, but I couldn't ssh into it, but the normal screen would show up. The issue was my ethernet interface name would change when the graphics card was plugged in. Normally ...
I found an easy solution thanks to Anonymous who commented above with a link to a CentOS bug report. Apparently this is a known issue in the 1062 kernel and the driver is somehow not being loaded in the right order.
A quick fix to immediately activate the Ethernet port is to unload the r8169 driver and then reload it, but this doesn't survive a reboot: