NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
WNCE2001 and static IP address
I have just bought one of these to use on an xbox but I need the xbox to have a static IP address. So I decided to test it on a Windows 7 PC to and to set it up.
Firstly, is it correct to say that the host ethernet device MUST be configured for DHPC, in other words I don't enter the static address on the host.
Assuming that the host uses DHCP I set the netgear to use a static address of 172.16.0.9. However when I reboot the PC, IPconfig on the PC shows a DHCP address rather than the static one. When I check the netgear admin interface it reports the address as 172.16.0.9 which is correct, but the PC shows a DHCP address on ipconfig.
It seems like the WNCE2001 is accepting the static address setting and then completely ignoring it. All I want is for this device to attach to my wireless network with a static IP address for the host. I've now been changing, reconfiguring for two hours and no matter what I do, the static address setting on the WNCE results in a DHCP address on the PC.
By the way the manual is one of the worst I have seen!
Any ideas?
Firstly, is it correct to say that the host ethernet device MUST be configured for DHPC, in other words I don't enter the static address on the host.
Assuming that the host uses DHCP I set the netgear to use a static address of 172.16.0.9. However when I reboot the PC, IPconfig on the PC shows a DHCP address rather than the static one. When I check the netgear admin interface it reports the address as 172.16.0.9 which is correct, but the PC shows a DHCP address on ipconfig.
It seems like the WNCE2001 is accepting the static address setting and then completely ignoring it. All I want is for this device to attach to my wireless network with a static IP address for the host. I've now been changing, reconfiguring for two hours and no matter what I do, the static address setting on the WNCE results in a DHCP address on the PC.
By the way the manual is one of the worst I have seen!
Any ideas?
10 Replies
reconfiguring for two hours and no matter what I do, the static address setting on the WNCE results in a DHCP address on the PC.
setting up static IP on WNCE2001 will NOT change device behind the WNCE2001.
WNCE2001 is transparent unit once connected to existing wireless. PC and/or device must have static IP if you want pc and/or device needs to have static ip- OK I understand now. That's what I mean about the manual, it's very poor. It's not made clear whether the WNCE2001 acts as a bridge or not.
Why then does the WNCE need to have any IP address information configured into it? Is it only for remote admin?
Thanks for the help! - WNCE2001 is setup for DHCP client so should get IP from existing network
setup will also tell you to use "domain name " to access which will automatically get you to the WNCE2001 interface. wether you use static IP or DHCP Client makes no difference for some and some prefer but that least of problem since it still acts transparent and you can hook up switch behind and connect more than one devices. - The WNCE2001 is a 'Wireless Client'. It's actually so easy to set up. If your router has WPS then press that button on both the router and the WNCE2001. If your router does not have WPS, that's okay just connect it to your computer and launch a web browser and the GUI will launch. If for some reason it doesnt' just go to www.mywifi.ext. Once paired with your network you're all set and can take it from device to device for easy use. I use this on my XBOX360 and have had no issues with online gaming.
- There are also videos on how to set this device up on youtube.com/netgearchannel.:D
- This is how it goes when you install it. after you finish it , open the wifiext.com and setup static IP address that is out side of your DHCP or setup address reservation under router's settings..
Windows 7
Plugs USB power adapter and plug provided ethernet cable to the WNCE2001
Once the Power LED is solid green, unit is "GOOD"
Open the browser and should open URL http://www.mywifiext.com/welcome.htm
Choose language
Hit next and it will go through status bar and look for "available" wireless network with following
SSID name
Channel
Security type
Signal Strength
It also includes "manually input my wireless SSID" for use who hides broadcasting of SSID
Choose your SSID and hit next
Provide your pass phrase and hit next
It will go through the status bar for connecting to the wireless router. After 1~2min it should come up with "You have successfully connected to wireless SSID NAME "
HIt finish. It will also ask you to save to your browser's favorites list. Close the the browser and open browser again
If you are using Win 7 it will ask your "network location" you can close or specify the type and save it - The fact that it has it's own IP-address is a big handicap. This means you can't use it to connect a NAT gateway wirelessly to a wireless ISP.
I currently have a WNR3500L (Wireless gateway) that I use when demoing off site. Often we have access to a guest network wirelessly only so I use a Windows7 box sharing it's wireless internet access via Windows ICS on it's wired network adapter.
Using the WNCE2001 on the wan port of the WNR3500L seemed like a brilliant idea, but requesting ip-addresses for two separate network interfaces through the same wifi-connection brakes this setup.
I need the setup to act as one client computer connecting to the guest network.
Any thoughts on this? I haven't tried the WNCE2001 myself yet because of the rumours about how it operates.
/Basse - ???
"every" network devices MUST have device IP wether one setup using "DHCP CLIENT" or "STATIC IP". This device will NOT do any NAT behind the WNCE2001, just pass the traffic to device behind the WNCE2001Using the WNCE2001 on the wan port of the WNR3500L seemed like a brilliant idea, but requesting ip-addresses for two separate network interfaces through the same wifi-connection brakes this setup.
I need the setup to act as one client computer connecting to the guest network.
this setup is EU's mistake by using WAN port of the 3500 putting double NAT.
you have setup 3500 an accesspoint but DISABLE DHCP and use LAN out of 3500 and connect to WNCE2001. - Hi To all
I have a similar problem with WNCE2001
I am using static ip adresses because the lan port is connected to a lan printer.
I setup correctly the device for connect to a cisco wi-fi. and it work good
The address of the device is:
IP: 10.133.3.196 S/N: 255.255.255.0 : GW: 10.133.3.1
The ip of the printer is
IP: 10.133.3.195 S/N: 255.255.255.0 : GW: 10.133.3.1
At first connection is ok, but after some time i loose the connection to the printer.
If i chenge the ip adress of the printer return to work but for some time and then down again.
Could someone help me?
Thanks - Thread is 2years old. Post your own thread.
Possible the location of the WNCE is not getting the signal
