Incorrect DHCP server address to wireless client

Guys,
I have deployed a centralized wireless architecture with 2 x wisms in each of our DCs. I just noticed the clients are receiving incorrect DHCP server address, please note there is no issue with connectivity, i just want to know why incorrect DHCP server address is handed out to the clients.
The DHCP server address received is apparently virtual interface address of the WiSM. i am running WiSM firmware 7.0.116.0
Any information is appreciated.
Cheers
AP

DHCP proxy is pretty usless in my mind. It was something that lingered from the old airespace days. In fact if you ask many cisco se's they will tell you they wished they didnt default to proxy. Also, if you ever use cisco ISE, you will need to disable proxy, becuase you will need to configure a helper pointing to the ISE box for DHCP finger printing.
Steve points out, if you use the WLC as a DHCP server it is a requirement to have it on. But we all agree here on CSC (Steve, Leo, Blake, myslef), that the DHCP server on a WLC is not robust and is problematic at times.

Similar Messages

DHCP Server Address Range

Hi there,
I was wondering if there was a way to change the built-in DHCP server address range from 192.168.1.x to, say, 192.168.0.x? For example, when you change the router IP from 192.168.1.1 to 192.168.0.1. I noticed that when you commit such a change, the DHCP range does not update accordingly. Any ideas?
Thank you,
Paul
Solved!
Go to Solution.

Your DHCP server range should update automatically to the 192.168.0.x subnet when you change your "Local IP address" to 192.168.0.1. Be sure to use a computer that is wired to your router when you do this. Also, be sure to click on "Save Settings", then wait (3 to 60 seconds) for the screen to refresh. You will likely be disconnected from the router when you do this. Do not worry about this. Power down the router and your computer.
Next, wait 30 seconds, then reboot router and computer. Your Local IP address and the DHCP server range should now have the same subnet.

I don't know much about computers can anyone walk me through this ? How Do I Change The Software Update Server Address On A Client ? what do I open and how do i put it in the right spot?

I don't know much about computers can anyone walk me through this ? How Do I Change The Software Update Server Address On A Client ? what do I open and how do i put it in the right spot?

