DHCP Server not giving out IP Address to APPLE iPhone

Hi, First off, I hope this is the correct forum....
A little background, I have a very nice 16GB 3G iPhone (from Apple of course). It has no problem connecting to my wireless access point (cisco 1240). I have an old windows server that I can turn on as a dhcp server and it gets an address back right away, however my mac server (10.5) will no give it an address and I do not understand why. Here is the log.....
Mar 16 19:06:37 macserver bootpd[37021]: server starting
Mar 16 19:06:37 macserver bootpd[37021]: server name macserver.schmittg.com
Mar 16 19:06:37 macserver bootpd[37021]: interface en0: ip 192.168.1.75 mask 255.255.255.0
Mar 16 19:06:37 macserver bootpd[37021]: interface en2: ip 10.211.55.2 mask 255.255.255.0
Mar 16 19:06:37 macserver bootpd[37021]: interface en3: ip 10.37.129.2 mask 255.255.255.0
Mar 16 19:06:49 macserver bootpd[37021]: DHCP DISCOVER [en0]: 1,0:21:e9:5:d3:de <iPhone-5>
Mar 16 19:06:49 macserver bootpd[37021]: service time 0.008083 seconds
Mar 16 19:08:11 macserver bootpd[37021]: DHCP DISCOVER [en0]: 1,0:21:e9:5:d3:de <iPhone-5>
Mar 16 19:08:11 macserver bootpd[37021]: service time 0.003807 seconds
Mar 16 19:08:12 macserver bootpd[37021]: DHCP DISCOVER [en0]: 1,0:21:e9:5:d3:de <iPhone-5>
Mar 16 19:08:12 macserver bootpd[37021]: service time 0.000683 seconds
Mar 16 19:08:13 macserver bootpd[37021]: DHCP REQUEST [en0]: 1,0:21:e9:5:d3:de <iPhone-5>
Mar 16 19:08:13 macserver bootpd[37021]: service time 0.001844 seconds
Mar 16 19:08:24 macserver bootpd[37021]: DHCP DISCOVER [en0]: 1,0:21:e9:5:d3:de <iPhone-5>
Mar 16 19:08:24 macserver bootpd[37021]: service time 0.000587 seconds
Mar 16 19:08:25 macserver bootpd[37021]: DHCP REQUEST [en0]: 1,0:21:e9:5:d3:de <iPhone-5>
Mar 16 19:08:25 macserver bootpd[37021]: service time 0.000409 seconds
Mar 16 19:08:27 macserver bootpd[37021]: DHCP DECLINE [en0]: 1,0:21:e9:5:d3:de
Mar 16 19:08:27 macserver bootpd[37021]: dhcpd: host 1,0:21:e9:5:d3:de declines IP 192.168.1.227 from server 192.168.1.1
Mar 16 19:08:27 macserver bootpd[37021]: service time 0.001994 seconds
What is wrong?
Thanks!

