Airport not getting IP address

So here's my problem.
I have a wireless linksys router that I've never had a problem with before until recently. My Mac connects to the network fine, but it says that my Airport does not have an IP address and that I can't get internet access through it. I have full bars and am connected to the network, but no internet. My roommate is connected via ethernet to the router with his PC and his works fine. Even when I connect mine via ethernet, I still have no internet connection.
I got on the phone with a Linksys technician who ran me through configuring the router, and after about an hour of trying he said that it wasn't a problem with the router but with my airport settings.
Please help! I know next to nothing about networking and I really need internet access for my work!
Macbook Pro 17" Mac OS X (10.4.8)

You may want to check the thread about not being able to connect to the internet. <http://discussions.apple.com/message.jspa?messageID=3615819#3615819> I am starting to get the idea that it my be effecting several differnent types of laptop and not just the iBook G4. I am cruising around and hearing similar stories of people having problems not being able to connect to the internet all of a sudden with their laptop, me being one of them. See if it doesn't sound similar.

Similar Messages

Guest users not getting IP address

I am setting up Cisco wireless along with ISE 1.3 for guest wireless. The client is going to use the self-registration portal for guest wireless users. I followed this Cisco doc to configure the self-registration portal:
http://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/118742-configure-ise-00.html
I tested this in my home lab and everything works fine. However, at the client users are not getting IP addresses from the DHCP server. This is the same DHCP server that is used for corporate wireless and if you connect that SSID, you get an IP address. I have looked what I configured at home and the client and everything looks the same. In the back of my mind, I feel something is missing, but I can't figure out what it is.
Edit: Not sure if this makes a difference or not, but they are using a Nexus 5K for their core switch and it hosts the SVI for this network.
Let me know what information you need and I will post it.
TIA,
Dan

Hello,
Some verifications below :
Did you verify if DHCP Proxy is enabled in wlc's wlan interface ? Case DHCP proxy is disabled, did you verify if the ip helper address is enabled in Nexus SVI ?
DHCP Scope is enabled in the DHCP Server or is enabled in the WLC ?
Verify if Trunk in the switch is enabled correctly passing all VLANs to WLANs ?
Verify if ACL to redirect configured in the WLC is allowing DHCP Server and DHCP Client to client receive IP Address and ports 8443 to Cisco ISE and DNS to resolve some address and get access to ISE Portal ?
The scenario is Local Switching or Central Switching ?
Regards

DHCP via Hyper-V VM, Server2012r2 Hyper-V host, clients not getting IP address

You have to authorize a dhcp server as Britv8 says. That's the only way it'll start dishing out leases. That's standard for Windows DHCP server in an AD Domain.
Also there's 0 reason to mention Hyper-V here. The whole point of virtualization is to do hardware level abstraction.

I recently encountered this. Setup:
Initial setup of the system was at a different location from its final destination, with different network equipment (switches) between the two. No teaming is involved, however.
Set up the system at its final destination, with DHCP via a Hyper-V VM (Server2012r2), Server2012r2 Hyper-V host, physical clients on the lan were not getting IP address.
The physical server box has a 4-port Intel Gigabit ethernet card.
I moved the setup (Hyper-V Virtual Switch manager) so that the interface for the DHCP server VM was isntead using one of two built-in Broadcom adapters.
While this topic seemed promising,
http://community.spiceworks.com/topic/251317-hyper-v-vm-not-leasing-ip-s-dhcp
unfortunately, "fiddling about" was not what I was looking for as possible solution.
My notes for the resolution:
Hyper-V system running...
This topic first appeared in the Spiceworks Community

Airport Extreem Not Getting IP Address

My Airport Extreem BaseStation is communicating with my cable modem and my computers, but is not getting an IP address and connecting to the internet. However, when I plug the ethernet cable straight up to my laptop the laptop gets on the internet. I have two laptops and neither one can get on the internet wirelessly through the Airport Extreem Basestation, but they can both connect when they are physically plugged into the cable modem. Help!!

