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!

Similar Messages

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.

Wireless 2504,user not getting dhcp ip address

Hi i have configured wlc 2504 .in that i have configured two interfaces.one is guest, 2nd is internal user,
the pblm when user try to connect with that contain ssid user not getting ip address,
i have connected only one link between core to wlc on port 1.for guest interface i used port 4.but no physical link.
Please help this

There are multiple ways how the clients can get their IP-address in a WLC deployment.
From the WLC-FAQ:
How does DHCP work with the WLC?
A. The WLC is designed to act as a DHCP relay agent to the external DHCP server and acts like a DHCP server to the client. This is the sequence of events that occurs:
Generally, WLAN is tied to an interface which is configured with a DHCP server.
When the WLC receives a DHCP request from the client on a WLAN, it relays the request to the DHCP server with its management IP address.
The WLC shows its Virtual IP address, which must be a non-routable address, usually configured as 1.1.1.1, as the DHCP server to the client.
The WLC forwards the DHCP reply from the DHCP server to the wireless client with its Virtual IP address.Note: You can also configure the WLC to act as a DHCP server. For more information on how to configure a WLC as a DHCP server, refer to the Configuring DHCP Scopes section of the document Cisco Wireless LAN Controller Configuration Guide Release 5.1.
If you want more in-depth information you should read "DHCP with the WLC":
http://www.cisco.com/en/US/partner/products/ps6366/products_tech_note09186a0080af5d13.shtml
Don't stop after you've improved your network! Improve the world by lending money to the working poor:
http://www.kiva.org/invitedby/karsteni

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

Clients not getting DHCP in VRF

Good morning -
We have devices in the global routing table (not in a VRF) getting DHCP addresses without issue. The SVI is configured as such:
interface Vlan2301
description BLUE
ip address 172.19.68.1 255.255.255.0
ip helper-address 10.4.16.222
interface Vlan2512
description RED
vrf forwarding RED
ip address 10.217.5.1 255.255.255.0
ip helper-address 10.4.16.222
Clients in BLUE are getting DHCP but clients in RED are not. If I statically assign an address I have connectivity and can reach the DHCP server (which is also DNS server; with a static IP in VLAN 2512 I can do name resolutions for example).
I am at a bit of a loss. Is there anything special I need to do for VRF IP HELPER-ADDRESS configuration? A capture on my firewall interface shows the DHCP server is trying to reply - it is like the helper-address is not forwarding the dhcp reply (or is not getting it)
11:11:52.915180 IP (tos 0x0, ttl 254, id 17478, offset 0, flags [none], proto UDP (17), length 337)
    10.217.5.1.67 > 10.4.16.222.67: BOOTP/DHCP, Request from xx, length 309, hops 1, xid 0xb53a220c, Flags [none]
          Gateway-IP 10.217.5.1
          Client-Ethernet-Address xx [|bootp]
11:11:52.918761 IP (tos 0x0, ttl 124, id 28096, offset 0, flags [none], proto UDP (17), length 344)
    10.4.16.222.67 > 10.217.5.1.67: BOOTP/DHCP, Reply, length 316, xid 0xb53a220c, Flags [none]
          Your-IP 10.217.5.12
          Server-IP 10.4.16.222
          Gateway-IP 10.217.5.1
          Client-Ethernet-Address xx [|bootp]
Any ideas?