The simplest method is to run a defaults command on the client Macs (easily pushed via Apple Remote Desktop):
defaults write com.apple.SoftwareUpdate CatalogURL 'HTTP_URL_FOR_CATALOG'
for a user. If you run it via sudo it will set it for whenever you use softwareupdate as root.
The HTTP_URL_FOR_CATALOG has been changed with Mac OS X 10.6. If you use MCX it will automatically pick the new catalog – however if doing it manually the following URLs need to be used for whichever client version is in question:
Mac OS X 10.4: http://mysus.example.com:8088/index.sucatalog
Mac OS X 10.5: http://mysus.example.com:8088/index-leopard.merged-1.sucatalog.sucatalog
Mac OS X 10.6: http://mysus.example.com:8088/index-leopard-snowleopard.merged-1.sucatalog
Mac OS X 10.7: http://mysus.example.com:8088/index-lion-snowleopard-leopard.merged-1.sucatalog
Mac OS X 10.8: index-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog
To double check this applied you can run the following command:
/usr/libexec/PlistBuddy -c Print /Library/Preferences/com.apple.SoftwareUpdate.plist
and /usr/libexec/PlistBuddy -c Print ~/Library/Preferences/com.apple.SoftwareUpdate.plist
to see what settings are for the computer and user appropriately.
If this is working correctly when running Software Update (GUI) you should see the server address appear in parenthesis in the title of the window.
MCX
Another alternative is to use Workgroup Manager to manage the preferences via MCX from your server. This can be done for users, or for computers if they are bound to your Open Directory.
If you are using 10.5 Server or newer: you can simply use the Software Update section under Preferences.
Manually:
Choose the accounts, computers, or groups to have the preference applied to.
Click on Preferences, and then the Details tab
Press the Add… button and navigate to /Library/Preferences/com.apple.SoftwareUpdate.plist
Press Edit…
Under Often, add a New Key and enter the name CatalogURL
Make sure the type is string and then enter your SUS URL (eg. http://mysus.example.com:8088/index.sucatalog or if using 10.6: http://mysus.examle.com:8088/ – see above from the defaults section)
Press Apply Now, then Done. Once users/computers have refreshed their MCX settings (usually the next login or restart) the new settings will take over.
If this is working correctly when running Software Update (GUI) you should see the server address appear in parenthesis in the title of the window.
In order to have a system-wide configuration one has to run the following:
sudo defaults write /Library/Preferences/com.apple.SoftwareUpdate CatalogURL "http://your.updates-server.lan:8088/index.sucatalog"
In order to correctly work both on Leopard and Snow Leopard the right command to issue is:
defaults write /Library/Preferences/com.apple.SoftwareUpdate CatalogURL "http://your.updates-server.lan:8088/index-leopard-snowleopard.merged-1.sucatalog"
Happily used and tested on my network
The DNS trick that Chealion points out is fantastic. I use it at our office, and every computer on our LAN will automatically pull the updates from the local repository at high speed without any configuration.
Create the swscan.apple.com DNS zone on your internal DNS server, and have it resolve via an A record to your Mac
Tags: automaticupdates mac clients macosx setting as default software update
Category: Serverfault
Share
0
0
Google +
0
0
0
5
You might also like:
Can I Update My Jb 4s To 6.1.2 Without Restore? Tue. Jan 21st, 2014
Iphone 4 Not Charging After Update To IOS6
IPad 2 Not Updating To IOS 5.1
How To Resolve The â€âunable To Install Updateâ€ Error For OTA IOS Updates?
What Is â€âSoftware Updateâ€ Doing When It Says â€âChecking For New Softwareâ€?
Advertisement
Comment
- See more at: http://www.eonlinegratis.com/2013/how-do-i-change-the-software-update-server-add ress-on-a-client-mac-to-use-my-own-server/#sthash.YhHp5zWk.dpuf

No contact with DHCP server when using VPN Client

Pretty weird problem I discovered recently.
We use the VPN Client to connect to a 1841 router. Everything works fine except for one small thing.
The client do not send out _any_ traffic if the destination is the ip-address of the DHCP-server the client got its original ip-address from.
This is verified by Wireshark. A ping on the client do not produce any ESP packets towards the VPN concentrator. No matter what traffic you try actually.
Discovered this when wanting to use Remote Desktop towards the Windows Server that is the local DHCP server and was not able to connect. Then tested ping and still no response. That made me look closer and found out that I could not communicate at all with the DHCP server.
As I said, pretty weird.
Anyone else have seen this? Anyone have a solution? Right now I use OpenVPN instead when I need to control that server.
- Roger

Hi and thanks for responding.
Nothing here apart from being unable to send any packets to the dhcp-server. No problem sending to any other system on the same subnet. The same happens when I connect my pc to another subnet that is served by another dhcp-server. Then I can not connect to _that_ dhcp-server. I can then of course connect to the previous dhcp-server.
I mean _no_ packets are generated out the client at all if the destination are your dhcp-server. No problem with the packet being blocked by a firewall or anything like that. Ping another system on the same subnet as the dhcp-server and the client happily generates ESP packets and sends them to the vpn-concentrator.
I do not know if it was clear enough in the first post so I am saying it here: the vpn-concentrator gives out the ip for the vpn connection. The dhcp-server I can not connect to is the server that gives the client its ip-address _before_ starting up the vpn client.
We use this vpn system so the IT personell will be able to connect to restricted resources from their laptops anywhere in the network, also when using wireless.
This was discovered when one admin wanted to connect from his laptop to a server that also happened to be the dhcp-server that had given his laptop his ip address before he used vpn.
Should be easy enough for anyone else to test. Just ping your dhcp-server after starting the vpn connection. No RFC 1918 addresses of course, there must be a route from your vpn-concentrator to your dhcp-server and at least icmp echo must be open through any firewall/acl.
The vpn version is 4.8.00.0440 on Windows XP configured to not allow local LAN access. I might test this with other versions/OS'es when I have the time.
Regards,
- Roger

DHCP only works for wireless clients on Time Capsule. How to fix?

Hi All,
I have a question concerning the DHCP server on my Time Capsule. I'm posting here because I think you network pros lurking in this forum probably have way more insightful advice than the n00bs in the Time Capsule forum
My DHCP server on the Time Capsule only works for clients connected wirelessly to that specific access point; clients plugged directly into the network via ethernet and through other APs do not receive a DHCP assignment from the Time Capsule.
How can I get the Time Capsule to serve DHCP addresses to EVERYONE on the network, not just clients connected via the Time Capsule?
Thanks,
Chris

I don't know that TC provides that. Switch the TC over to its bridged mode (also known as an Access Point or AP), and run a DHCP Server on Mac OS X Server (fodder for this forum) or a DHCP server on another available device. Less desirable though feasible (so long as the IP address pools are coordinated and non-overlapping with other pools or static addresses), run multiple DHCP servers.

Windows 2008 DHCP Server Address Range and Exclusion Range

Hi ,
I have a couple of Doubts regarding DHCp windows 2008 server
1) The DHCP server is given a static Ip in a network series eg(192.168.1.x) starting Ip is 192.168.1.1 to 192.168.1.254 ,
and if the range is from 192.168.1.10 to 1.250 ,
Should the DHCP server be not given an Ip in the DHCP range specified ?
ie the DHCP server static IP should not be in the 192.168.1.10-192.168.1.250 , ( I have given as 192.168.20.5)
Even though the Exclusion range can be specified , Just want to know if this is best practice.
2) And next setting up the range , should we give the entire network address as range ( eg 192.168.1.1 to 192.168.1.254) and set exclusion range
or take a particular series (eg 192.168.10-100)
Please advise
Thanks in Advance
Regards
Anand M