By "first time user" I was referring to someone who had just taken their Airport Base Station out of the box and was trying to set it up for the very first time.
Perhaps you situation is very similar to Richard's. While in your case, power cycling the Base Station did eventually solve the problem, another solution that has worked for many people with a problematic Base Station after the Airport 4.2 upgrade is to do a hard reset and reconfiguration from scratch of the Base Station. Apparently this is also the solution recommended by Apple's own tech support people in response to a problem like this.

Cisco 891 not getting IP address with DHCP with latest IOS

Hi,
I have a few Cisco 891 routers that are configured as DHCP clients on the WAN interface.
For some reason when I boot the router with a late IOS, the router is not receiving an address.
It works just as expected with the older IOSes.
Any ideas of what changed?
This is how the interface is configured:
interface FastEthernet8
ip address dhcp
no ip redirects
no ip unreachables
no ip proxy-arp
duplex auto
speed auto
no cdp enable
This IOS does not work:
c890-universalk9-mz.154-3.M2.bin
While these do work:
c890-universalk9-mz.150-1.M7.bin
c890-universalk9-mz.151-2.T2.bin
c890-universalk9-mz.152-1.T1.bin
Doing a "show ip interface brief" shows that FastEthernet8 is unassigned with the affected IOS.
With the older IOSes there is an IP address.
I had to downgrade two routers due to this issue, and did not have plenty of time to troubleshoot.
Both of the routers are connected to DSL from the same ISP...
Anyone seen anything like this before?

Add another one to the list.
I have a MacBookPro3,1 that connects to WIFI no problem. It used to connect to ethernet when I originally bought it, however I've been using WIFI exclusively for the past 2 years.
Recently I had a need to connect via ethernet and it wouldn't work at home (apple airport router). I next tried connecting via ethernet at a friends house using a linksys WRT54G, no dice either. I have the computer in the lab today (University Network) and I get the same error. 3 different locations, 3 different routers, all same problem. It used to connect to home and university networks ethernet right away.
IP address assigned is 169.xxx.xxx.xxx - subnet - 255.255.0.0
no other info. It's showing up as connecting to the network, but unable to communicate with DHCP. It does work if I enter all of the information in manually.
At first I thought I had messed something up in networking preferences as I tend to play around with things alot. However I did a complete system format, and fresh install of OSX Lion and I still have the same problem, without any of my meddling around to confuse things.
What gives?

TC not getting IP address

Setup is as follows:
Virgin Media Super Hub - Connected to internet OK, set to DHCP
TC - Set to DHCP (to receive from Hub), Bridge mode
Up to 20:00 tonight has worked perfectly for months, all of a sudden no internet connection.
I have spent hours playing with settings and resetting the hub and TC but the problem seems to be that the TC cannot get an IP from the hub.
If I statically assign an IP to the TC I still cannot connect to the internet and all devices connecting through TC wifi will not get an IP and auto assign a 169.254.x.x address.
I can at anytime connect to Virgin Hub via wifi and network cable and get on the internet, but would like to go back to previous working order where Virgin provides one wifi and TC provides private wifi
Any ideas welcome!

For some time with a static IP the TC worked along with the router and all iOS and OSX devices were getting an IP. The they stopped getting them for a while and reverted to default 169.x.x.x addresses.
An hour or so later and everything was ok again.
This evening everything has stopped working once more through the TC. no changes in settings at all. just the usual devices connecting in the usual way.
Try doing this manually.. The bridge setup we are using is automatic.. but there is no need to use that.. any wireless router can be setup in wan bypass mode.. ie ignore the wan port, just use the TC as if it is a router.. but set a static IP and no dhcp.
It would help me to know the IP of the virgin hub.. what is it set to..
Just so I can give you specifics.
And also what OS and airport version you are running.. even if you run Mountain Lion I would suggest you use 5.6 airport utility.
The basics of this are simple.
Do a factory reset on the TC.
It will go back to router mode.. leave it in router mode.. makes no difference to us.
Set a static IP in the right range for the Virgin hub but avoid the dhcp range used by it. eg virgin hub is 192.168.1.1 make the TC 192.168.1.254 and turn off dhcp in the TC.
Then plug the LAN port of virgin hub to LAN port of the TC.. this is the wan bypass.
The TC will now exist in the network as a bridge device.. but controlled manually.
If it still fails.. then I suspect faulty hardware in the TC or some fault or issue by virgin hub or ISP.

