WRT54G2 V1 Fails to get WAN DHCP address

Hi All,
I have a new WRT54G2 V1 that works fine, with the exception it will not pickup a DHCP address from the cable modem. I have gone through the standard steps assuring the modems, cables and computers work on other setups and have no issues there.
The wireless and hub portions of the G2 work as usual. I flashed the firmware to the latest FW_WRT54G2V1_1.0.04.005_US and there is no change in operation, also the G2 responds correctly to a full reset to factory settings.
On the router's reboot the WAN light comes on briefly (assume self-test), but remains off after the router is fully booted.
Have I forgotten something obvious, or is this an out-of-the-box failure ?
Cheers,

Once more step which you can try is, connect the Ethernet cable to the LAN Port 1 and the other end of that cable to the Internet Port of the Router and then check if the WAN light on your Router lids or not...
If it still doesn't lid, then i think it might be the problem with the Router itself, and you need to replace your Router.

Similar Messages

RVS4000 won't get WAN DHCP address

I just tried replacing a cheap domestic router/switch with an RVS4000 V2 on our work network. This has a WAN connection to a cable modem for internet access via a dynamic IP address.
When I first connected the RVS4000 it got a WAN ip address via DHCP of 192.168.100.11. This is the type of IP address we get when there is an upstream problem with our ISPs cable network, and sure enough we had no internet access. The RVS4000 was set to use DHCP on the WAN interface. So I logged a support call with our ISP but they said there were no problems at their end.
I then swapped the RVS4000 out for the original router. This worked fine and got a WAN DHCP address of 77.xxx.yyy.zzz as it should. Swapped back to the RVS4000 and back to the same problem of getting a 192.168... address.
So, I downloaded the latest firmware from Cisco, which was V2.0.3.2 and flashed the RVS4000.
I then tried again connecting the RVS4000 to the cable modem but this time it would not get any WAN DHCP address at all. On the Status/Gateway page of the web interface it said that the WAN interface was down. However, on the front panel there was a yellow light indicating a live connection on the internet port.
Any suggestions? I am assuming there must be a fault, but thought I would check for advice before sending it back.

Hi Nick,
Connect your computer directly to the modem, obtain the right IP address. Then put the RVS4000 back to the modem connection. Go to the set up, MAC ADDRESS CLONE, Enable this feature then use the option "clone my pc mac".
Then wait 1-2 minutes and refresh the WAN.
Basically this feature puts your computer's MAC on the router WAN interface. You can also use the previous router's WAN MAC if you know it and want to manually type it in.
-Tom

Hyper-V - Legacy NIC not getting DHCP address at boot, but when OS loads the NIC gets a DHCP address

Hi, I have a strange issue with DHCP.
I have a lab environment on a single Hyper-v 2012 Server. AD, DNS & DHCP exist on a single virtual machine, I have a flat network 192.168.1.x, all VM's are on this network. I have authorised DHCP and Setup the scope.
A VM has a legacy adaptor, the legacy nic is configured in the boot order as the first device.
When I boot the machine I do not get a DHCP address, however when the OS boots the Legacy NIC then gets a DHCP address??
I need to use a legacy NIC as I need to PXE boot the VM, however I should get an IP address at boot time, which I don't get.
I have run Wireshark on the DHCP server, I can see the legacy NIC do a "DHCP Discover and the DHCP Server respond with a DHCP Offer" however all communication ends there. I have disable all firewalls and I see no reason for this not to work.
I have done tis before with no issues but I am unable to get this to work on this server!!!!!

Hi
According to your description , it is recommended to make sure or do :
        In your environment , there is no any other valid DHCP, BOOTP or proxy DHCP offers.
        Make sure if the DHCP server is overload.
        So suggest to test that creating a new “internal virtual switch” and change the settings of VM which provide DHCP service to connect to the new “virtual switch”.
        Then create a new VM use legacy NIC also connect to the new “internal virtual switch” and try to PXE Boot.
Hope this helps.
Best Regards
Elton ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Cannot get a DHCP address from my ISP

I just got a WRT54G router, I managed to configured it all. I can ping any computers on the network. What I cannot do is get my DHCP address from my isp, meaning that I can't connect to internet.
I am 100% sure that my ISP address was given by a DHCP server since that's how it was configured on my old router before it got smashed into pieces.
I have the latest firmware upgrade for the router (version 6) and it is correctly plugged in my modem.
What is strange is that couple of hours ago, I managed to get an address for about 15 minutes, then it dropped and I have not been able to pick a new one anymore, no matter what I do.
Anyone can help me?

Achnod wrote:
Alright, but how do I do that?
Disconnect the power cord.
Or if its a telephony modem, hold the reset button until it reboots.

CRIO failing to get a DHCP assigned address

