i hate lan maintenance so much

why is this not working? because i have no idea what i'm doing. my wireless is working flawlessly. my powerline networking units are not. they've been fine for months. do i need to do something on my router to make them work? i reset from the router web interface and just got new firmware, still nothing.

so an ip finder site says my ip is: (i replaced some numbers with q for privacy sake, though i have no idea if that matters)
75.qq.77.57

why is my wireless ipv4 pointing at what looks like my home ip while my lan ethernet card is pointing some 169 number? is that normal? and is my subnet mask supposed to have two zeroes at the end?

wired
Autoconfiguration IPv4 Address. . : 169.qqq.29.146(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0

wireless
IPv4 Address. . . . . . . . . . . : 192.qqq.1.106(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0

Code (text):

1. Windows IP Configuration
2.  
3.    Host Name . . . . . . . . . . . . : Experiment626
4.    Primary Dns Suffix  . . . . . . . :
5.    Node Type . . . . . . . . . . . . : Hybrid
6.    IP Routing Enabled. . . . . . . . : No
7.    WINS Proxy Enabled. . . . . . . . : No
8.  
9. Wireless LAN adapter Wireless Network Connection 2:
10.  
11.    Media State . . . . . . . . . . . : Media disconnected
12.    Connection-specific DNS Suffix  . :
13.    Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
14.    Physical Address. . . . . . . . . : 88-9F-FA-5D-38-9A
15.    DHCP Enabled. . . . . . . . . . . : Yes
16.    Autoconfiguration Enabled . . . . : Yes
17.  
18. Ethernet adapter Local Area Connection:
19.  
20.    Connection-specific DNS Suffix  . :
21.    Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
22.    Physical Address. . . . . . . . . : 78-2B-CB-7D-07-F4
23.    DHCP Enabled. . . . . . . . . . . : Yes
24.    Autoconfiguration Enabled . . . . : Yes
25.    IPv6 Address. . . . . . . . . . . : fd36:25bf:8509:0:ec65:771c:qqqq:1d92(Pref
26. erred)
27.    Temporary IPv6 Address. . . . . . : fd36:25bf:8509:0:a091:27d7:qqqq:fc03(Pref
28. erred)
29.    Link-local IPv6 Address . . . . . : fe80::ec65:qqqq:50da:1d92%11(Preferred)
30.    Autoconfiguration IPv4 Address. . : 169.qqq.29.146(Preferred)
31.    Subnet Mask . . . . . . . . . . . : 255.255.0.0
32.    Default Gateway . . . . . . . . . :
33.    DHCPv6 IAID . . . . . . . . . . . : 293088203
34.    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-D2-BD-qq-78-2B-CB-7D-07-F4
35.  
36.    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
37.                                        fec0:0:0:ffff::2%1
38.                                        fec0:0:0:ffff::3%1
39.    NetBIOS over Tcpip. . . . . . . . : Enabled
40.  
41. Wireless LAN adapter Wireless Network Connection:
42.  
43.    Connection-specific DNS Suffix  . :
44.    Description . . . . . . . . . . . : DW1501 Wireless-N WLAN Half-Mini Card
45.    Physical Address. . . . . . . . . : 88-9F-FA-5D-38-9A
46.    DHCP Enabled. . . . . . . . . . . : Yes
47.    Autoconfiguration Enabled . . . . : Yes
48.    Link-local IPv6 Address . . . . . : fe80::e4a3:6578:451b:5214%10(Preferred)
49.    IPv4 Address. . . . . . . . . . . : 192.qqq.1.106(Preferred)
50.    Subnet Mask . . . . . . . . . . . : 255.255.255.0
51.    Lease Obtained. . . . . . . . . . : Wednesday, December 19, 2012 5:17:08 PM
52.    Lease Expires . . . . . . . . . . : Thursday, December 20, 2012 5:23:44 PM
53.    Default Gateway . . . . . . . . . : 192.168.1.1
54.    DHCP Server . . . . . . . . . . . : 192.168.1.1
55.    DHCPv6 IAID . . . . . . . . . . . : 193503226
56.    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-D2-BD-qq-78-2B-CB-7D-07-F4
57.  
58.    DNS Servers . . . . . . . . . . . : 192.168.0.1
59.                                        192.168.1.1
60.    NetBIOS over Tcpip. . . . . . . . : Enabled
61.  
62. Tunnel adapter isatap.{7CEECD1D-7395-44DC-A5A2-DB8097E9D36D}:
63.  
64.    Media State . . . . . . . . . . . : Media disconnected
65.    Connection-specific DNS Suffix  . :
66.    Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
67.    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
68.    DHCP Enabled. . . . . . . . . . . : No
69.    Autoconfiguration Enabled . . . . : Yes
70.  
71. Tunnel adapter Local Area Connection* 9:
72.  
73.    Media State . . . . . . . . . . . : Media disconnected
74.    Connection-specific DNS Suffix  . :
75.    Description . . . . . . . . . . . : Microsoft 6to4 Adapter
76.    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
77.    DHCP Enabled. . . . . . . . . . . : No
78.    Autoconfiguration Enabled . . . . : Yes
79.  
80. Tunnel adapter Local Area Connection* 13:
81.  
82.    Media State . . . . . . . . . . . : Media disconnected
83.    Connection-specific DNS Suffix  . :
84.    Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
85.    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
86.    DHCP Enabled. . . . . . . . . . . : No
87.    Autoconfiguration Enabled . . . . : Yes
88.  
89. Tunnel adapter isatap.{7FADF466-2B17-4F5E-B3F0-C380CA53108B}:
90.  
91.    Media State . . . . . . . . . . . : Media disconnected
92.    Connection-specific DNS Suffix  . :
93.    Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
94.    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
95.    DHCP Enabled. . . . . . . . . . . : No
96.    Autoconfiguration Enabled . . . . : Yes

169.whatever means your Ethernet adapter isn't getting an IP address assigned to it by the router.

Can you post your network topography? Something is happening that's causing DHCP to occur over wireless but not over the wired interface.

okay that's weird, i just noticed my lan is marked as public. wtf.


doing the network map thing from the control panel's network and sharing:
this one is for my lan:
"windows cannot create the network map because the network's location type is public"


this one if for my wireless:


Uploaded with ImageShack.us




and there's the network listed as public with no link to change it to home.



Uploaded with ImageShack.us

How are your powerline adapters connected to the rest of your network?

router > powerline adapter > upper floor into electrical outlet > lower floor powerline adapter > pc (these were working normally till yesterday, no extension cords or power strips)

It's most likely a problem with the powerline adapters themselves. If one of them is defective or malfunctioning, the computer will see a network connection, as if it was plugged into a switch or a router, but without DHCP functionality Windows assigns it that useless private address.

Check the connection between the router and the powerline adapter, and if they have some sort of configuration menu see if you can access both of them.

Am I the only one who saw this thread and wondered "Who is Ian Maintenance?"

Probably.

Ok..
169.x.x.x can mean several things. 1 is that the router isn't seeing the attached device to the computer. 2 means that the tcp/ip stack is fooey and windows doesn't remember how to ask for one. 3 is that the adapters themselves are fooey and aren't talking.. this would be does the power outlet still give power? 4 the router itself has decided that the wireless is the primary focus.

I used to tech these but they were a real pain in the ass. Possibilities for trouble shooting. 1 ..get the powerline adapter from the farthest bring it to the router , plug it in locally different outlet but somewhere near. If this works you have an issue between where your router is, and where you want the powerline to work.


Was there weather recently, lighting so on. Power adapters are per my old knowledge, extremely sensitive to shorts /power fluctuations

It is always worth it to check the connectors between router and powerline adapter, powerline adapter and computer for issues, try new cords so on. If this is usb connected to the computer not getting an ip address, try a different port.

I would check the router home page for issues on this firmware update, and see if you need to directly connect via a lan card to reset it/get the powerline working again.

One of many results for Ian Maintenance. God I hate this guy.

The man who made you wish for William "14 pints" Hague to come back. No one thought that would happen.

direct connection from the router did not work either. upon closer examination of the router and some untangling i noticed the wire coming out of port 2 was going into port 3. after unplugging, issue resolved. case closed. trouble ticket marked as fixed. the rest of the dominoes should fall like a house of cards. checkmate.

oh man, loopbacks can cause all sorts of weird shit to happen.

Ain't it always a wire at the wrong place and wrong time, had a friend that was screaming at his new pc because it wouldn't connect. Turns out in the process of getting sad new pc in place he twisted and mangled the ethernet. No obvious damage to the cord but cord was kaput. I encouraged him to check his wiring, but he did not. After much fussing and calling the pc's tech support he comes back with the above information.

I then laughed at him.