I am having a similar problem:
---------------- Client Request --------------------
op = BOOTREQUEST
htype = 1
flags = 0
hlen = 6
hops = 0
xid = 20714
secs = 27
ciaddr = 0.0.0.0
yiaddr = 0.0.0.0
siaddr = 0.0.0.0
giaddr = 0.0.0.0
chaddr = 0:4:13:2a:2f:ed
sname =
file =
options:
Options count is 9
dhcpmessagetype (uint8): REQUEST 0x3
maxdhcp_messagesize (uint16): 0x224
requestedipaddress (ip): 192.168.1.66
server_identifier (ip): 192.168.1.200
host_name (string): m3-0004132A2FED
parameterrequestlist (uint8_mult): {0x1, 0x3, 0x6, 0xf, 0x21, 0x42, 0xa0}
vendorclassidentifier (string): snom-m3-SIP/01.25//10-Mar-09 16:36
client_identifier (uint8_mult): {0x1, 0x0, 0x4, 0x13, 0x2a, 0x2f, 0xed}
end (none):
bootpd[3138]: DHCP REQUEST [en1]: 1,0:4:13:2a:2f:ed <m3-0004132A2FED>
SELECT
state=SELECT
Sending: DHCP ACK (size 300)
bootpd[3138]: replying to 192.168.1.66
=================== Server Reply =====================
op = BOOTREPLY
htype = 1
flags = 0
hlen = 6
hops = 0
xid = 20714
secs = 0
ciaddr = 0.0.0.0
yiaddr = 192.168.1.66
siaddr = 192.168.1.200
giaddr = 0.0.0.0
chaddr = 0:4:13:2a:2f:ed
sname = ryan-perrys-computer.local
file =
options:
Options count is 8
dhcpmessagetype (uint8): ACK 0x5
server_identifier (ip): 192.168.1.200
lease_time (uint32): 0xdec
subnet_mask (ip): 255.255.255.0
router (ip_mult): {192.168.1.1}
domainnameserver (ip_mult): {208.67.222.222, 208.67.220.220}
domain_name (string): wha
end (none):
bootpd[3138]: ACK sent <no hostname> 192.168.1.66 pktsize 300
bootpd[3138]: service time 0.001879 seconds
destination address 255.255.255.255
---------------- Client Request --------------------
op = BOOTREQUEST
htype = 1
flags = 0
hlen = 6
hops = 0
xid = 11587
secs = 27
ciaddr = 0.0.0.0
yiaddr = 0.0.0.0
siaddr = 0.0.0.0
giaddr = 0.0.0.0
chaddr = 0:4:13:2a:2f:ed
sname =
file =
options:
Options count is 4
dhcpmessagetype (uint8): DECLINE 0x4
server_identifier (ip): 192.168.1.200
requestedipaddress (ip): 192.168.1.66
end (none):
bootpd[3138]: DHCP DECLINE [en1]: 1,0:4:13:2a:2f:ed
bootpd[3138]: dhcpd: IP 192.168.1.66 declined by 1,0:4:13:2a:2f:ed
marking host 192.168.1.66 as declined
state=<none>
bootpd[3138]: service time 0.001143 seconds
destination address 255.255.255.255

Similar Messages

WRT310N - Wireless not giving out IP addresses - Any hope?

I have a WRT310N. For wired ethernet there is no problem whatsoever but when I try to connect wireless laptops, cameras, etc. I can only do it 2 out of 10 times.
I usually get a limited connectivity error. It seems like the unit isn't giving out IP addresses over wireless. After rebooting and/or resetting it will sometimes work for a bit. There seems to be quite a few posts that are like mine so I don't have a good feeling about there being a solution to this problem.
Is there?
So I can get some work done, this morning I pulled the WRT310N and put the old WRT54G back on because it works great.

Upgrade/reflash the firmware for your router, reset the router and reconfigure. This should solve your problem.

WRT54gr not giving out ip addresses

I have a WRT54GR that seems to stall after running a couple of days. After about 3 - 5 days of running my PC's can see the wireless network, connect to it, but will not be given an IP address. If I reset the WR54gR the PC or laptop get's an IP address just fine. Any thoughts?
It has the latest firmware and YES, I have re-applied the latest firmware to this router.

Hi , try a few changes in the wireless settings.....from a hardwired PC access your router using http://192.168.1.1 "admin" is the password.....slect the wireless section and select channel 11....save settings....then go to the advanced wireless settings and reduce the beacon interval to 50 and reduce the RTS and fragmentation threshold by 40 each..
re-connect to your wireless network and observe.

I don't understand the thing you call live bookmarks never used it, and most forums I have used notify VIA E-mail not giving out my E-mail address information when a reply has been made to the thread in question.

So how do I get notified of updates in this forum? As I said: I don't understand the thing you call LIVE BOOKMARKS I have never used them, and most forums I have used notify VIA E-mail not giving out my E-mail address, or other private information when a reply has been made to the thread in question, so how do I get notified of updates in this forum? I have seen no normal options for setting my viewing preferences used for this forum. Thank You.