I just went through heck with my IT deparment on this so thought I'd post it here.
I had four cRIO-9073s on a remote switch in one of our labs, that MAX (Measurement and Automation Explorer) was saying were using Link-local addresses. In fact, all were using the EXACT SAME address: 169.254.62.215. Very strange! I was able to talk to them using MAX some times, doing remote restarts, etc., but other times not. All were configured to grab a DHCP address or fall back to link-local.
As it turns out, the RIOs were attached to a Cisco switch that has a feature callled STP fully enabled on all ports. STP is designed to prevent accidental loops in the network from downing your network, and that feature blocks all initial transmissions from attached devices for 30 seconds before letting them through, while it "listens" and "learns" about your device, analyzing to make sure that letting it connect won't create a loop. Apparently this 30 second delay (forever in computer terms!) is too long for the cRIOs, so they take a link-local address, and since they can't even check the network for other link-local users because their transmissions aren't being forwarded, they all take the exact same address. I'm still amazed MAX can find them under these conditions!
The way to get it working is to turn on "PortFast" on the Cisco switches, which simply disables the steps in STP that cause the slowdown (blocking, listening, learning). Fortunately this can be done on a port-by-port basis, as it's recommended to NOT turn it on if ports are going to another switch (as that then opens the door for a loop).
Here's more info:
http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a00800b1500.shtml
Here's hoping you don't need this!

Hello Erik,
Thank you very much for the post. Great work figuring out the root cause of your communication issue!
Cameron F
Applications Engineer
National Instruments

OS X 10.6.7 not getting reserved DHCP address from router.

I have a MacBook Pro running OS X 10.6.7
My router is NetGear WGT624v3. I have the router setup to assign out reserved DHCP address for my Macs.
I am not getting the reserved address, but rather "any" address in the pool.
Other types of devices are getting the reserved address. For example, old windows computers, and my Android phone. Only the Mac computers seem to be getting the incorrect addresses.
Any ideas please?
Duane

As long as it shows up in the Windows Boot Camp control panel I'd say fine, happened to a lot of people - I have not had Windows 7 show in Mac Startup Disk control panel for years in my Mac Pro.

RVS4000 v2 when VLAN used Vista computers can't get a DHCP address.

Just bought a RVS4000 v2. Firmware v2.0.0.0.3. All worked fine when using factory default settings. But I bought this because I wanted to implement VLANs. I defined VLAN2 for the VOIP phones connected through a switch to Port 1. I also defined VLAN3 for my accounts computers, whose switch connects to port 3. All VLANs are defined by Port, untagged.
The phones, using Linux, pick up an IP address fine. So do the two remaining W2K systems. XP systems do but rather slowly. Vista though just hangs for a while, then uses an autoconfiguration address and won't connect unless I spoecify the IP settings. However if I connect the same Vista system to a port which uses the default LAN, it gets an IP address fine. I haven't tested Win7 yet.
Why? Is this a bug in the firmware, or just a bug in Vista?

May be a bug. A Wireshark trace might be illuminating.

Slingbox Pro can't get a DHCP address from my WRT310N router

Reset my Slingbox and on my router Dhcp table I see a dhcp address for 58 seconds but the slingbox network light keeps flashing. Then the address disappears and the slingbox network light continues to flash. Have tried changing the router, same issue.

You can try this link and follow the steps, i think it will help you in fixing your problem.
If possible connect a different Cat5 Cable from your Router to the Slingbox.

Windows will not get a DHCP address from my OS X Server

Is there a trick I need to do to get my windows machines to get and address from my OS X Server?

i have had the same issue. Windows clients (XP, 2003, 7) just could not receive an address from the dhcp server.
I think i got it solved by removing an invalid line in my dhcp server config file.
This is what i did:
stop dhcp server
open /etc/bootpd.plist (you need admin rights to edit)
remove the following two lines:
<key>dhcp_domain_name</key>
<string></string>
save file
start dhcp server again
alternatively, you can fill the dhcp_domain_name with a valid domain name suffix. Both options seem to have worked just fine for me.
<key>dhcp_domain_name</key>
<string>whatever.mydomain.com</string>
Tips:
I am using Sublime Text for such tasks. It asks for administrator password when trying to save the file, much more convinient than trying to use TextEdit
To get to the /etc directory from your favorite text editor easily: Go to the standard open file dialog. Press Cmd+Shift+G. Type /etc and press enter
also see the official documentation:
https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/ man8/bootpd.8.html
dhcp_domain_name
The default DNS domain name (option code 15). If this property is not
present, the server will supply its own default domain name (if available).

PCs failed to get dynamic IP Addresses?

