NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
XET1001 setup issue
I have 2 powerline XET1001's. One is hooked into my router and the other in another room. On both units, the power light is on solid, the blue light and other green light are flashing as they are supp...
Hello Builder 55,
I have the same issues. I found this info in the forum. I am going to try this out.
Got this all working, here's how:
Issue was that my home network used subnet 192.168.1.x while the powerline devices I purchased used 192.168.100.y and I could not change that fact. Needed home office and multimedia devices in living room to be on same subnet so as to share data such as music files and Samba Share on mediaserver for windows clients.
Noticed that Powerline Devices are hard coded to 192.168.100.1 and 192.168.100.13 respectfully by observing them one at a time inside my Netgear Routers Attached Devices screen(swapped them around to get IPs). Could not change their IP's.
Set my router to 192.168.1.1 base IP but this appeared to conflict with the powerline device so I did the following:
1. Set Router base IP(Gateway) to 192.168.100.20 (plenty of room for the powerline devices and any additional I might add)**
2. Set DHCP pool in router from 192.168.100.40 thru 192.168.100.254
3. Left 192.168.100.21 thru 192.168.100.39 free for static IP for any devices in living room or elsewhere.
** If IP's are tight for you you could setup reservations in your router admin console for the powerlines specifically.
Everything now works. Linux multimedia server in living room can see internet and home office windows and Mac clients can see the shares/mounts. If you have a Linux mediaserver like me, ensure you set the nameserver's to 127.0.0.1 and 192.168.100.20 (in /etc/resolv.conf )....or whatever you had to set your Gateway/router base IP to based on the annoyingly hard coded IP's on the Powerline devices.
Hope this helps some,..had me stymied for two weeks.
Thanks
mustang7173
I have the same issues. I found this info in the forum. I am going to try this out.
Got this all working, here's how:
Issue was that my home network used subnet 192.168.1.x while the powerline devices I purchased used 192.168.100.y and I could not change that fact. Needed home office and multimedia devices in living room to be on same subnet so as to share data such as music files and Samba Share on mediaserver for windows clients.
Noticed that Powerline Devices are hard coded to 192.168.100.1 and 192.168.100.13 respectfully by observing them one at a time inside my Netgear Routers Attached Devices screen(swapped them around to get IPs). Could not change their IP's.
Set my router to 192.168.1.1 base IP but this appeared to conflict with the powerline device so I did the following:
1. Set Router base IP(Gateway) to 192.168.100.20 (plenty of room for the powerline devices and any additional I might add)**
2. Set DHCP pool in router from 192.168.100.40 thru 192.168.100.254
3. Left 192.168.100.21 thru 192.168.100.39 free for static IP for any devices in living room or elsewhere.
** If IP's are tight for you you could setup reservations in your router admin console for the powerlines specifically.
Everything now works. Linux multimedia server in living room can see internet and home office windows and Mac clients can see the shares/mounts. If you have a Linux mediaserver like me, ensure you set the nameserver's to 127.0.0.1 and 192.168.100.20 (in /etc/resolv.conf )....or whatever you had to set your Gateway/router base IP to based on the annoyingly hard coded IP's on the Powerline devices.
Hope this helps some,..had me stymied for two weeks.
Thanks
mustang7173