Your DHCP server range should update automatically to the 192.168.0.x subnet when you change your "Local IP address" to 192.168.0.1. Be sure to use a computer that is wired to your router when you do this. Also, be sure to click on "Save Settings", then wait (3 to 60 seconds) for the screen to refresh. You will likely be disconnected from the router when you do this. Do not worry about this. Power down the router and your computer.
Next, wait 30 seconds, then reboot router and computer. Your Local IP address and the DHCP server range should now have the same subnet.

Finding DHCP server address

Hi I've just bought a managed switch on ebay and trying to find its IP address. I can see in network settings it's giving me an IP via DHCP but trying in terminal with 'ipconfig getpacket en0' doesn't return anything. Does anyone have any suggestions? Cheers

This is fundamentally a Netgear-specific question, and not something that particularly involves OS X.
169.254.0.0/16 is in the self-assigned IP address range. You're not getting an address from the switch, which implies that the DHCP server isn't working right, that you're not on a vLAN where the DHCP server is working, or the DHCP server is disabled. Given that device is a managed switch, it's anybody's guess how the ports and vLANs and the DHCP server are configured.
If you've not already done so, get the manual for the switch and read through that; that'll give you some idea of the interface and capabilities and norms for the device.
Some of the few discussions on the hardware reset process are here, here and here in the Netgear forums, and particularly a blog post here, and it looks like there are registration-required Netgear forums for this series switch that might have additional discussions.
Based on those Netgear forum discussions, there are some bricked switches around, too.

Incorrect DHCP IP Addresses

Suddenly, I am having trouble getting DHCP to work with my network. When I have Using DHCP selected in the System Preferences, the addresses that it receives are incorrect. This happens to all of the computers on my network (wired and wireless). They receive an IP Address of 10.0.1.xx and a router address of 10.0.1.1 which will not allow any connections. Instead they should be receiving an IP Address of 192.168.2.xx, and a router address of 192.168.2.1. If I use Manual configuration, I can successfully connect.
Can anyone point me in a direction to find out why, and how to fix this problem?
Here is what I have connected to my Belkin 4 port Router and Netgear 4 port switch:
1. Wired
a. One G5 running OS 10.4.9
b. One G3 graphite iMac running OS 10.4.9
c. One G3 original iMac running OS 10.3.9
d. One G3 Blue and White running OS 10.3.9
e. One HP running Windows XP
f. One DSL modem.
2. Wireless
a. One Pismo G3 Powerbook running OS 10.4.9
Here is what I have done to troubleshoot:
a. Power cycled all equipment (many times since this has been going on for several months).
b. Replaced the router with a new one (I thought that maybe the router was the problem).
c. Installed the latest updates to all OS's.
d. Contacted Belkin Tech Help (they just told me that they never heard of such a problem).
G5 Mac OS X (10.4.9) Dual 2 GHz PPC G5, 1.5 GB DDR SDRAM, HDD 150 GB

