1.

Solve : Please help me isolate the issue(Powerline Adapter+Router)?

Answer»

So... The issue I am currently having first: Unidentified network/No network access.

I've been using the current powerline adapter(NETGEAR XWN5001) to access the router located downstairs for approximately 6 months. I do not use the WIFI option at all and exclusively use the wired setup of the adapter.

Three days ago, the aforementioned issue started occurring after a night's worth of computer shut down. I turned the computer on, Local Area Connection was stuck "identifying" for GOOD 2-3 minutes, after which it turned into Unidentified network/No network access that I am suffering from. I tried the most basic(and the only) fix I know of, which is unplug everything, wait 2 minutes, power on modem->power on router->plug in adapter downstair->plug in adapter upstair->turn on DESKTOP. Unfortunately, this did not change a single thing(As I relied on this "fix" for decades, I attempted this method at least 5 times hoping the next try would magically fix everything).

The main problem is that I do not know which part of the "network map" is broken... My setup goes: Wall->Modem->Linksys E900 Router->XWN Adapter(downstairs)->XWN Adapter(Upstsairs)->Desktop. I'm fairly certain that this is not a modem/router issue since I can connect to the internet(with very feint signal) using the desktop's WIFI to access the router(with or without the adapters plugged in). So the problem must be within the powerline adapters, right?

However, what perplexes me the most is this: When I access the router using the WIFI, the XWN5001 appears as one of its DHCP clients on LAN interface with an assigned IPv4 Address. When I access the XWN5001 adapter itself using the IPv4 address(typed in browser), it says that its LAN port has IP address, DHCP turned on, and SUBNET mask+gateway IP address are also visible. Doesn't this mean that there's a working connection between the router and adapters?

I can connect to neither the router nor the adapter without WIFI enabled(Shouldn't I be able to if there's a working connection between the router and adapters since everything is wired?).

So... I'm at my wit's end. The modem connects to internet fine, the router seems to work fine(connects to internet via WIFI as mentioned), router seems to be connected to adapters and assign their IP addresses fine, adapter seems to be connected to the computer via ethernet cable fine(I can connect directly to modem with powerline adapters and internet works), but somewhere along the line, the assigned IP address is lost and ipconfig returns APIPA IPv4 address(169.254.x.x) with blank default gateway value when I try ipconfig /all.


Your insight would be greatly appreciated....

Edit: Should've included things I've tried since two days ago(Problem's going on for three):

1. Restart modem/router/adapters/computer
2. Reset TCP/IP Stack with https://support.microsoft.com/en-us/kb/299357 (Actually tried both manual and microsoft fixit)
3. Disable/Enable the LAN adapter
4. Disabled Anti-virus/Firewall
5. ipconfig /release and /renew as administrator ( /renew says "An error occurred while renewing interface Local Area Connection : unable to contact your DHCP server. Request has timed out.")
6. Attempted updating router+adapter firmwares (Both say they are already up to date).
7. Checked DHCP Client service to ensure that it is "Started" and "Automatic." Please clarify this
Quote

My setup goes: Wall->Modem->Linksys E900 Router->XWN Adapter(downstairs)->XWN Adapter(Upstairs)->Desktop.
what is a "XWN Adapter?"
You should have only one device doing DCHP. However, I am not familiar with your XVN adapter. But I doubt it could just change by itself. If you did not change anything, the most liely cause would be either a hardware failure or somebody has installed another device nearby that interferes with your poser line connection.

I would try this: Put both power line units in the same room end see if a good connection can be made. This would confirm they are working normally.


Sorry, I should've just said powerline adapter instead of "XWN Adapter."

I have no idea if powerline adapter always had "DHCP: ON" when everything used to work correctly. Since that appears to be the default value after resetting to factory settings, I can only imagine it did.

I do believe the power lines by themselves are functioning fine since I can connect directly to the modem using the power line adapters from upstairs(Wall->Modem->Powerline downstairs->Powerline upstairs->Desktop). It stops functioning when I introduce the router into the equation, which obviously means that router is creating the issue.

I just do not understand how that can be when it lists the powerline adapter as one of its DHCP clients and apparently assigns an IP value(which, again, somehow gets lost when I try ipconfig on desktop). <---- I have poor networking knowledge and maybe this means nothing and they aren't connecting/communicating correctly at all?


I have no idea if this would help, but here's my ipconfig /all...


Windows IP Configuration

Host Name . . . . . . . . . . . . : Min-PC
Primary Dns Suffix . . . . . . . :
Node TYPE . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : san.rr.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 10-BF-48-87-20-6F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::1879:1fda:4fb6:1964%23(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.25.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 386973512
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-F1-28-04-00-12-17-9D-C1-E3
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : san.rr.com
Description . . . . . . . . . . . : BROADCOM 802.11g Network Adapter
Physical Address. . . . . . . . . : 00-12-17-9D-C1-E3
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2605:e000:1c0e:16b:a922:7313:d0bc:b3b5(Preferred)
IPv6 Address. . . . . . . . . . . : fd6c:9abb:cad1:0:a922:7313:d0bc:b3b5(Preferred)
Temporary IPv6 Address. . . . . . : 2605:e000:1c0e:16b:169:25a4:db59:5e9(Preferred)
Temporary IPv6 Address. . . . . . : fd6c:9abb:cad1:0:169:25a4:db59:5e9(Preferred)
Link-local IPv6 Address . . . . . : fe80::a922:7313:d0bc:b3b5%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.129(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Saturday, April 02, 2016 8:14:58 PM
Lease Expires . . . . . . . . . . : Sunday, April 03, 2016 8:15:02 PM
Default Gateway . . . . . . . . . : fe80::cad7:19ff:fea5:ad79%10
192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 167776791
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-F1-28-04-00-12-17-9D-C1-E3
DNS Servers . . . . . . . . . . . : 209.18.47.61
209.18.47.62
192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{B976B6C9-321F-42E1-96C2-496BD96A18FB}:

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 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.san.rr.com:

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


Discussion

No Comment Found