Cisco ISE 1.2, Clients not getting IP address in closed mode

Hello, I am running closed mode on my switchports. I have an issue where some clients come in in the morning, try to login, and will not get network access. I see that this is because they do not get an IP address. I am using MAB for authentication currently. They appear to MAB correctly and get Authorized in ISE, but they do not get an IP. Therefore, they also do not get the DACL of permit ANY. It's like the port gets de-authenticated during the night. Usually when the machine is rebooted it will come up with an IP address. Here is my switchport config...
switchport access vlan 32
switchport mode access
switchport voice vlan 64
logging event link-status
authentication event fail action next-method
authentication event server dead action authorize vlan 32
authentication event server dead action authorize voice
authentication event server alive action reinitialize
authentication host-mode multi-auth
authentication order mab dot1x
authentication priority dot1x mab
authentication port-control auto
authentication periodic
authentication timer restart 600
authentication timer reauthenticate 7200
authentication violation restrict
mab
dot1x pae authenticator
dot1x timeout quiet-period 300
dot1x timeout tx-period 10
dot1x timeout ratelimit-period 300
dot1x timeout held-period 300
service-policy input QoS-Input-Policy
service-policy output QoS-Host-Port-Output-Policy
end

Thanks, here is the requested output of an Unauthorized client. I had to configure authentication open so they could still get access...
SJ5051IDF1#show authen sess int g2/20 d
Interface: GigabitEthernet2/20
MAC Address: d4be.d94f.ab92
IPv6 Address: Unknown
IPv4 Address: 10.42.32.109
User-Name: D4-BE-D9-4F-AB-92
Status: Unauthorized
Domain: DATA
Oper host mode: multi-auth
Oper control dir: both
Session timeout: N/A
Common Session ID: 0A2A000B000034E367D4B998
Acct Session ID: Unknown
Handle: 0x21000508
Current Policy: POLICY_Gi2/20
Local Policies:
Template: DEFAULT_LINKSEC_POLICY_SHOULD_SECURE (priority 150)
Security Policy: Should Secure
Security Status: Link Unsecure
Method status list:
Method State
mab Authc Success
SJ5051IDF1#
SJ5051IDF1#
SJ5051IDF1#show ip access int g2/20
SJ5051IDF1#
SJ5051IDF1#
SJ5051IDF1#show access-list int g2/20
^
% Invalid input detected at '^' marker.
SJ5051IDF1#show access-list ?
<1-2799> ACL number
WORD ACL name
ipc Show access-list config download info
rate-limit Show rate-limit access lists
| Output modifiers
<cr>
SJ5051IDF1#show access-list g2/20
SJ5051IDF1#
SJ5051IDF1#
SJ5051IDF1#

Advising record (ADV - HSBC form) in DME file could not get email address

Dear all,
I have problems with DME file that Advising record could not get email that is maintained in vendor master data.
Standard communication methods in vendor master data must be Emails.
We use exit module to get this email for below fields:
Email chnl se. flag
Email address
T-code DMEE -> Advising record
(Attributes tab: Mapping procedures is Exit module.
Source tab: value was entered for Exit function)
We test once and got the expected result: email shown on DME file, in advising record.
However, as I rechecked recently, we have no email shown (though Constant value 'ADV' shown).
The form is active by the way.
I do not know if I miss anything in configuration.
Please advise.
Thank you very much.
Rgds,
Linh

Hello Linh,
Did you manage to resolve this. I'm facing the same problem, not able to get the email address.
Can you please provide the function module you used.
Thanks,
Srini

AP not getting ip address assigned.