Good morning -
I have a pair of 6513 in a VS40 (VSS quad sup) connected via L3 MEC to a VSS pair of 4500X. Active to Active and Standby to Standby connected in a L3 MEC port-channel that is also a vnet trunk:
(Core)
interface Port-channel5
description Distribution Uplink
no switchport
vnet trunk
ip dhcp snooping limit rate 100
ip address 172.20.68.1 255.255.255.252
ip ospf message-digest-key 1 md5 XXX
spanning-tree guard root
(4500 Distribution)
interface Port-channel1
description Core Uplink
vnet trunk
ip arp inspection trust
ip address 172.20.68.2 255.255.255.252
ip ospf message-digest-key 1 md5 XXX
The interfaces are all using LACP mode Active inside the channels
On the 4500 we have a global routing table and a vrf. Both have helper addresses pointing to the DHCP server which is extranet service behind the 6513 Core.
interface Vlan2301
description Global Routing Table
ip address 172.19.68.1 255.255.255.0
ip helper-address 10.4.16.222
interface Vlan2512
description VRF
vrf forwarding RED
ip address 10.217.5.1 255.255.255.0
ip helper-address 10.4.16.222
DHCP for the Global Routing Table subnet works. DHCP for the VRF does not.
What is interesting is if we shut down the link that is connected to the standby 4500 (Te2/1/1) DHCP starts to work for the VRF.
Using <debug ip dhcp server packet detail> at the 4500 here is what I am seeing.
When both links are up and DHCP is failing for the VRF:
Mar 10 20:02:02.419: DHCPD: BOOTREQUEST from 0100.1a6b.3a56.13 forwarded to 10.4.16.222.
Mar 10 20:02:10.473: DHCPD: Reload workspace interface Vlan2512 tableid 3.
Mar 10 20:02:10.473: DHCPD: tableid for 10.217.5.1 on Vlan2512 is 3
Mar 10 20:02:10.474: DHCPD: client's VPN is RED.
Mar 10 20:02:10.474: DHCPD: using received relay info.
When I shut the Te2/1/1 link down in the L3 MEC at the 4500 DHCP starts to work for the VRF RED:
Mar 10 20:04:41.354: DHCPD: BOOTREQUEST from 0100.1a6b.3a56.13 forwarded to 10.4.16.222.
Mar 10 20:04:41.369: DHCPD: Reload workspace interface Port-channel1.2002 tableid 3.
Mar 10 20:04:41.369: DHCPD: tableid for 172.20.68.2 on Port-channel1.2002 is 3
Mar 10 20:04:41.369: DHCPD: client's VPN is .
Mar 10 20:04:41.369: DHCPD: forwarding BOOTREPLY to client 001a.6b3a.5613.
Mar 10 20:04:41.369: DHCPD: no option 125
Mar 10 20:04:41.369: DHCPD: broadcasting BOOTREPLY to client 001a.6b3a.5613.
Mar 10 20:04:41.369: DHCPD: no option 125
Mar 10 20:04:44.808: DHCPD: Reload workspace interface Vlan2512 tableid 3.
Mar 10 20:04:44.808: DHCPD: tableid for 10.217.5.1 on Vlan2512 is 3
Mar 10 20:04:44.808: DHCPD: client's VPN is RED.
It is like there is a bug that is treating the L3 MEC as a L2 MEC when both links are present; or the VNET trunk is not being processed correctly.
Has anyone else used a L3 MEC with a VRF and a DHCP helper with success? Is this a bug?
03.05.01.E is the code we are running on the 4500X-32(SPF+)
This is also with TAC but I thought I would share with the community in case anyone else has a similar environment or if Cisco experts want to comment.

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

VWLC clients getting DHCP address from management VLAN

Hi,
We have a strange scenario whereby some wireless employees are obtaining addresses from the management VLAN.
Some details:
DHCP managed by MS DHCP 2008 R2 (in remote data centre)
Cisco vWLC AIR-CTVM-K9 running v7.6.110.0
AP's are a mix of 2602 and 3702 (46 and 2 of each respectively)
SSID's are employee, guest, and production devices (all mapped to their own interface with relevant VLAN tag as per normal)
AP's all in FlexConnect mode as per vWLC caveats
Some employees are receiving addresses in the wireless management VLAN. This network only has six DHCP addresses available as it is solely for AP's, WLC and HSRP gateway. Obviously this gets exhausted very quickly leaving us with a scenario where clients are not obtaining DHCP addresses.
I understand that with FlexConnect mode, it will assign IP's from the native VLAN. What I don't understand is why most clients receive addresses in the correct VLAN, but a handful do not, and then cannot get an address from DHCP. Obviously the ideal scenario would be to put the AP's into local mode but unless this has changed in a SW release then I don't believe it's possible...
My question is: How do I get ALL the employees to obtain addresses from their interface and not the management VLAN?
Thanks in advance.

Hi,
I think we need a closer look to your configurarion to eliminate some possibilities:
- What is the WLAN security you choose?
- What is the interface that is configured under the WLAN?
- Does your WLAN have local switching enabled?
- If your security is using RADIUS server, do you have AAA override enabled under the WLAN config?
- If your security is using RADIUS server, do you send any attributes to the users?
- You have eliminate that clients that got management vlan IPs are always on same AP or they can be on any AP.
HTH
Amjad

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?

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

Clients not getting DHCP from external server

Hi,
I have a 4402 (version 7.0.235) working with 10 units of 1121 APs connected to it. The WLC is not configured to work in LAG mode. Physical portt #1 is connected to the Main Switch (trunk). I have 3 WLAN mapped to 3 Different VLAN and Everything (security and internal, external DHCP) is working swell...
Now- I have connected Physical port #2 directly to an ADSL Router (giga port), Configured Port 2 as untaggedwith the proper IP details.
I have configured this interface to receive DHCP from the ADSL Router and for some reason, Clients are not getting addresses.
When I assign a Static address to my laptop I get internet access and all is nice. I tried configuring The WLC internal DHCP server (instead of the ADSL router) and that didn't help. It seems like a DHCP problem but I dont understand the source of the problem of think of the solution.
When turning off the proxy settings I noticed that it helped. Is there anything to do with that? The problem was that after a while the other WLANs starting causing DHCP issues as well.
What is supposed to be configured? Any Expert is the House?
I attached a crappy drawing..

Hi Scott,
Thanks for your answer.
So what you are basicly saying is that I have 2 choices: 1 - disable the Proxy option on the WLC and work with external DHCP servers (internal will not work when this is enabled). 2 - Enable the Proxy option and only work with the WLC internal DHCP.
I have installed many WLCs this way, having Different DHCP Servers (external and internal) for multiple WLANs.
What do you think may be different this time? The router that I am using isn't the most expencive but it is providing DHCP to other clients (wired client) with no problems.
Thanks!!!

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

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.

Not getting DHCP address on HP 8000 Elite

Similar Messages

Maybe you are looking for