Greetings,
PCs from VLAN 10 cant receive dynamic IP Addresses from the Multilayer Switch(MSHQ3), which i configured it with DHCP. MSHQ3 is connected to a switch(SHQ1), SHQ1 is configured with trunk port and only will receive VLAN 10 from MSHQ3, and access ports are configured to the PCs. The pkt file is attached here. Please help. :-(

SOLVED!
Just changed the connection from cross-over to straight through between the switch and the multilayer switch.

AEX fails to get DHCP address, but works on DLink

Sorry for the long post -- I'm hoping the details will help you diagnose the problem faster in the long run.
My DLink router gets a DHCP IP address from the (Comcast) cable modem, but when I switch to the AirPort Extreme (5th gen, refurbished), it doesn't. It shows an autoconfiguration IP address of the 169.254 variety, suggesting that DHCP isn't working for the AEX. (Just fyi, my girlfriend's macbook can connect to the AEX and get 10.0.1.x IP addresses; I can ping the AEX over wifi.)
Airport Utiltiy shows a red number 2 with a single error indicating Internet failure to get IP address or something. The suggested solution is power-cycling the modem; failing that, contact the ISP. Contacting Comcast was amusing but useless...they gave me instructions for setting up AEX with a DSL modem -- twice -- without understanding my objection!
The AEX is configured for DHCP (not Static or PPPoE), and uses all stock settings (I did both a soft reset and used the Airport Utility to restore default settings...not sure if those two are the same).
I've tried power-cycling the router and cable modem numerous times, including leaving them off for 15+ minutes and leaving the AEX connected for 6+ hours. I tried using the DLink to release the DHCP reservation and then quickly switching the cable over to the AEX.
I read somewhere that resetting the "CMTS (cable modem termination system)" might help. I mentioned it to the Comcast tech support, but they didn't respond.
At this point, I'm not sure what else to try. It could be the refurbished unit is broken, but 95% of the time these sorts of things are configuration issues. (I know a fair amount about networking, but I'm new to Apple products so I could be doing something stupid.) I may try connecting the AEX to the LAN side of the DLink to see if it can get a DHCP address from that...but I'm clearly grasping at straws.
<whimpers>...Help?

Update: The AEX does get a DHCP address when connected to the LAN side of the DLink gateway. (But the AEX doesn't get one when connected directly to the cable modem. Yet the DLink gets a DHCP address when connected to the cable modem.) So...??!?!!!

Airports fail to serve DHCP addresses

I am having trouble reconfiguring an existing network with 2 Airport devices -- switching to having the Airports serve addresses via DHCP is failing, and would appreciate help determining what I'm doing wrong here.
Details:
I have a network with a 16-IP public address space x.x.x.208-223. My DSL router/firewall is at x.209, and I have various devices with manually assigned statics IPs in the x.210-x.218 range. The router is configured to serve up the last 4 IP addresses x.219-x.222 via DHCP. Within the static IP range, I have a Time Capsule at x.210 and an Airport Express at x.214, located at far ends of the house, and running differently named wireless networks. They have so far been configured with [Connection sharing: Off (Bridge Mode)] Under Internet > Internet Connection and appropriate manual settings under Internet > TCP/IP.
All has worked fine with this configuration to-date. Our few devices without a static IP were assigned DHCP addresses from the 219-222 range, whether connected via our hard-wired ethernet network, or over either wireless network -- the addresses picked up from the router at 209.
While the 4 addresses available by DHCP were previously sufficient, with the proliferation of mobile devices in my family, it's not enough anymore, and I am trying to reconfigure the Airports to serve up private network blocks 10.0.x.x and 10.0.y.y via DHCP [Connection sharing: Share a public IP address]. This is not working. When I reconfigure either Airport in this manner, network devices connecting via wireless no longer can connect to the internet. Connection to the wireless network itself is fine, but the device is unable to get a DHCP address from the Airport. Instead, after a short delay it gets a self-assigned address in the 169.254.x.x range. This happens with either Airport base station, and both with my iPhone 4 as well as my MacBook Pro.
Thinking that having the router serve DHCP within the public space might be interfering with the Airport DHCP in its own private block, I tried disabling DHCP at the router. Even so, I cannot get the Airports to start serving IP addresses to their wireless clients.
Any suggestions ?

Hi Linc,
I appreciate the discussion. Let me reply in-line
Linc Davis wrote:
I'm having a lot of trouble understanding your questions. Rather than trying to figure it out, let me tell you how it should work.
You have a DSL modem that is also a router. It gets an address for its WAN interface from your ISP's DHCP server, or it has a static address -- doesn't matter which.
My router has a static WAN IP address, which is in my ISP's subnet. The LAN is my own public subnet 209.128.72.208/28, and the router's LAN IP address is 209.128.72.209.
It had better not be serving DHCP on the WAN, or you may get kicked off by your ISP. I'd be surprised if you were even able to configure it that way.
No, it's not serving DHCP on the WAN. It is serving DHCP only on the LAN, in the 209.128.72.219-222 range.
The router's LAN interface has a fixed private IP address that you configure. It serves DHCP to other devices on the LAN.
Yes, that is how it is.
The AE can get an address from the router for its Ethernet port from the router, or it can have a fixed address, whichever you want.
Yes, it is configured with its own static, manually configured address, which is 209.128.72.214, outside of the DHCP range served by the router.
Set it to operate in bridge mode, which means that the wireless network will be like an extension of the wired network, with the same address pool. Wireless devices will get their addresses from the router.
Yes. To-date I have operated it in bridge mode, exactly that way. And it's worked great up until now. Devices with manually assigned IP addresses in the 209.128.72.210-218 range have worked fine either when connected by ethernet or wireless, and those without (iPhones, etc) have picked up DHCP addresses from the router just fine.
The AE does not need to be a DHCP server.
Unless your needs are very unusual, that setup will work for you.
And so it has worked that way for a while. However, my needs have changed recently. The range of available IPs for DHCP from the router is limited to 4 devices (209.128.72.219-222). That worked fine when we had only 4 devices (iPhone, iPad, Roku, and Blackberry). Now, the kids have wireless devices (iPod touch and an old iPhone). The available range is not sufficient for 6 devices. So, rather than serve wireless devices with addresses from the limited remaining IPs in the public subnet, I want to have the AE serve DHCP in a private network 10.1.x.0/24 , which obviously has alot more room.
I'm willing to try turning off DHCP on the router completely. That doesn't seem to help -- I've tried it twice.

Linksys WRT54GL won't get dhcp address from isp

I'm using Linux.
I just bought this router because it had good reviews on Newegg but for the past 4 hours I have gotten nowhere with it.
When I connect the router to the net and click the refresh button on the browser interface, the router doesn't go out and get a dhcp address. I see the initial click of the mouse that hits the modem but no information comes back. No addresses are updated.
I have tried cloning the mac address but that does no good either.
Any hints appreciated.
Thanks

Try resetting the router for 30 secs in such a way that power light is blinking on the router.Also, try doing the complete network power cycle i.e., unplug the power cables from the modem & from the router.Then, plug in the power cable to the modem first once all the lights are solid on the modem you could plug in the power cable to the router & then try configuring the router & it will definately work!!!

WRVS4400N Unable to get DHCP address via wireless

I am having an issue with the WRVS4400N. I am unable to get a DHCP address via wireless. If I connect directly to the router via RJ45, I get a dhcp address an and able to get to the internet. Has anyone ran into this issue.

This seems to be a problem with the latest firmware (v1.01.03) available from Linksys for this router. The stock firmware for my WRVS4400N router assigned DHCP addresses to wireless devices without any issue. As soon as I upgraded the router to v1.01.03, the router no longer assigns DHCP addresses to wireless devices. I have verified there is no issue with the router itself by rolling back to version 1.00.16 with the recovery utility.
One workaround I noticed with firmware v1.01.03 is that the router will actually assign DHCP addresses to wirelss devices temporarily if it assigns a DHCP address to a device connected to the physical port. This only last for a little before the router stops giving out DHCP address to wireless devices though. It's a shame since I was looking forward to some of the features in the v1.01.03 firmware.
Chuck

No Hyperv Virtuals get DHCP address - but Physical Host Can

HyperV Server 2012 Core on a dedicated machine on local domain.
Machine connected directly into local network that has a DC running DHCP.
None of the VM's can get a DHCP Address from the server. Even if i set static addresses still they cannot route anywhere, cannot even ping the HyperV server they are sat on but other local machines can!!!!
The physical host cant ping the
The physical HyperV server has no problem getting a DHCP address or any routing issues, nor do any of the other clients on the local network, including another HyperV server running server VM's
What ive tried so far
Deleted Virtual Switch and removed the NIC from the virtual hosts in HyperV Manager- then re-adding new one.
Put in a different network card
Removed Physical host from Domain, renamed machine to different name and re-joined
Used different IP addresses for the Physical host
Reloaded the HyperV server from scratch and created new VM.
Ive had HyperV previously running on this machine without problem, so now i cant see why i cant get it running again.
Anybody have any suggestions on what i can try next, im all out of ideas.

Hi Fulgent,
I am assuming that , the hyper-v server have two NICs , one for host and the other one was configured as an external switch for VMs .
If the VMs can not access the dhcp and local network , please try to delete the external switch then uninstall the Physical NIC in device manager and click " scan for hardware changes " to reload it.
Try to create external virtual switch for VMs again .
Any further information please feel free to let us know .
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

WRT54G2 V1 Fails to get WAN DHCP address

Similar Messages

Maybe you are looking for