Sign in with
Sign up | Sign in
Your question

local area connection doesn't have a valid ip configuration (Windows 7)

Last response: in Networking
Share
April 26, 2013 7:36:06 PM

Okay, firstly I know that this problem has been seen often and I browsed a few threads where people had the same problem but couldn't find a solution that worked for me.

I'm running on windows 7. We have a router in our house, which other people connect to, however my desktop is too far away from the router to get a decent wireless signal, so I'm currently using a D-Link Powerline adaptor, connected to my computer with an ethernet cable. I'm fairly sure the issue doesn't lie with the adaptor or router.

My desktop says that that it is an 'unidentified network' with no network access. The thread title is what I get when I try to troubleshoot it in the network and sharing centre. I have tried reinstalling the driver for the ethernet, to no avail.

Here is my ipconfig /all:

Quote:
Windows IP Configuration

Host Name . . . . . . . . . . . . : Ben-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home.gateway

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : home.gateway
Description . . . . . . . . . . . : D-Link DWA-160 Xtreme N Dual Band USB Ada
pter(rev.A2)
Physical Address. . . . . . . . . : 00-26-5A-71-D6-F2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:44b8:5130:9800:8845:24a5:eaaa:bdb(Pr
eferred)
Temporary IPv6 Address. . . . . . : 2001:44b8:5130:9800:3141:a760:8bbf:ca61(P
referred)
Link-local IPv6 Address . . . . . : fe80::8845:24a5:eaaa:bdb%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.6(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Saturday, 27 April 2013 12:23:10 PM
Lease Expires . . . . . . . . . . : Sunday, 28 April 2013 12:24:06 PM
Default Gateway . . . . . . . . . : fe80::204:edff:febc:D 11d%12
192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 318776922
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-A6-FA-E0-50-E5-49-BF-4B-96

DNS Servers . . . . . . . . . . . : 2001:44b8:1::1
2001:44b8:2::2
192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Atheros AR8151 PCI-E Gigabit Ethernet Con
troller (NDIS 6.20)
Physical Address. . . . . . . . . : 50-E5-49-BF-4B-96
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::7d5d:2164:58c3:7e2d%11(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.126.45(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 240182601
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-A6-FA-E0-50-E5-49-BF-4B-96

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

Tunnel adapter isatap.home.gateway:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : home.gateway
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
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

Tunnel adapter isatap.{C7B485BB-0872-49FC-A56D-65779EBBA921}:

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
a b $ Windows 7
April 26, 2013 8:00:38 PM

Tunnel adaptor DHCP Enabled. . . . . . . . . . . : No Can you change/enable that
m
0
l
April 26, 2013 11:16:30 PM

ur6beersaway said:
Tunnel adaptor DHCP Enabled. . . . . . . . . . . : No Can you change/enable that


Do you know how I can do that? I've googled around but all I can find is how to enable/disable DHCP for the wireless LAN, not the tunnel adaptors...
m
0
l
Related resources
a b $ Windows 7
April 26, 2013 11:27:51 PM

I suggest you delete the IPv6 entry completely and assign an address manually, something like 192.168.1.100. I came across something similar once when a Powerline adapter also had a wireless capabillity and the LAN was behaving like yours. Is your's also wireless capable?

Another possiblity is the old chestnut Bonjour which comes from Apple, which has a Service you can disable if you suspect it causes this or, if you really want to keep it, change its startup to Automatic - Delayed Start.

m
0
l
April 26, 2013 11:51:53 PM

Saga Lout said:
I suggest you delete the IPv6 entry completely and assign an address manually, something like 192.168.1.100. I came across something similar once when a Powerline adapter also had a wireless capabillity and the LAN was behaving like yours. Is your's also wireless capable?

Another possiblity is the old chestnut Bonjour which comes from Apple, which has a Service you can disable if you suspect it causes this or, if you really want to keep it, change its startup to Automatic - Delayed Start.



I uninstalled Bonjour this morning, I'd heard that it can cause issues.

Can you go into more detail on your first couple of points? Sorry, I'm sorta a novice at this sort of thing. Also my Powerline adaptor is not wireless capable, I'm pretty sure. It only supports the use of Cat5 cables.
m
0
l
a b $ Windows 7
April 27, 2013 11:28:27 AM

In the connection's Properties pages, take the tick out of Microsoft TCP/IP v6 then below that, highlight Internet Protocol (TCP/IP) and click on Properties. Blob the Use the following address button and in the top box, type 192 then 168 1 100, click in the first box of the subnet and the rest completes itself and in the Gateway section, put in 192.168.1.254. Enter that same gateway below in the DNS box, click Apply and OK your way out. Restart the computer and see if that manually assigned address helped.
m
0
l
!