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...??!?!!!

Similar Messages

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.

Failed to get DHCP response on interface "Marking interface dirty"

Dears
i have WLC 5508 showing the below Logs , which prevent the users from connecting to the SSIDs , also its disconnecting the associted users
DHCP Socket Task: Jul 11 09:54:08.992: %SIM-3-DHCP_SERVER_NO_REPLY: sim_interface.c:1039 Failed to get DHCP response on interface 'interface-02'. Marking interface dirty.
*mmListen: Jul 11 09:54:08.638: %MM-3-INVALID_PKT_RECVD: mm_listen.c:7671 Received an invalid packet from 10.21.1.25. Source member:0.0.0.0. source member unknown.
it shows 3 to 4 times durring 1 hour ,
any idea about the problem , and what exactly Dirty interface means ??

looks like you could be using interface group.
(WLC) >show interface group detailed
Interface marked with * indicates DHCP dirty interface.
whenever the existing interface goes dirty does the client tries the next available interface for dhcp.
The idea of Interface Groups is that you can have a WLAN utilize multiple interfaces/VLANs/Subnets/DHCP Pools, either for load balancing. At its heart it is purely round robin or based on hash generated using mac address(it depends on the wlc code), but should a client connect in on a certain interface and not be able to complete the DHCP process we mark it as dirty for 30 minutes. During those 30 minutes we basically remove that Interface from the Interface Group as it won't be selected for use.

Failed to get IP address for Local Host (2) , OPMNCTL: opmn start failed

HI,
Hi, I have installed on Oracle 10g on Redhat Enterprise Linux V.2.1 . I was able to start OEM without any issues. Recently I had changed the static IP address and I couldn't able to start OPMNCTL and getting the following error while starting opmnctl start. error message is as follows.
Failed to get IP address for local host(2).....
Failed to get IP address for local host(2).....
Failed to get IP address for local host(2).....
my current configuration in /etc/hosts file is as follows.
127.0.0.1 localhost.localdomain servername
After going through some of threads available in Oracle, I have added the static IP address in the /etc/hosts but still I am getting the same error.
my new hosts file is as follows.
127.0.0.1 localhost.localdomain servername
10.21.253.102 localhost.localdomain servername
I don't know why this is looking for localhost (2). I did not set up any local host (2) and I could not see anything in my network confiuration also.
could you please help me in this issue? I appreciate your help in this regard.
Thanks
venkat

Hi, i think that the application server part is looking for a /etc/hosts entry
in this format:
127.0.0.1 localhost
As i noticed, this is used for internal communication.
Try this entry as is, without a domain...

"failed to get MAC address for machine"

here is the jist of things.
installed leopard and have it pimped out to my personal specs. I like where everything is and how things are working. No issues. just so you know, i only use WIFI for internet, i share with the guys upstairs. In order to get wifi on my machine, i use a USB dongle. works great no issues with it ever, well until i physically broke it. No big deal. So i replaced it with another one, different drivers/chipset worked.. And since i installed leopard i only backed it up once with TM, i dont care for daily/hrly backups, weekly is fine for me. Now after 2 weeks and a new usb network card. TM gives me an error. i click on the little red i and it says "the backup volume could not be found" so googled and searched the forums not much help, so i tried and formated my ext drive repaired and click on TM again, same error. In the error log in console, right after i turn on TM i get this error, "failed to get MAC address for machine" then 180 secs later, TM fails. again, and again.
Can anyone tell me where i can find what MAC address its looking for??? ethernet has never been plugged in to my machine ever. its only been online via USB wifi. Im really lost here, i dont know what i can do.. im sure if i try another drive ill get the same error. please help if you can.. much appriciated.
Jamie

yeah i get a 'failed to get mac address' message too. what's weird is that it seems that leopard 'broke' my ethernet (there was no mac address, couldn't connect to the internet through ethernet after a clean install), and then 10.5.2 'fixed' it. for some reason, i have an 'ethernet 2' heading in system preferences that works correctly and has a mac address and everything, while the regular 'ethernet' tab doesn't work at all. however, i still get this time machine error. i don't understand why time machine is so incredibly fickle. sorry, i'm really of no help to anyone, other than adding another voice to the frustration.

BPEL process fails in SOA (in UNIX), but works fine in SOA (in Windows) env