Thanks for your reply via email/msg. He wrote:
If you are interested in the actual design data for the Xeon processor, go to the Intel site and the actual CPU part numbers are:
Xeon 4 core - E5.1620v2
Xeon 6 core - E5.1650v2
Xeon 8 core - E5.1680v2
Xeon 12 core - E5.2697v2
I read that the CPU is easy to swap out but am sure something goes wrong at a certain point - even if solderedon they make material to absorb the solder, making your work area VERY clean.
My Question now is this, get an 8 core, then replace with 2 3.7 QUAD CHIPS, what would happen?
I also noticed that the 8 core Mac Pro is 3.0 when in fact they do have a 3.4 8 core chip, so 2 =16? Or if correct, wouldn't you be able to replace a QUAD CHIP WITH THAT? I;M SURE THEY ARE UO TO SOMETHING AS 1) WE HAVE SEEN NO AUDIO FPU OR PERHAPS I SHOULD CHECK OUT PC MAKERS WINDOWS machines for Sisoft Sandra "B-E-N-C-H-M-A-R-K-S" -
SOMETHINGS UP AND AM SURE WE'LL ALL BE PLEASED, AS the mac pro was announced Last year, barely made the December mark, then pushed to January, then February and now April.
Would rather wait and have it done correct than released to early only to have it benchmarked in audio and found to be slower in a few areas- - - the logical part of my brain is wondering what else I would have to swap out as I am sure it would run, and fine for a while, then, poof....
PEACE===AM SURE APPLE WILL BLOW US AWAY - they have to figure out how to increase the power for 150 watts or make the GPU work which in regard to FPU, I thought was NVIDIA?

Can't get DHCP server to give out correct subnet IP's.

Hi all,
I recently added a VLAN to my SG500X switch. I have the devices communicating between the VLAN’s (using static IP’s).
I setup the new DHCP subnet on my Windows 2003 server but I can’t seem to get the DHCP server to hand out IP’s from the new subnet.
From what I understand, the Windows DHCP server is supposed to detect which VLAN the request is coming from and hand out the correct one. If I plug a laptop into one of the untagged switch ports for the new VLAN I get an IP address...but it's from the original/primary subnet.
Do I need to configure anything else on the switch? It seems to be handing out IP’s on the primary subnet/VLAN just fine. I just need it to hand the correct one.
Any suggestions are appreciated.
Thanks,
Dan

Everyone has provided you good info on what to look into so I will just try to give you some background info as this topic threw me for a loop back in the day when I was studying for my CCNA. It never was really explained how the dhcp server knew which scope to assign from. It works like this assuming the dhcp server is not inside the broadcast domain of the client.
1.Client with sends a DHCP request broadcast message
2.Access switch receives untagged frame from client with destination mac of FF:FF:FF:FF:FF:FF
3.Access switch encapsulates the packet into a frame that includes the vlan ID that was configured on the access port the client was connected to. Lets say vlan 10
4.Frame is forwarded out all interfaces in the same vlan or trunk interfaces except where it was received from
5.Your router receives the frame from the trunk port. You either have an SVI or subinterface configured on the L3switch/router that is listening for traffic from that vlan. That SVI/subinterface will have an IP address on it. lets say 10.0.0.1/24.
SVI
int vlan 10
ip address 10.0.0.1 255.255.255.0
ip helper-address 192.168.1.50
Router
int f0/0.10
encapsulation dot1q 10
ip address 10.0.0.1 255.255.255.0
ip helper-address 192.168.1.50
6.Here is were the ip helper comes into play. The router inserts the source IP of the SVI/subinterface for that vlan into the packet and sends it to the dhcp server. So 10.0.0.1 ->192.168.1.50
7.DHCP server receives and chooses the scope based on the source IP in the packet. so in my example the dhcp server will look through it's configured scope and would find one for the 10.0.0.0/24 network.
8. DHCP server sends the dhcp offer to the IP of the SVI/subinterface which then forwards it on to the client.

New Subnet not handing out IP Addresses

I have created a new subnet (10.168.64.x) on a Netware 6.5 server using DNS/DHCP Admin Tool.
The old subnet (10.168.60.x) is running out of IP addresses but still functioning properly. The new subnet (10.168.64.0) is showing in DNS/DHCP but not handing out addresses.
I have done all of the following-
-Bound an IP address to the Server in the range of the new subnet (10.168.64.1)
-Unloaded and Loaded DHCPSRVR
Still no luck - What are some other steps I can take to get this new Subnet to hand out IP's?
I loaded DHCPSRVR -d2 and got the following message - https://docs.google.com/document/d/1...it?usp=sharing
Any help is appreciated!