Hi all,
I have a problem with my AIR-AP1041N-E-K9, i do not seem to get an ip-address assigned after a reset to factory defaults.
I do see the AP with CDP:
Device-ID: ap
Advertisement version: 2
Platform: cisco AIR-AP1041N-E-K9
Capabilities: TransBridge IGMP
Interface: gi5, Port ID (outgoing port): GigabitEthernet0
Holdtime: 163
Version: Cisco IOS Software, C1040 Software (C1140-K9W7-M), Version 12.4(25d)JA1, RELEASE SOFTWARE (fc1)
Technical Support:
http://www.cisco.com/techsupport
Copyright
Duplex: full
Power drawn: 15000 milliwatts
SysObjectID: 0.0
Addresses:
unknown addres
So that should mean that layer 2 connectivity is fine.
I have the AP connected to a cisco SG300 switch,and assigned switchport trunk allowed vlan's: 1,3,4,8.
Can someone help me?
Regards,
Menno
Message was edited by: Menno Hogenbirk
I also noticed that when i connect to the AP via console-cable, i can see the AP boot up in the console session, but then i do not get a login prompt, but it seems like the AP is responding; if i shutdown the interconnecting link between the switch and the AP, i do see log messages appearing in the console-connection.
I have tried to debug on the Switch, but i need a password, so i can debug, which i do not have.,

Hi, thanks for your reply,
I'm should be getting my ip via DHCP(as i believed that this is the way that the AP searches for an ip, when it has no config yet). The DHCP-server is configured on a cisco 871 router that is connected to the switch, as i found no option to configure it on my switch, which is in layer 3 mode. The DHCP-pool is assigned to the vlan(native) 1 address-range(in this case 192.168.0.x/24). I also have configured a range for my workstations, and here i do get Ip-addresses assigned.
The AP does not connect to a Wireless controller. Also i have checked my inter-vlan routing on my switch, and i have connectivity to all vlans, so i believe my AP should have connectivity to the DHCP-server configured on the router.
Ping-test from switch shows no issues:
Swouter#ping 192.168.0.1
Pinging 192.168.0.1 with 18 bytes of data:
18 bytes from 192.168.0.1: icmp_seq=1. time=0 ms
18 bytes from 192.168.0.1: icmp_seq=2. time=0 ms
18 bytes from 192.168.0.1: icmp_seq=3. time=0 ms
18 bytes from 192.168.0.1: icmp_seq=4. time=0 ms
----192.168.0.1 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
Message was edited by: Menno Hogenbirk
Problem has been resolved.

Wifi clients not getting IP addresses

Hello Experts,
I have a Cisco 1140 AP, and using express setup I have cnofigured a IP address to it. This AP is connected to our public network and is configured with a public ip address. We want the guest users to connect to Wifi and gain access to Internet.
While the users connect to Wifi, I find their laptops getting IP address in series 169.x.x.x due to which they are unable to get to internet.
Can somebody guide to what all configuration required so that laptops would get ip address?
Thanks
Arvind

Hello George,
I do not have any DHCP server, I want the AP to allocate IP addresses to wifi clients.
Anshul,
Is there any way the AP distribute the IP addresses? I want to have the AP act as an DHCP server and allocate IP address of wifi clients.
If this is not possible in this AP model 1142N, any other Cisco AP model available, which can act as DHCP server?
My requirement basically is:
The AP should allocate IP in the range 192.168.x.x and I would connect the AP to the public network. The wifi clients should be able to get to Internet.
Please suggest any other model in Cisco which should meet my requirement.
Thanks
Arvind

Not getting IP address

My father's old iMac G3 slot loading system, running 10.2.3 experienced a power company power outage and restoration of power yesterday. It was connected to a DSL modem and all was working ok. Afterwards the DSL modem didn't work so the telco is sending a replacement. In the mean time I took the iMac home with me and cabled it to a router/DSL setup used by my iMac 24" and my wife's Gateway. The iMac boots up and spends a longish time in the Network startup phase and when done does not have an IP address from the DHCP server in the router. Other computers connected to this router get an IP address immediately so it's something in the iMac.
I can ping localhost (127.1.0.0) ok but cannot ping the router (192.168.1.1).
Is there anyway to test the iMac ethernet NIC to see if the power problem effected it?
Would doing an OS 10.2 reinstall be of any help? Any suggestions?