Hello,
BPEL process fails in SOA (in UNIX), but works fine in SOA (in Windows) environment
Step 1: Build a asynchronous BPEL process which has no extra node. Make and deploy it in 'local windows desktop SOA' server
The BPEL process has three nodes:
a. client - on the left side of the swim lane
b. receiveInput - first node in swim lane (client calls 'receiveInput')
c. callbackClient - second and last node in the swim lane ('callbackClient' calls client)
Step 2: Go to BPEL console and 'Initiate' the BPEL process -> 'Post XML Message'
Step 3: Now, I can see the successfully completed BPEL instance in the BPEL console.
Now,
Step 4: Deploy the same BPEL process (dummy asynchronous) in the SOA server (hosted in unix box)
Step 5: Go to BPEL console and 'Initiate' the BPEL process -> 'Post XML Message'
Step 6: I find that the BPEL instance appears to have ended in error (on the second node i.e. callbackClient )
With the following error message
+<invalidVariables xmlns="http://schemas.oracle.com/bpel/extension"><part name="code"><code>9710</code>+
+</part><part name="summary"><summary>Invalid xml document.+
According to the xml schemas, the xml document is invalid. The reason is: Error::cvc-complex-type.2.4.b: The content of element 'DummyBPELProcessProcessResponse' is not complete. One of '{"http://xmlns.oracle.com/DummyBPELProcess":result}' is expected.
Please make sure that the xml document is valid against your schemas.
+</summary>+
+</part></invalidVariables>+
Has anyone faced similar issue as above ?
i.e. process works find in windows environment (local SOA), but fails in SOA server in UNIX environment
Appreciate your help in understanding this issue.
Thanks,
Santhosh

Hello,
The fix to this issue appears to have been as follows:
+<schema attributeFormDefault="unqualified"+
+     elementFormDefault="qualified"+
+     targetNamespace="http://xmlns.oracle.com/DummyBPELProcess"+
+     xmlns="http://www.w3.org/2001/XMLSchema">+
+     <element name="DummyBPELProcessProcessRequest">+
+          <complexType>+
+               <sequence>+
+                    <element name="input" type="string"/>+
+               </sequence>+
+          </complexType>+
+     </element>+
+     <element name="DummyBPELProcessProcessResponse">+
+          <complexType>+
+               <sequence>+
+                    <element name="*:result*" type="string"/>+
+               </sequence>+
+          </complexType>+
+     </element>+
+</schema>+
In DummyBPELProcess.xsd,
modifiying "result" to ":result" appears to have resolved the issue in SOA under unix environment.
If anyone can explain why "result" works in SOA under windows and ":result" works in SOA under unix environment, I would really appreciate your help.
Thanks,
Santhosh

Failed to get proc address for GetLogicalProcessor...

hi everyone whenever i try to open the skype after instalation it show me this error"Failed to get proc address for GetLogicalProcessorInformation (KERNEL32.dll."please help me to solve this problem.i will be very thankfull to you for this favour.thank you.

Hi, i think that the application server part is looking for a /etc/hosts entry
in this format:
127.0.0.1 localhost
As i noticed, this is used for internal communication.
Try this entry as is, without a domain...

DHCP fails to get IP address