If you don't get any replies here, try the DNS/DHCP specialist forum
https://forums.novell.com/novell-pro...dent/dns-dhcp/

How get the RVS4000's DHCP server to assign another IP address other than its own as the default gateway to its DHCP clients?

Hi,
I have a RVS4000 router with DHCP enabled and in router mode.
The LAN is 192.168.2.x. The RVS4000 static IP address is 192.168.2.8
The router is not the RVS4000 and is at 192.168.2.1
The RVS4000 dhcp is assigning it's clients a default gateway of 192.168.2.8 instead of what I want 192.168.2.1.
How can I get the RVS4000's DHCP server to assign another IP address other than its own as the default gateway to its DHCP clients?
Thanks

Hi Gail, you cannot do this. The router, as the DHCP server will only assign a default gateway of what IP interface the DHCP server runs on. If you have the default IP, the gateway is 192.168.1.1. If you create a second vlan, by default it would be 192.168.2.1.
There are not configuration options for the built-in DHCP server. If you'd like to expand this functionality, you would need an external dhcp server.
-Tom
Please mark answered for helpful posts

AirPort Express DHCP Server for distribution of IP-addresses?

Does the AirPort Express have an DHCP server that distribute local IP-addresses like other Wi-FI router does? If so, how do I set it up in the AirPort Utillity?

+Seems I cant force it to only use a specific subset of the IP address range?+
That would be up to the Netcomm router to provide the IP addresses to be used. I'm not familiar with Netcom, but a router with the type of capability I was thinking of could be configured to provide a certain range of IP addresses to a given device based on the MAC address of the device.
The additional information that you just furnished indicates that you probably have a basic featured router designed for home network use that would not have this type of capability. In that case, the AirPort Express would not be able to be configured to Distribute a Range of IP Addresses. It would have to be configured as a "bridge" on the network and receive IP addresses from the main router.
Or, the AirPort Express might be able to distribute the IP addresses that you want if you configure it to Share a public IP address. The rub here is that you will have what is known as a Double NAT on your network. You'll have two devices handling DHCP on the network when there should only really be one. It may or may not function correctly as this is not a recommended configuration.
Message was edited by: Bob Timmons

I have tried to send photos through text messaging and it will not send. I thought my iPhone 3 was giving out so I got my iPhone 4 last night and still can't send photos through text message. What is the deal??

I have tried to send photos through text messaging and it will not send. I thought my iPhone 3 was giving out so I got my iPhone 4 last night and still can't send photos through text message. What is the deal??

Also MMS is supported on a carrier by carrier basis. While mostly every carrier does support ths feature make sure that your carrier allows this functionality.

AX does not hand out ip addresses in roaming mode

I am trying to set up roaming network in my house using a Airport Extreme as the main router and a ethernet connected (via Powerline HD) Airport Express on the second floor of my house. I followed the usual instructions to set up the Airport Express to create wireless network in bridge mode. The Express allows clients to connect and accepts the password but does not hand out ip addresses. so the roaming device (an ipad and an Air) end up with self-assigned addresses in the 169.*.*.* range.
How do I correct this?
option click on the Air wifi symbol shows that its corrected to the correct wifi base station
Airport Utility sees both the main Extreme base station and the Express second floor base station, and neither reports any problems.
Thanks.

I am trying to set up roaming network in my house using a Airport Extreme as the main router and a ethernet connected (via Powerline HD) Airport Express on the second floor of my house. I followed the usual instructions to set up the Airport Express to create wireless network in bridge mode. The Express allows clients to connect and accepts the password but does not hand out ip addresses.
Actually, with the AirPort Express in bridge mode, the AirPort Extreme would be the router "handing out" the IP addresses as they would just be "passing through" the Express in this configuration.
Let's double-check your roaming network configuration, just to be sure nothing was missed.
Roaming Network Setup
Ref: See page 42 of the Apple AirPort Networks guide.
Setup the AirPort connected to the Internet to "Share a public IP address." Internet > Internet Connection > Connection Sharing: Share a public IP address
Setup the remaining AirPorts, as bridges. Internet > Internet Connection > Connection Sharing: Off (Bridge Mode) For each AEBSn in the roaming network:
For each base station:
Connect to the same subnet of the Ethernet network.
Provide a unique Base Station Name.
The Network Name (SSID) should be identical.
If using security, use the same security type (WEP, WPA, etc.) and password. Note: It is highly recommended that you use WPA2 Personal for best bandwidth performance.
Make sure that the channel is set at least three channels apart from the next base station to prevent Wi-Fi interference.