When a machine makes a DHCP request, it sends a packet from IP address 0.0.0.0 to 255.255.255.255 on port 68. I receives a packet to its new IP address from the server on port 67. If twp reposonses come back, there is a protocol to decide which one to take. What's happening to you is that you are expecting the belkin to be the one whose response is chosen. Instead an Apple machine is anwering, and its response chosen over the belkin, if it indeed answers. You can tell its an Apple machine from the IP addresses.
The way to troubleshoot this is to run /Applications/Utilities/Terminal on one of the Macs and enter the following:
on 1a-d:
$sudo tcpdump -ien0 -e -X 'port 67 or 68'
on 2a:
$sudo tcpdump -ien1 -e -X 'port 67 or 68'
on each, enter control-c to terminate. Next, renew the DHCP lease on a trouble machine on the network you're troubleshooting. You will see link level line showing you the MAC addresses of the machines in the DHCP dialog, as well as their IP addresses. From here you can determine which machines are responding.
The simple answer is to get the Apple one to stop responding, and the Belkin to. I suspect there are two responders, and the Apple is winning the negotiation. If you can't get it to stop, We'll have to look deeper.
-Phil

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

Some wireless clients can't discover or connection to local wired systems

Hi,
I've just upgraded my home wireless from an NetComm NB5540 + modem to a LinkSys X3000.
Internet access works fine for all devices, but some wireless devices can't "see" my Win7 desktop system that's on a wired connections to the router.
I've tried three devices...
Galaxy Note phone (running ICS 4.0.4) can discover and connect to file shares on my desktop system without any problems.
Asus Transformer Prime tablet (running JellyBean 4.1.1) can see the router on the local network, but can't see my desktop. Even if I manually type in the IP address it can't connect to it
Likewise my old WinXP laptop can see the router but can't see or connect to any other devices.
Any suggestions welcome.
Hugh
ps. I tried connecting the NetComm router with just Wifi configured to one of the ethernet ports on the X3000, so I've got two Wifi networks running in parallel. If I connect to this second WiFi network with any of the above devices then they can all discover and connect to my desktop system on the wired connection to the X3000.

Just to test network connectivity, why don't you ping the wired client from the wireless devices that are not able access it? Do post your results so we can further analyze this scenario. By the way, when you cascaded another access point (using the NetComm router) to the X3000, was it via LAN- LAN? Was the X3000 still the DHCP server for the wireless clients?

DHCP Server Daemon for Aironet

Hi,
does Cisco Aironet acts as a DHCP server for the wireless client?
Thanks.

Nope...Cisco Access Points can't work as a DHCP server for the wireless clients..Tejal

WLC 7.0.230.0 - Incorrect DHCP addresses being allocated by internal DHCP server

Background:
Initially there were 3 SSIDs configured but all of them were assigned a single interface and this interface was configured with the controller management IP address as DHCP server so that the WLC could assign IP addresses to wireless clients, guns and printers etc.
Issue:
As part of PCI initiative, we decided to segment the traffic in multiple subnets based on type of wireless clients; so now there are 3 interfaces configured and each SSID is assigned a specific dynamic interface and each interface is configured to use the controller management IP address as DHCP server.
There are 3 scopes configured for each of the dynamic interfaces/SSIDs and DHCP proxy is enabled but wirelss clients are still being allocated IP addresses from the original DHCP scope that was associated with the dynamic interface originally assigned to all 3 SSIDs.
What am I missing here?
I verified the following:
1. Each SSID is assigned a different dynamic interface (Users, Voice and Handhelds)
2. Each dynamic interface is configured to use controllers management IP address as DHCP server
3. DHCP scopes configured with correct network information for each dynamic interface and enabled

As mentioned in my first post, I am using the management interface IP address of the controller as the DHCP server in the configuration of all the dynamic interfaces.
I have not configured the override DHCP option in the WLAN configuration becuase I have specified the internal DHCP address in the dynamic interface.
But I did check the AP group configuration and there I found that the SSID is not assigned to the correct dynamic interface even if the WLAN configuration is correct.
I will change the AP group configuration to correct this. Thanks!

Wireless clients cannot get ip address

I have 7 WLANs configured all work fine but the latest. The 7th WLAN I configured will not let clients get an IP address. I can plug a wire into the port with the same VLAN configured on the port and I get an IP address but wireless clients connected to an AP on that port cannot get an IP adddress. Any suggestions would be appreciated.

Hello,
where is the DHCP server configured?
- do all other 6 WLAN's work fine with the same DHCP server.
- do you have any H-REAP VLAN mapping , or AP groups configured?
they will override the WLAN-interface configuration.
Kind regards
Talal
=======
please rate answers that you find useful , and mark as answered - when it is :-) - so others can find it easily

Configure DHCP Server options for Internet Sharing?