I'm using dhcpcd to try to get a lease for an IP address, but each attempt is met with a "timed out" message. The DHCP server works for other Arch Linux installs on this network, and it works for the same laptop when using Windows. This install also fails when trying on other DHCP servers, not just on my home network. I'm not sure what it is now. I usually run iptables, but I stopped it thinking it might be the problem. I've also stopped networkmanager. I have a completely updated system, I ran pacman -Syu just now and rebooted.
I can manually set the IP address and it works fine, and I've tried dhclient instead of dhcpcd.
root@thinkpad ~# dhcpcd --release
dhcpcd[7377]: dhcpcd not running
root@thinkpad ~# dhcpcd -d eth0
dhcpcd[7378]: version 5.2.12 starting
dhcpcd[7378]: eth0: using hwaddr ....
dhcpcd[7378]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
dhcpcd[7378]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
dhcpcd[7378]: eth0: broadcasting for a lease
dhcpcd[7378]: eth0: sending DISCOVER (xid 0x485d8657), next in 4.24 seconds
dhcpcd[7378]: eth0: sending DISCOVER (xid 0x485d8657), next in 7.21 seconds
dhcpcd[7378]: eth0: sending DISCOVER (xid 0x485d8657), next in 15.01 seconds
dhcpcd[7378]: eth0: sending DISCOVER (xid 0x485d8657), next in 31.15 seconds
dhcpcd[7378]: timed out
# lspci -v | grep -A10 Ethernet
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
Subsystem: Lenovo Device 21ce
Flags: bus master, fast devsel, latency 0, IRQ 50
Memory at d5300000 (32-bit, non-prefetchable) [size=128K]
Memory at d532b000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 6040 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] PCI Advanced Features
Kernel driver in use: e1000e
Kernel modules: e1000e
and
# dmesg | grep e1000e
shows the link is up:
e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
This is my rc.conf with the comments removed:
LOCALE="en_US.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="localtime"
TIMEZONE="America/Indiana/Indianapolis"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
MODULES=(fuse nvidia thinkpad_acpi)
UDEV_TIMEOUT=30
USEDMRAID="no"
USEBTRFS="no"
USELVM="no"
HOSTNAME="thinkpad"
interface=eth0
address=
netmask=
broadcast=
gateway=
NETWORK_PERSIST="no"
DAEMONS=(!hwclock syslog-ng udev @slim network iptables dbus @bluetooth networkmanager @acpid !smbnetfs crond @alsa @cpufreq)
Last edited by fester (2011-12-09 22:48:47)

Mavrick, that did not fix it.
NgoHuy... dhcpcd -C eth0 did not solve the problem either.
I think dhcpcd is broken for wlan0 too...
root@thinkpad ~# dhcpcd -C eth0
dhcpcd[8439]: version 5.2.12 starting
dhcpcd[8439]: eth0: broadcasting for a lease
dhcpcd[8439]: wlan0: broadcasting for a lease
dhcpcd[8439]: timed out
dhcpcd[8439]: forked to background, child pid 8453
I also tried
dhcpcd eth0 -C /usr/lib/dhcpcd/dhcpcd-run-hooks
and that didn't work.
I removed dhcpcd:
root@thinkpad ~# pacman -Runs dhcpcd
and reinstalled it
root@thinkpad ~# pacman -S dhcpcd
and i still get the same problem
root@thinkpad ~# dhcpcd -d eth0
dhcpcd[8590]: version 5.2.12 starting
dhcpcd[8590]: eth0: using hwaddr .....
dhcpcd[8590]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
dhcpcd[8590]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
dhcpcd[8590]: eth0: broadcasting for a lease
dhcpcd[8590]: eth0: sending DISCOVER (xid 0x4b4b814b), next in 3.91 seconds
dhcpcd[8590]: eth0: sending DISCOVER (xid 0x4b4b814b), next in 8.73 seconds
dhcpcd[8590]: eth0: sending DISCOVER (xid 0x4b4b814b), next in 15.68 seconds
dhcpcd[8590]: eth0: sending DISCOVER (xid 0x4b4b814b), next in 32.46 seconds
dhcpcd[8590]: timed out
Last edited by fester (2011-12-08 13:03:41)

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.

Not getting DHCP address on HP 8000 Elite

I'm using the Feb 2010 CD. Windows 2003 DHCP server
Boot with the cd and no dhcp address.
If I type "dhcpcd eth0 -n" enough times I will eventually get an address, although the first time it's usually "err, eth0: Failed to lookup hostname via DNS: Name or service not known"
The same CD works OK with a HP dc7900, dc7800, etc. It looks like they all have the same Intel e1000e nic, but maybe no?

I'm starting to investigate issues that may be similar to yours and I had a
thought that I thought I'd share with you ;-)
In what may be a related situation one of our admins is having issues with
the dhcp client on an openSUSE 11.1 (and 11.2) during and after the install
on some Dell servers. Sometimes the dhcp client will not get an ip address.
After some poking he found that there are in fact two dhcp clients available
: dhcpcd (dhcp client daemon) and dhclient (package is called dhcp-client).
The default client in openSUSE - and presumably the Linux environment of
ZENworks Imaging - is dhcpcd v3.x. It seems that there are a number of
reports of this client being problematic. The maintainer of this client has
recently released v5.x which may resolve the issues with v3.x.
In our testing on openSUSE dhclient works much more reliably than dhcpcd,
where "more" is equal to 100%. None of this helps us of course, but it is
background info that leads up to my idea: is it possible to use the other
client, dhclient in the ZEN Linux environment? I don't know if this client
is even included in the ZEN Imaging Linux environment or not. If it isn't
then maybe it might be possible to modify the initrd/root/linux files to
include it. This would at least let you have another means of acquiring a
dhcp ip address. I'm sorry that I do not have the Linux skills to do more
than make a suggestion...
Cheers,
Ron
PS I have submitted an enhancement request via the openFATE website to have
the dhcp client daemon upgraded to v5.x. Maybe if you think it a good idea
you could login to the openFATE portal and vote it up!

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.