Lion Server not handing out DHCP addresses to Snow Leopard client

I have been pulling my hair out over this.
Here is the layout
Lion Server running on the newest Mac Mini and doing mail, DNS, DHCP, Software update and has a valid, not self assigned, certificate
3 clients running Lion Desktop (2 iMACs and a MBP pro (all no more that a year old and all woth the current updates)
1 client running Snow Leopard Desktop (last years 13 inch MBA)
The 3 Lion clients can get dhcp fro mthe Lion server without any issue
The SL client cannot get a DHCP address from the Lion server
A tcpdump shows the DHCP request coming from the MAC address of the SL client but no response from the Lion Server and nothing showing a deny in the logs for the DHCP server or any other system/kernel logs. The Lion clients all show the request and reply for them. All 4 clients currently have a static assignment in DHCP but even if I remove them all and do auto-assign for everything or even each one individually, the SL client will not get an address both on the Wifi and Ethernet (I have the USB ethernet adapter).
I also have an Aiport Extreme and if I use that for the DHCP server then all clients get the addresses. I know the DHCP server in the extreme cannot be shut down but if you give the extreme a static address then assign dhcp on the extreme to only give out one address and that is the same one that is statically assigned then it "thinks" it is out of addresses and no longer tries to assign addresses
At first I thought there was a conflict between the extreme and the Lion server but as I mentioned above, tcpdump clearly shows the requests going right to the Lion server
I'm usually pretty good at this kind of thing but this one has me stumped. I'm thinking bug, anyone else run into this yet?

Ryan jones,
> Having trouble with our dhcp server handing out IP addresses through the
> Wireless Lan Controller.
Has it ever worked? Is the Wireless controller configured to forward DHCP
requests to your DHCP server?
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)
Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

New 2008 R2 DHCP server will not hand out IP addresses

We've recently migrated our Domain Controllers to 2008 R2, Virtual Machines. (DC3 & DC4).
DC2 is an older 2003 box, 32 bit, set for retirement. All former roles have been moved to DC3 & DC4, including FMSO roles, and the server (DC2) has been demoted. The only service that remains on DC2 is DHCP.
I've used NETSH to export / import the DHCP info to DC4. All reservations have transferred ( Printers) and the scope shows "active" on DC4 and authorized, and running, but whenever I shut DHCP down on DC2, DC4 doesn't start handing out
IP addresses to clients.
Even after rebooting a client multiple times, running ipconfig /release & /renew, it never finds the new DHCP server, nor does the server show any client information in the address leases. (other than reserves)
We have a Cisco ASDM deployed, but DHCP and DNS are both disabled on this device, so I'm not sure IP Helper would be an issue here.
Since both my new DC's are 2008R2, do I need to elevate active directory up to 2008 function before DHCP will work?

Hi,
Is the issue resolved? As suggested by
Wyatt Miller, you can check if it was caused by IP helper.
In addition, is the new server authorized?
Here is a migration guide for you:
Migration of DHCP Server from Windows Server 2003 to Windows Server 2008
http://blogs.technet.com/b/teamdhcp/archive/2009/02/18/migration-of-dhcp-server-from-windows-server-2003-to-windows-server-2008.aspx
Hope this helps.

DHCP server not reasigning IPs