I seem to recall that Mac OS 10.2 had a problem with getting the DNS numbers.
What you need to do it is manually fill your numbers. You can still use dhcp and fill in the dns numbers.
BDAqua suggests in a post.
You can use OpenDNS for looking up web addresses.
Put these numbers in Network>TCP/IP>DNS Servers for a try...
208.67.222.222
208.67.220.220
https://www.opendns.com/homenetwork/start/device/apple-osx-tiger
(Please note that you do not need to a joint open DNS to use it.)
http://discussions.apple.com/message.jspa?messageID=5908432#5908432
Hear is the the full story.
Seems like you are not getting the DNS address or addresses.
apple > system preferences > network
Double click on network connection you are using.
Pick the TCP/IP tab.
Verify that you have a DNS Server. If you do not, look on your windows machine and see what the net address is. You can also pick using DHCF and still enter you DNS server address.
You can use
harddrive > applications > utilities > network utility
to diagnose the situation.
You can ping google.com. Result:
Ping has started ...
PING google.com (64.233.167.99): 56 data bytes
64 bytes from 64.233.167.99: icmp_seq=0 ttl=244 time=215.362 ms
64 bytes from 64.233.167.99: icmp_seq=1 ttl=244 time=279.597 ms
64 bytes from 64.233.167.99: icmp_seq=2 ttl=244 time=189.747 ms
64 bytes from 64.233.167.99: icmp_seq=3 ttl=244 time=250.657 ms
64 bytes from 64.233.167.99: icmp_seq=4 ttl=244 time=183.232 ms
64 bytes from 64.233.167.99: icmp_seq=5 ttl=244 time=243.753 ms
64 bytes from 64.233.167.99: icmp_seq=6 ttl=244 time=173.108 ms
64 bytes from 64.233.167.99: icmp_seq=7 ttl=244 time=230.239 ms
64 bytes from 64.233.167.99: icmp_seq=8 ttl=244 time=180.639 ms
64 bytes from 64.233.167.99: icmp_seq=9 ttl=244 time=232.177 ms
--- google.com ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 173.108/217.851/279.597/33.615 ms
If that does work, try pinging 64.233.167.99 Result:
Ping has started ...
PING 64.233.167.99 (64.233.167.99): 56 data bytes
64 bytes from 64.233.167.99: icmp_seq=0 ttl=244 time=189.655 ms
64 bytes from 64.233.167.99: icmp_seq=1 ttl=244 time=213.471 ms
64 bytes from 64.233.167.99: icmp_seq=2 ttl=244 time=257.873 ms
64 bytes from 64.233.167.99: icmp_seq=3 ttl=244 time=172.745 ms
64 bytes from 64.233.167.99: icmp_seq=4 ttl=244 time=226.723 ms
64 bytes from 64.233.167.99: icmp_seq=5 ttl=244 time=171.883 ms
64 bytes from 64.233.167.99: icmp_seq=6 ttl=244 time=260.308 ms
64 bytes from 64.233.167.99: icmp_seq=7 ttl=244 time=172.963 ms
64 bytes from 64.233.167.99: icmp_seq=8 ttl=244 time=198.840 ms
64 bytes from 64.233.167.99: icmp_seq=9 ttl=244 time=181.215 ms
--- 64.233.167.99 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 171.883/204.568/260.308/32.247 ms
If pinging 17.254.3.183 works but pinging apple.com doesn't. You have a bad DNS Server address.
BDAqua suggests in a post.
You can use OpenDNS for looking up web addresses.
Put these numbers in Network>TCP/IP>DNS Servers for a try...
208.67.222.222
208.67.220.220
https://www.opendns.com/homenetwork/start/device/apple-osx-tiger
(Please note that you do not need to a joint open DNS to use it.)
http://discussions.apple.com/message.jspa?messageID=5908432#5908432
Robert
=======================================================
I suggest that you try pinging Google.com.
Macintosh-HD -> Applications -> Utilities -> Terminal
mac $ ping -c4 google.com
PING google.com (64.233.187.99): 56 data bytes
64 bytes from 64.233.187.99: icmp_seq=0 ttl=245 time=177.617 ms
64 bytes from 64.233.187.99: icmp_seq=1 ttl=245 time=251.899 ms
64 bytes from 64.233.187.99: icmp_seq=2 ttl=245 time=169.291 ms
64 bytes from 64.233.187.99: icmp_seq=3 ttl=245 time=250.119 ms
--- google.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 169.291/212.232/251.899/38.894 ms
mac $ ping -c4 64.233.187.99
PING 64.233.187.99 (64.233.187.99): 56 data bytes
64 bytes from 64.233.187.99: icmp_seq=0 ttl=245 time=176.723 ms
64 bytes from 64.233.187.99: icmp_seq=1 ttl=245 time=247.889 ms
64 bytes from 64.233.187.99: icmp_seq=2 ttl=245 time=176.890 ms
64 bytes from 64.233.187.99: icmp_seq=3 ttl=245 time=244.623 ms
--- 64.233.187.99 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 176.723/211.531/247.889/34.744 ms
mac $
Analysis: If you cannot ping Goolge.com but you can ping 64.233.187.99, then you need to enter you dns address. For some reason Mac OS X sometimes doesn't set the dns. You can set it manually.
apple > system preferences > network
tcp/ip tab and enter address of dns servers
example 162.33.160.100
You will need to use a different number.
Robert
Robert

