Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Lan connection showing up as unidentified


  • Please log in to reply

#1
McGufter

McGufter

    Member

  • Member
  • PipPip
  • 17 posts

Hello,

 

 I have a small issue with the Lan connection with windows 7. I have wireless but its an old pci card so I wanted to connect via ethernet as well. The issue is that the ethernet connection is comming up as unidentified.

I see this is not an uncommon problem, plenty of similar issues on forums but the soultion seems to vary, and looks like it needs some degree of expertise which I don't have.

 

I have updated the driver for the lan controller.

Disconnected the poiwer for a few hours.

Disabled and enabled a few times.

as were suggestions found on line but to no avail.

 

here is the ipconfig, I would be grateful if someone can suggest a solution to the problem.

 

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Tim Roofer>ipconfig/all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Pikey
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : sitecom.router

Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . : sitecom.router
   Description . . . . . . . . . . . : Sitecom Wireless Network PCI Card turbo g
 WL-171
   Physical Address. . . . . . . . . : 00-0C-F6-1D-A7-9F
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::6491:2675:966b:30c1%13(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.104(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 21 September 2014 13:40:44
   Lease Expires . . . . . . . . . . : 28 September 2014 13:40:48
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 369102070
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-A6-01-1C-6C-F0-49-51-9F-0A

   DNS Servers . . . . . . . . . . . : 192.168.0.1
   Primary WINS Server . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller #2
   Physical Address. . . . . . . . . : 6C-F0-49-51-9F-08
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::390f:20bd:a017:c8db%12(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.200.219(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 309129289
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-A6-01-1C-6C-F0-49-51-9F-0A

   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : 6C-F0-49-51-9F-0A
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{1DF20369-9E68-485C-A25F-E7E401424A9C}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.sitecom.router:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : sitecom.router
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{FE57D934-A99E-445A-900D-18C971ACEB76}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

C:\Users\Tim Roofer>


  • 0

Advertisements


#2
SpywareDr

SpywareDr

    Member 3k

  • Member
  • PipPipPipPipPipPip
  • 3,822 posts
Ethernet adapter Local Area Connection 2:

   Autoconfiguration IPv4 Address. . : 169.254.200.219

 

 

That "169.xxx.xxx.xxx" IP address means that Windows cannot find a network to connect your Ethernet card to.

 

Are you sure the ethernet cable is known-for-a-fact-to-work?

 

What is that cable plugged into ... on both ends?


  • 0

#3
McGufter

McGufter

    Member

  • Topic Starter
  • Member
  • PipPip
  • 17 posts

Hello Spyware Dr and thanks for the reply.

 

   I am attempting to use a tp-link powerline adapter, so there are 2 cables, one of which I have checked and the other I will check tomorrow and let you know.

The cable is plugged into the router by the modem and then to the tp-link unit plugged into the wall and then on the other end the cable is plugged into the other tp-link unit and into the ethernet port on the back of the computer. 

thanks.


  • 0

#4
Ztruker

Ztruker

    Member 5k

  • Technician
  • 7,091 posts

Power-line adapters are finicky. I've used them before and it often takes me several attempts before I get them to communicate with each other successfully.

 

One easy way to check is to move the computer close enough to the router so you can connect via a Ethernet cable. If that works then it's the Power-line adapter that is the problem.


  • 0

#5
McGufter

McGufter

    Member

  • Topic Starter
  • Member
  • PipPip
  • 17 posts

Sorry about the delay in getting back to this thread, I checked both cables and they work, the next step is dragging my computer downstairs and going directly into the router. we shall see how this goes. I appreciate the feed back, thanks.


  • 0

#6
Ztruker

Ztruker

    Member 5k

  • Technician
  • 7,091 posts

If it works when wired then keep them close together so you can see both Powerline Adapters and try setting them up. Once you get them working then move upstairs and repeat the sequence you used to connect them.


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP