NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Cannot Use FTP Program After WNR2000v3 Install
After a week trying to figure this out, and multiple email exchanges with NETGEAR support, I'm still clueless and it's still not working. I have no idea what to do next, because I don't know what I'm...
OK - what you should have done was add a wireless access point, rather than a router - or - replace your existing router with a wireless router. Multiple routers in a single network are usually a source of grief.
It is possible to configure a wireless router to work as an access point (I'm running a WNR2000 like this right now - because my Linksys access point failed, and I haven't gotten around to buying a new one) - the basic steps are ...
1) Set the wireless router's LAN address to an appropriate one - in your case the correct thing to do is to reduce the DHCP range of the hughesnet router so that you can give the Netgear router an address outside of the DHCP range. The alternative if you can't or don't want to change the settings on the hughesnet router is to select an ip address toward the high end of the range - say 192.168.0.251 (I will explain why later).
2) Disable the DHCP server on the wireless router.
3) Connect the wireless router to the network using one of it's LAN ports - do NOT use the WAN port.
4) Configure the wireless security as desired.
Because this procedure makes no changes to the existing network, your ftp program should not be affected and should continue to work.
Now back to the ip addressing - as you probably know, each device on the network needs to have a unique ip address - if you give the wireless router an ip address within the DHCP server's lease range, it is possible that the DHCP server may give that same address to another device, so you are instructed to set the ip address outside of the server's lease range - this is the correct way to do it.
However - realistically speaking - what are the chances of your having 250 devices attached to your network? Slim to nil - which is why you can usually get away with setting the ip address at the end of the server's DHCP range - you will probably never have enough devices connected for the server to lease that address.
Let me know how things go - also - I am travelling and don't always have internet access so if there's no reply - just check back in a day or two...
It is possible to configure a wireless router to work as an access point (I'm running a WNR2000 like this right now - because my Linksys access point failed, and I haven't gotten around to buying a new one) - the basic steps are ...
1) Set the wireless router's LAN address to an appropriate one - in your case the correct thing to do is to reduce the DHCP range of the hughesnet router so that you can give the Netgear router an address outside of the DHCP range. The alternative if you can't or don't want to change the settings on the hughesnet router is to select an ip address toward the high end of the range - say 192.168.0.251 (I will explain why later).
2) Disable the DHCP server on the wireless router.
3) Connect the wireless router to the network using one of it's LAN ports - do NOT use the WAN port.
4) Configure the wireless security as desired.
Because this procedure makes no changes to the existing network, your ftp program should not be affected and should continue to work.
Now back to the ip addressing - as you probably know, each device on the network needs to have a unique ip address - if you give the wireless router an ip address within the DHCP server's lease range, it is possible that the DHCP server may give that same address to another device, so you are instructed to set the ip address outside of the server's lease range - this is the correct way to do it.
However - realistically speaking - what are the chances of your having 250 devices attached to your network? Slim to nil - which is why you can usually get away with setting the ip address at the end of the server's DHCP range - you will probably never have enough devices connected for the server to lease that address.
Let me know how things go - also - I am travelling and don't always have internet access so if there's no reply - just check back in a day or two...