Hello everyone,
We're having a big issue with our DHCP server (MAC OS X Server 10.6.4), because it runs out of IPs, because it's not reasigning the same IP to the same device.
The file /var/db/dhcp_leases show me the same MAC address and different IP, not freeing the anyone and thus, causing the server to stop giving IPs. We've currently managed to make a script to delete the leases db daily, but some days it's nt enough, any advise you could give us?
Some of the dchp_leases file:
ip_address=10.1.0.182
hw_address=1,0:26:bb:55:c4:e2
identifier=1,0:26:bb:55:c4:e2
lease=0x4cbda154
ip_address=10.1.0.181
hw_address=1,0:1b:63:b5:6a:de
identifier=1,0:1b:63:b5:6a:de
lease=0x4cbda0a3
name=MAC265
ip_address=10.1.0.180
hw_address=1,c4:2c:3:32:2d:23
identifier=1,c4:2c:3:32:2d:23
lease=0x4cbd9fe3
name=MAC265
ip_address=10.1.0.179
hw_address=1,c4:2c:3:32:2d:23
identifier=1,c4:2c:3:32:2d:23
lease=0x4cbd9f27
name=iPod
ip_address=10.1.0.178
hw_address=1,90:84:d:c4:72:2e
identifier=1,90:84:d:c4:72:2e
lease=0x4cbd9d08
Thanks in advance,
Message was edited by: gmestre

This looks more like a problem with network settings and not any hardware problem. Try to setup your LAN connection again. Recheck your network service provider settings (thru default access page 192.xxx.xxx.xxx, using wireless connection): check whether DHCP server is enabled.
If you are using mac address filter, add mac address of your LAN card to the allowed addresses in network settings in 192.xxx.xxx.xxx
3000 N100-0768DKU
XP Home 5.01.2600 SP2
Ubuntu 8.04(hardy)

WRE54g not handing out IP address to client systems

This is probably a silly question, but I'll ask it anyways.
We have a Linksys WRT54G ver6 running latest firmware revision 1.02.0 along with a WRE54G ver3 running firmware 3.01.01.
Both devices are configured to use WPA-PSK security, and I have reconfirmed that the key is the same on both devices.
The wireless router is connected to our existing wired network, and so the DHCP functionality of the router is disabled as we want wireless clients to get their IP address from our existing DHCP server on the wired network. This part works fine, wireless systems can connect to the wireless router and they are given an IP address from the range configured on our wired DHCP server.
The range expander has been configured with the same SSID, and security settings as the wireless router. Wireless clients can see the SSID being broadcast by the range expander and they are able to connect to it, but they are not given an IP address.
Is this because the range expander is expecting to receive the IP's from the DHCP server on the wireless router ( which is disabled ) and does not know anything about our existing wired DHCP server?
Thanks.

ok I knew this was going to be something silly.
I tried disabling the wireless security on both devices and this allowed wireless clients to receive an IP address from the Range expander ( verified by the MAC address of the Access point the wireless clients were connected to ).
So I rechecked the security settings again, the key was fine but the issue turned out to be that the wireless router was configured to use WPA2 while the range expander only seems to have support for WPA. Once I enabled WPA on the wireless router, the wireless clients were able to connect and receive their IP address via the Range expander.

Self-assigned IP (DHCP is not getting correct IP address)

I just moved and got my internet connection not long ago. When the installation people were there, they tested the internet connection by plugging the ethernet cable directly to my girlfriend's macbook (one of those new white macbooks). It worked pretty well. I set the router up then, and it worked fine.
The problem is: I can connect wirelessly to the LAN created by the router (and internet works), but if I try to plug the ethernet cable directly from the modem to my macbook, it will self-assign an IP address and I can't get a connection. This problem has never happened before, and it happens just at home (no matter how many times I try to reboot the modem). The funny thing about it is that it still works if I plug the ethernet cable directly to my girlfriend's macbook instead of mine.
Can anybody give me a suggestion? Just to make sure: my mac (as well as my girlfriend's) runs snow leopard.
Thanks in advance,
Davi

There's no common issue.
All a self-assigned IP address means is that DHCP did not assign you an IP address.
This can occur for a variety reasons, from the DHCP server only issuing one address per network (many DSL modems do this) to running out of addresses (many cable modems will issue up to five but no more, and many routers will not issue more than ten.)
The brute force fix attempt is, as mentioned above, to power off your Macs and other machines, power off the router, then power off the DSL or cable modem. Wait a minute, then power them up in reverse order (DSL/Cable modem, then a minute later the router, then a minute later your PCs/Macs.)

DHCP Server not giving out IP Address to APPLE iPhone

Similar Messages

Maybe you are looking for