Cisco 3502I Not getting ip address

I just deployed 2 brand new 3502I access points. Ap's are connected to a PoE module on a 4507. Ap's are powering up. The 4507 is configured to hand out ip addresses to the ap's. When I run 'sh cdp nei det', I can see the ap's but they do not have an ip address assignment. Another weird thing is in the output of the command, each ap has two entries. One entry shows gigabit0 and the other gigabit0.1. I have never seen this before. I dont know if this in some way is why the ap's are not getting an ip address. I have 40 other 3502I from 2 yrs ago and no problem. The IOS of the new ap's is 15.2. Anyone have an idea to what may be happening? TIA

I will use the cisco 3750 PoE for further testing. It is close by my office and the cable run is under 200 ft. I used this same switch and port to configure the other 40 3502i ap's. Below is the output of the show power inline fa1/0/12:
H02_3750_PoE#sh power inline fa1/0/12
Interface Admin Oper       Power   Device              Class Max
                            (Watts)
Fa1/0/12 auto   on         15.4    AIR-CAP3502I-A-K9   3     15.4
Interface AdminPowerMax   AdminConsumption
             (Watts)           (Watts)
Fa1/0/12              15.4                 15.4
Here is the output of show power inline from a different 4507:
4507#sh power inline gi1/6
Available:953(w) Used:83(w) Remaining:870(w)
Interface Admin Oper            Power(Watts)     Device              Class
                            From PS    To Device
Gi1/6     auto   on         16.6       15.4       AIR-CAP3502I-A-K9   3
Interface AdminPowerMax   AdminConsumption
             (Watts)           (Watts)
Gi1/6                 30.0                 15.4

DHCP: Some clients not getting IP address

Recently setup a new DHCP server on Mac OS X Server 10.5.8 running on an Xserve. We migrated from a Linux server.
The Xserve was originally just a file server. So the only services currently running are: AFP, DHCP, NFS, and SMB. No additional software is running.
The DHCP server ran just fine for the first couple weeks. But then we found some computers just stopped getting IP addresses from the DHCP server. Some were new computers introduced to the network. Some were laptops that had left and come back. However, the DHCP server is definitely still giving out IP addresses and renewing them for most new and existing computers. There have been five computers that have not gotten IP addresses so far, and that had been the case both on the wireless and on a wired connection. Two were PC's, one running Windows 7 and one running Windows XP with Lenovo's ThinkVantage software. The other three were different models of MacBook Pros.
For those five computers, we managed to get them working in two ways. One, we can select to use DHCP with a manual address. When we do that, it manages to pick up all the other information from the DHCP server like DNS and gateway. The second thing we can do is configure the DHCP server to supply a static IP address by providing it with the MAC address of these machines. When we do that, the computers receive the IP address from the DHCP server.
So I guess you could say the problem I'm experiencing is for a few computers the DHCP server seems to only be able to provide static addresses, but not dynamic ones with a lease time.
I have logging set to the highest for the DHCP server. Below is the first thing I noticed that keeps showing up. Sometimes it shows a different MAC address than the one below. None of the afflicted computers have that MAC address, though. I have not seen any other errors in the logs for the DHCP server.
Jan 24 12:09:47 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:09:47 fileserver bootpd[73839]: service time 0.000304 seconds
Jan 24 12:09:50 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:09:50 fileserver bootpd[73839]: service time 0.000280 seconds
Jan 24 12:09:54 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:09:54 fileserver bootpd[73839]: service time 0.000264 seconds
Jan 24 12:10:03 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:10:03 fileserver bootpd[73839]: service time 0.000265 seconds
Jan 24 12:10:11 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:10:11 fileserver bootpd[73839]: service time 0.000283 seconds
Jan 24 12:10:19 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:10:19 fileserver bootpd[73839]: service time 0.000291 seconds
Jan 24 12:10:28 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:10:28 fileserver bootpd[73839]: service time 0.000324 seconds

