Maybe this is common knowledge but I'm scratching my head over it and didn't pull any quick answers via Google so I'll throw it out here to see if anybody either has a fix, or at the very least has seen it before.

I'm currently running an older trendnet powerline kit, and while it appears to be working as advertised the Ethernet port it's connected to is reporting as "not connected". I suspect it's something to do with a signal it's expecting to get from the powerline adapter but as I said I wasn't able to come up with a definitive answer via google.

Any ideas?

KaptCrunch

April 10, 2013 01:11 PM

your firewall / AV may be the issue ...not a trusted port

or your power nic died

sswilson

April 10, 2013 01:23 PM

Quote:

Originally Posted by KaptCrunch
(Post 701879)

your firewall / AV may be the issue ...not a trusted port

or your power nic died

But that's the point.... there's absolutely nothing wrong with the connection through the powerline adapter other than the fact that windows reports the Ethernet cable being unplugged. (and no... I completely disconnected the wireless adapter so I know it's getting through to the network / internet through the port that claims to be disconnected).

I even went so far as to double check that there weren't two e-net ports on the motherboard.... ;)

KaptCrunch

April 10, 2013 01:43 PM

tried a known good cable ?

doh windows report un plugged means

not connect to web / lan

sswilson

April 10, 2013 01:46 PM

Quote:

Originally Posted by KaptCrunch
(Post 701891)

tried a known good cable ?

Good idea... it's a new cable so maybe it's not passing the "connected" signal back. (I'm not even sure if there is such a line signal that wouldn't affect actual connectivity).

KaptCrunch

April 10, 2013 01:52 PM

Quote:

Originally Posted by sswilson
(Post 701892)

Good idea... it's a new cable so maybe it's not passing the "connected" signal back. (I'm not even sure if there is such a line signal that wouldn't affect actual connectivity).

Can't say for sure as I don't have access to that PC screen ATM (It's the living room PC hooked up to the TV... ;) ) but again, I have network and internet connectivity through the port and I'm measuring data speeds on the upstairs adapter (Slave) through the util software installed on a PC connected to the same switch as the downstairs adapter (Host) so the cable is working even if Win7 doesn't think it is. :)

Once I have access I think I'm going to delete the nic from device manager and let it pick up the drivers / stack again.

edit: Ok, it's the PC... I'm getting a proper connection through the cable on my laptop. I'll dump the nic in device manager to see if it picks up the drivers, if that doesn't do it I'm just going to leave it as is since it's working fine. :)

grinder

April 10, 2013 03:27 PM

i've seen this on windows 7 machines if they sense a lag in finding DNS servers... the systray will have a yellow explanation warning saying "local only, limited internet" but internet works perfectly fine.