IOS device failed to get ip address on multiple wlan on the same anchor controller

Dear Experts:
in my implementation, we need 2 WLANs be served on the same anchor controller.
WLAN1: wep/40bit, integration with NAC/OOB on anchor controller for guest wlan service.
and guest account controlled by NACguest server.
WLAN2: wep/40bit, no layer3 secuirty for temporary using.
foreign controller: WiSM on v6.0.196.4 (also testing on 6.0.182.0)
anchor controller: WLC4402 on v6.0.196.4
on WLAN1:
Windows7 client get ip address correctly.
iOS (iPhone4 on 4.3.1/4.3.2, iPad2 on 4.3.1/4.3.2) can get ip address correctly on WLAN1.
WLAN2, iOS device cannot get ip address.
compare with debug message "debug clien mac" + "debug dhcp message enable"
on both foreign and anchor controller.
on foreign controller:
PM state has changed from: DHCP_REQD (7) Change state to RUN (20) last state RUN (20)
on anchor controller:
PM state always stay on: DHCP_REQD (7) Change state to DHCP_REQD (7) last state DHCP_REQD (7)
Enable/Disable DHCP Address Assignment Required is not work.
Enable/Disable DHCP proxy is not work.
Any hit this issue when get ip address failed in multiple WLANs on the same anchor controller?
In attachment log file,
DMZ.log: anchor controller on DMZ.
S3p1.log: WiSM on v6.0.182.0
S3p2.log: WiSM on v6.0.196.4
client mac: 00:1f:3b:05:33:c1, Windows7 Client
client mac: 58:55:ca:cf:d2:07, iPhone4 with 4.3.1,
WLAN1 subnet: 10.61.246.0/23
WLAN2 subnet: 10.61.248.0/23

Hi, Nicolas:
just checking the attachment for the run-config on foreign/anchor controller.
DMZ_run.config - anchor controller
s3p1_run.config - WiSM on v6.0.182.0
s3p2_run.config - WiSM on v6.0.196.4
at this moment, we have disable the wlan 10 on foreign controller, and wlan 2 on foreign controller.
Wilson...

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!!!

SPA525G Won't get DHCP Address

So I have a couple of brand new SPA525Gs right out of the box and we are having trouble with them on the network.
I've setup a sniffer capture to see what's happening and it looks like the phone sends out a dhcp request but never accepts the offer from the switch.
I then setup a static IP address on the same subnet and it will not respond to the ARP requests either.
If I connect it back to back with my laptop, however I can ping it and get to the web interface fine.
Other older 504 and 525 phones are all working fine on this same subnet and switch port.
The phones came with version 7.5.2a and we upgraded them to 7.5.5 still does the same thing.
Has anyone else seen this? Small business support didn't offer up much help.

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!!!

One at a time - 1st iPhone gets DHCP address, 2nd iPhone gets a 169

We have a windows 2003 server as a DHCP server, it gives out a proper address to the first iPhone connecting to the network over wireless but then any other iPhones just get the 169.x.x.x address (which I know is a self configured address).
If the 1st phone disconnects then the next phone will get on and the 1st phone can't get back on. Also tried using a router to do the dhcp and the same thing happens. It looks to be because the name of the device as far as the dhcp server is concerned is "iPhone" even though the names of the phones are different. Both phones are running the latest 2.2.1 software, I did have a look and can see a few issues with dhcp posted but all un-answered.

Yep, both phones have had network settings reset, server has been rebooted and latest firmware on router. Thanks for the article, it is what I would do if the phone couldn't get an IP at all, seems strange that they can both get an IP address no problem when the other phone isn't around.

AEX fails to get DHCP address, but works on DLink

Similar Messages

Maybe you are looking for