Recently setup a new DHCP server on Mac OS X Server 10.5.8 running on an Xserve. We migrated from a Linux server.
The Xserve was originally just a file server. So the only services currently running are: AFP, DHCP, NFS, and SMB. No additional software is running.
The DHCP server ran just fine for the first couple weeks. But then we found some computers just stopped getting IP addresses from the DHCP server. Some were new computers introduced to the network. Some were laptops that had left and come back. However, the DHCP server is definitely still giving out IP addresses and renewing them for most new and existing computers. There have been five computers that have not gotten IP addresses so far, and that had been the case both on the wireless and on a wired connection. Two were PC's, one running Windows 7 and one running Windows XP with Lenovo's ThinkVantage software. The other three were different models of MacBook Pros.
For those five computers, we managed to get them working in two ways. One, we can select to use DHCP with a manual address. When we do that, it manages to pick up all the other information from the DHCP server like DNS and gateway. The second thing we can do is configure the DHCP server to supply a static IP address by providing it with the MAC address of these machines. When we do that, the computers receive the IP address from the DHCP server.
So I guess you could say the problem I'm experiencing is for a few computers the DHCP server seems to only be able to provide static addresses, but not dynamic ones with a lease time.
I have logging set to the highest for the DHCP server. Below is the first thing I noticed that keeps showing up. Sometimes it shows a different MAC address than the one below. None of the afflicted computers have that MAC address, though. I have not seen any other errors in the logs for the DHCP server.
Jan 24 12:09:47 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:09:47 fileserver bootpd[73839]: service time 0.000304 seconds
Jan 24 12:09:50 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:09:50 fileserver bootpd[73839]: service time 0.000280 seconds
Jan 24 12:09:54 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:09:54 fileserver bootpd[73839]: service time 0.000264 seconds
Jan 24 12:10:03 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:10:03 fileserver bootpd[73839]: service time 0.000265 seconds
Jan 24 12:10:11 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:10:11 fileserver bootpd[73839]: service time 0.000283 seconds
Jan 24 12:10:19 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:10:19 fileserver bootpd[73839]: service time 0.000291 seconds
Jan 24 12:10:28 fileserver bootpd[73839]: DHCP DISCOVER [en1]: 1,0:23:32:c1:31:c3
Jan 24 12:10:28 fileserver bootpd[73839]: service time 0.000324 seconds

Cisco Flex Connect and users can not get IP Address by WAN

Hello my name is Ivan
I have a wlc 5508 with license base to 50 aps, i use a deployment flex connect. I already registered all my access points, I use web authentication to authenticate users guest, and the service dhcp is in the central site.
My issue is the users in each remote site, can not get an ip address by dhcp from the central site, they can authenticate in the guest ssid, but any users can not get an ip.
The request is passing by the wan in this way
Central Site DHCP - Router WAN - Remote Site - Users with notebooks. I use flex connect central deployment (all the traffic consulting to the wlc) .
perhaps i should use local deploy? The wlc is in the central site.
Can you help me to resolving this issue please? , perhaps any advice?
Regards
Ivan.

Thanks Osita
If I configure Central Authentication and I configure central switching I need to create a dynamic interafce for each remote site and each dynamic interface associated with a different VLAN ID, because I can not associate a single interface dynamic to the same VLAN ID, but in my case the client remote in each remote site have the same network segment with the same VLAN ID with the same SSID for guests. My goal is to configure web authentication with the local DHCP server at each remote site, will this work?.Each remote site have its own server dhcp.
If I configure authentication central authentication with central switching with web authenticacion as I set in my scenario?
My issues are the interfaces dynamics, because I have the same network to the customer guest with the same ID VLan in each remote site
Regards

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.

Airport not getting IP address

Similar Messages

Maybe you are looking for