Good morning, all.
I have a Sprint (Sierra 595U) AirCard internet connection, which I'm sharing over my AirPort (using OS X's built-in Internet Sharing) to several Windows clients in my office. I see that when Sharing is enabled, en1 takes on the address 10.0.2.1 by default, as well as the role of default gateway/router and DHCP server for the Windows clients.
My question is: Can I configure the IP addresses and DHCP options for Internet Sharing to another address/mask scheme?
Just like I changed my home wireless network away from the default 192.168.1.0/24 for security reasons, I'd like to do the same here.
Thanks and Regards,
BrooklynWalker

Some paranoia is good.
Yes, of course security paranoia can be cultured. like yogurt
I googled.
This might help:
http://www.aleph0.com/computing/macosx/dhcp-setup/
but from what I just read, changing away from the default net & mask might be putzy.Some other discussions for you:
http://www.macosxhints.com/article.php?story=20050331194834746
or you might see something here that helps.
Sorry not to be more specific. Hard to tell if you already googled for yourself.
I'll let someone smarter than I am take a look for you, here.

Wireless clients cannot get to internet

Hi All,
I'm fairly new to networking and have been trying to troubleshoot an issue with my home lab.
I have a Cisco 2800 router with 2 interfaces, gig0/0 that is the "external" interface and gets an IP via DHCP, and gig0/1 that is the internal interface with IP 10.10.10.1 and a DHCP pool of 10.10.10.100 - 10.10.10.254. A nat pool containing the external interface IP (192.168.1.110) exists.
Current configuration : 3229 bytes
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname Router
boot-start-marker
boot-end-marker
no aaa new-model
ip cef
no ip dhcp use vrf connected
ip dhcp excluded-address 10.10.10.1 10.10.10.99
ip dhcp pool dpool1
import all
network 10.10.10.0 255.255.255.0
dns-server 8.8.8.8 8.8.4.4
default-router 10.10.10.1
ip domain name home.local
ip name-server 8.8.8.8
ip name-server 8.8.4.4
multilink bundle-name authenticated
interface GigabitEthernet0/0
ip address dhcp
ip nat outside
ip virtual-reassembly
duplex auto
speed auto
interface GigabitEthernet0/1
ip address 10.10.10.1 255.255.255.0
ip nat inside
ip virtual-reassembly
duplex auto
speed auto
no mop enabled
interface FastEthernet0/3/0
shutdown
interface FastEthernet0/3/1
shutdown
interface FastEthernet0/3/2
shutdown
interface FastEthernet0/3/3
shutdown
interface Vlan1
no ip address
shutdown
ip http server
ip http authentication local
ip http secure-server
ip nat pool ovrld 192.168.1.110 192.168.1.110 prefix-length 30
ip nat inside source list 1 pool ovrld
access-list 1 permit 10.10.10.0 0.0.0.255
snmp-server community public RO
control-plane
scheduler allocate 20000 1000
end
Coming off the internal interface is a 3750, and attached to that 3750 is a 4400 Wireless Lan Controller.
I'm able to create a wireless network that uses the router for DHCP and clients can connect to this wireless network and obtain an IP from that DHCP pool. The wireless clients can ping the default gateway (10.10.10.1) as well as every other device on that network, including hard-wired devices on the 3750. The arp table on the router also shows the wireless clients.
However, only clients connected via ethernet can access the outside (internet), wireless clients, who appear to get the exact same network config, are unable to access the internet they can only access other devices on that 10.10.10.0 network.
So I'm confused as to why with what appears to be the proper default gateway (10.10.10.1) and a valid IP from the router, what could be broken so hard-wired clients can NAT to the outside while wireless clients can't? I can't find any setting on the WLC 4400 that would be restricting wireless clients from leaving the local network.
Any clarification on my issue/my understanding of the problem would be greatly appreciated. Cheers!

Hello smorrissey,
May I ask, how many end devices do you have connected to the switch? And if you tried to connect wireless clients simultaneously with wired devices?
Because from your config it seems you're using only dynamic NAT:
ip nat inside source list 1 pool ovrld // this command will translate IP picked by ACL 1 to address in pool named ovrld. Because you have only 1 address in this pool, only 1 inside device will be able to communicate with outside world (Internet) at a time.
I would suggest to add keyword "overload" at the end of this command (ip nat inside source list 1 pool ovrld overload) to enable PAT, which will allow multiple LAN devices to use 1 outside address at the same time thanks to port address translation.
Hope this will help.
Michal

Incorrect DHCP server address to wireless client

Similar Messages

Maybe you are looking for