Ignoring a DHCP-supplied hostname

Is it possible to ignore a DHCP-supplied hostname? I have my hostname set via the System Preferences->Sharing pane, and like it that way. When I connect to my network at work (which has a DHCP server configured to pass down hostnames), my hostname in my shell is the nasty VLAN info string configured by my network admins. I'd like it to remain my own, attractive hostname.
I know I can configure myself with a static IP, but I don't really see a need for that.
Is there anything like /etc/dhclient.conf on Linux systems? Can I somehow tell OS X to ignore the DHCP-supplied hostname, like I can tell dhclient systems?

That appears to be it. My /etc/hostconfig doesn't have a HOSTNAME entry, but I can add one.
I know it only changes for my local system. I'm on a laptop, so I tend not to run permanently active services. I'm part of the support staff, so I don't need inbound remote admin access.
Thanks for the feedback!

Similar Messages

Troubles with DHCP-supplied LDAP servers

Hello,
this feature does'nt work at all in my environment....
I've a openldap server (RFC 2307) and a couple of macs (newest leopard) which are working quite nice together for a while now.
It's a closed Network and want to get rid of the following commands, which I have to enter on each new mac:
sudo dsconfigldap -x -e -v -s -a ldap.mydomain.de -n "MYLDAP"
sudo dscl -q localhost -create /Search SearchPolicy dsAttrTypeStandard:CSPSearchPath
sudo dscl -q localhost -merge /Search CSPSearchPath /LDAPv3/ldap.mydomain.de
Instead i want to use the possibility to transmit the needed ldap-data using DHCP.
Therefore I've added the following lines to my dhcpd.conf-Server
option ldap-server code 95 = text;
option ldap-server “ldaps://ldap.mydomain.de:636/dc=mydomain,dc=de”;
Booting a mac I've got the following results:
bo-dhcp-228:~ sysadm$ ipconfig getpacket en1
op = BOOTREPLY
htype = 1
flags = 0
hlen = 6
hops = 0
xid = 276885973
secs = 0
ciaddr = 10.0.0.228
yiaddr = 10.0.0.228
siaddr = 10.0.0.78
giaddr = 0.0.0.0
chaddr = 0:1c:b3:b0:e2:d5
sname =
file =
options:
Options count is 9
dhcpmessagetype (uint8): ACK 0x5
server_identifier (ip): 10.0.0.78
lease_time (uint32): 0x5a0
subnet_mask (ip): 255.255.255.0
router (ip_mult): {10.0.0.1}
domainnameserver (ip_mult): {10.0.0.9}
domain_name (string): mydomain.de
ldap_url (string): ldaps://ldap.mydomain.de:636/dc=mydomain,dc=de
end (none):
So far so good.
But the ldap-server never got used.
dscl localhost list /LDAPv3 on the mac-client shows emtpy results, and
on the wire there is absolutely no traffic to ldap.mydomain.de.
In fact the mac-client completely
ignores the dhcp-provided settings. Of course I've enabled the
Setting "Add DHCP-supplied LDAP servers to automatic search policies" on
the client.
I've tried to trace the problem on the client-side by doing
sudo ipconfig setverbose 1
touch /Library/Preferences/DirectoryService/.DSLogAtStart
and looking into /Library/Logs/DirectoryService/DirectoryService.debug.log , /var/log/system.log
and /var/log/com.apple.IPConfiguration.bootp but there is no hint why the client is not using the published ldap-settings.
It must be some problem on the mac-side.
Can anybody give a hint howto solve this problem?
Thanks
Christian

I have not tried to set this up using the command line (as you described), but have in the past done it using "Server Manager" (on the server) and "Directory Access" on a Mac OS X 10.4.x client.
When I did this I found that Macs after booting would not show a list of network login acocunts (as they should have) and typically trying to login using 'other' would fail. Also typically after a minute or two (and several attempts) it usually did work. AppleCare's suggested workaround at the time was to not use DHCP to advertise the OpenDirectory but to instead manually define it on the clients (using Directory Access).
My belief as to why it did not work is that when a Mac boots, it enables its network interface, asks the DHCP server for an address (and the LDAP details) and then in theory should continue to boot and connect to the LDAP server. However I believe that the timing of these events is such that the Mac goes past the LDAP stage before it has finished the DHCP stage and as a result does not have the LDAP information in time. By manually defining the LDAP (OpenDirectory) server in Directory Access it is already known in advance and you avoid this problem.
I have seen nothing to suggest that Leopard is any different in this area (although my recollection is that Panther - Mac OS X 10.3) did not have this problem.
So I use a manually defined entry on all our computers, and I have incorporated this in to the standard disk image I use to build all the new computers.

AEBS associates client hostnames with DHCP-supplied IP addresses?

Hi,
I have 3 Mac's, a Windows and a Linux machine on my home network.
I'm looking at getting an Airport Extreme Base Station.
I understand it does DNS forwarding and caching out-of-the-box.
I'd love to know if the Airport Extreme when acting as a DHCP server for the network will associate the client host names with the IP addresses it dishes out.
In other words, if I name my iMac "slartibartfast" will the AEBS pick up on this, and allow me ping and ssh to slartibartfast by name from the other machines on the network?
Note that I'm not talking about Bonjour here - I'm talking about DNS names.
I believe on the Mac to give it a DNS host name I have to do
scutil --set HostName slartibartfast
Thanks,
Sarah

Unfortunately, Apple dropped a number of features and functions in the "upgrade" to AirPort Utility 6.x in Lion and Mountain Lion.
If you are still running Lion, download and install AirPort Utility 5.6 for Mac OS X Lion to get those features back. Just keep both AirPort Utility 5.6 and 6.1 on your Mac and use the one that you need.
If you are using Mountain Lion on your Mac, things get more complcated since Apple will not officially allow you install AirPort Utility 5.6 on that operating system.
The workaround is to use a utility like Pacifist to manually extract the application and then manually install it in the Utilities folder. It will run fine this way.
More details here:
http://www.macworld.com/article/1167965/mountain_lion_and_the_ancient_airport_ba se_station.html
Another workaround....if you have Time Machine backups.....is to back in time to locate AirPort Utility 5.6 and restore it to the desktop. Then drag it into the Utilities folder.

Solaris 10 zone configuration with sysidcfg and dhcp and hostname

Hi
Excuse me if I look like a n00b... it's probably because I'm a n00b.
I've been struggling in the dark for more than 2 days now and I'm wondering if I'm thinking about this all wrong...
I have stand-alone server where I need to run zones. I want to create zones and automagically configure them at boot (read: by running a script). So here's what I need...
A zone
starting from unconfigured state
whose hostname is not the same as the zone name
using corporate DHCP to get its IP address
with DNS config coming from the DHCP server
registering its address the DNS
with a preconfigured root password
(I don't own the corporate DHCP or DNS servers, I can't put my own DHCP or DNS servers on the network.)
I would lke to create the zone, throw some config at it, then boot the zone and walk away. I am using zones with exclusive-IP. I can construct the zones and manually configure them once they're started to have DHCP, my own name, registered IP address with DNS and everything else I have specified above. But I don't want to do it manually...
Sysidcfg seems to do some of what I want but not entirely.
In sysidcfg I can set the root_password, the primary interface using DHCP, DNS server. I can't set a hostname in sysidcfg AND use configure it for DHCP. So the hostname is not what I want it to be after the zone is started and ready to go. The DHCP server is providing the DNS configuration, Solaris does not seem to honour it, but i'll ignore that for the moment.
I have tried various combinations of using sysidcfg, /etc/nodename, /etc/hostname.+interface+ and /etc/dhcp.+interface+ but I can't find any combination that actually works.
I can write to the zonestorage/etc/nodename to set the nodename, that works. But it does not match the DHCP address, so I get prompted for a new name service because it can't find a DNS entry for the name.
I can write to the zonestorage/etc/hostname.+interface+ and /etc/dhcp.+interface+ (to get the system to register its name with the DNS server after getting its DHCP address) but then I get a system with no root password and no DNS configuration, even though they are set in the sysidcfg file.
I can write a script that gets part of the way using sysidcfg and /etc/... files, then boots the zone and then runs a bunch of voodoo via zlogin commands to fix all the stuff that couldn't be done 'properly', but that's not a 'boot and walk away' environment. I can write a script that uses sysidcfg and hacks around with other files in /etc (like nsswitch.conf, resolv.conf), but that just feels likes a dirty hack to fix something that wasn't done properly in the first place.
So where am I going wrong and how do I do it right (within the constraints defined)? Why can't I configure, boot and walk away?
Thanks

Thanks abrante
Thanks for your response!
I don't think the config is messed up after the installation. I think the installation is fine, it's just not what I want :-)
I'm trying to decouple the zonename from the system name and get DNS registrations working. After installation, a DHCP client can get its hostname from DNS but I'm trying to do it the other way around. I want the DHCP client specify its own hostname, get an address from the DHCP server and then register its hostname with DNS. If the system gets its name from DNS/DHCP then I have to configure those to provide the system name and I don't own the DHCP/DNS infrastructure. These zones are for a development/QA environment, so we create and reconfigure these frequently. Hence the need to specify the system name within the zone and register that name in the DNS.
I have tried fiddling with the PARAM_REQUEST_LIST but it does not seem to be working as I expect. :-$ Removing 12 did not help with setting the hostname from the system. DNS does not have a registered name for this system anyway, so even if it tried to get a name for this system, it would get nothing.
I also do want the DHCP to change the DNS server and domain name, but this does not happen even though my dhcpagent includes 6 and 15 in the PARAM_REQUEST_LIST. I still have to set them in the sysidcfg file because it is always ignored in Solaris (S10u8 with 10_Recommended 30-Jul-2010)
As stated, I know I can hack around with the system after it has booted. But I'm trying to configure the system before it starts and let it take care of itself and not have to touch it. Frankly I'm surprised that the sysidcfg does not allow you to set a hostname name when you are using DHCP, that the default DHCP configuration does not register the system name with the DNS server, and the DNS config from the DHCP response is ignored. Even a sys-unconfiged system requires DNS configuration during initial boot, when I know that the DHCP response contains DNS information.
FYI: Windows systems using DHCP work as expected in this respect by default, i.e. set system name, use DHCP --> system gets address from corporate DHCP, DNS settings are set from DHCP information, DNS registration is made for system name.
I'm working around this at the moment... I call my zone by the system name I want, I hardcode the DNS settings in the sysidcfg file and I create the hostname.+nic+ and dhcp.+nic+ files in the zone storage to get the system to register its name with DNS, them boot.
Edited by: cydonian on Aug 19, 2010 7:45 PM

Router reports garbage characters for Mac's DHCP client hostname

I've got a Linksys wifi router giving nice wireless access to my 17" powerbook (OSX 10.3.9). But when I look at the DHCP active IP table, this one (and another Mac I have on the network) both show up with garbage characters on the "client hostname" even though I have the "DHCP client Id" field filled in in the Network, TCP/IP system preference pane. How do I get the router to see my client's name?
Mike

Might help if you told us what the "garbage" was. It
might help indentify what it relates to because it's
highly unlikely to be truly random. It's more likely
to be based on the client's MAC address.
ok. It is, exactly: ¸#Ð„ª
In any case, DHCP client ID and hostname are not
related, so you might be out of luck depending on
what the Linksys is doing.
ah! Sorry - I thought that's what it wanted. So, where on my machine do I set the client hostname? Where does a router grab this info from? I've got a PC connected to this thing which does report its name correctly.
Thanks,
Mike

DHCP and hostname

Anyone know how I can acquire an IP via DHCP and have a hostname in my /etc/hosts file?
currently i get
192.168.100.101 unknown #added by DHCP
would like to have
192.168.100.101 pfw01 loghost
Before I switched to DHCP I had pfw01 in my hostname.le0 file but now it just doesnt see it anymore

check out this website...it should give you what you needhttp://sunblade100.wells.org.uk/cache/30.html

DHCP client hostname unknown

I have a SunBlade using Solaris 9 with the DHCP client. I am requesting the DHCP information from a w2k box that is sharing my DSL connection. I cannot seem to get the configuration to provide a hostname (always comes back "unknown"). Any suggestions?

Hi there,
Edit the file /etc/init.d/network and change the line that reads
"dhcp") hostname=`/sbin/dhcpinfo Hostname` ;;
to
# "dhcp") hostname=`/sbin/dhcpinfo Hostname` ;;
"dhcp") hostname=`/usr/bin/cat /etc/nodename` ;;
Then, edit the file /etc/init.d/inetsvc and change the line that reads
hostname=`/sbin/dhcpinfo Hostname`
to
# hostname=`/sbin/dhcpinfo Hostname`
hostname=`/usr/bin/cat /etc/nodename`
Save the files and reboot the system. The system's hostname will be the
entry in the file /etc/nodename.
Regards,
Chris

Windows 8.1 w/Update 1 ignores WPAD DHCP Option 252

Hi!
We try to roll out Windows 8.1 w/Update 1 and Internet Explorer 11 with the lastest updates installed. The clients are configured to autodetect proxy settings in IE with WPAD DHCP-Option 252. The clients are not allowed to query
WPAD in DNS.
No problems with Windows 7.
In NetMon I can see the DHCP Request with the following result
- WPAD: http://wpad.server.name/wpad.dat - Type 252
     OpCode: Web Proxy Auto Detection (WPAD), 252(0xFC)
     Length: 30 (0x1E)
     URL: http://wpad.server.name/wpad.dat
+ End:
But the Windows 8.1 client still tries to use name resolution
NbtNs:Query Request for WPAD   <0x00> Workstation Service
The same issues with WindowsToGo with Windows 8.1 w/Update 1.
Any ideas? We tried a lot with Troubleshooting Automatic Detection on
http://technet.microsoft.com/en-us/library/cc302643.aspx but nothing helps. Thanks!

Hi,
Have you checked those articles?
How to configure proxy server settings in Windows 8
Windows 8 – Supporting proxy services with Static Configurations,
Web Hosted PAC files and Domain Policy Configured Proxy
Insight WPAD proxy settings on IE
Please take a look to see if they could help here.
Best regards
Michael Shao
TechNet Community Support

Wrong hostname from DHCP

Hi,
I've been following a strange issue between Macs and Windows Server based DHCP for some time.
Mac's got their IP address via DHCP, just like Windows machines.
The compter name is set up in Sharing in System Preferences. Everything seems to be normal.
Now the fun starts:
When I open a Terminal window I see a completely different name on the command prompt. This probably causes Apple Remote Desktop not to see some clients when they are on, because they have wrong hostname. ARD complains the Mac are offline when I can walk to the Mac and plainly see it's switched on and connected to the network.
So, my theory is, the IP Mac get's was previously assigned to an laptop computer, which goes off the network and the DHCP-supplied IP address is released and next get's assigned to a Mac. Somehow the hostname used by the previous IP lease holder sticks to the IP address and get's slapped to the Mac. Strangely this hostname overrides the name assigned on System Preferences.
Has anyone else observed similar behavior?

Here's some of my journal:
Nov 01 12:01:41 localhost kernel: e1000e 0000:00:19.0: irq 40 for MSI/MSI-X
Nov 01 12:01:41 localhost kernel: e1000e 0000:00:19.0: irq 40 for MSI/MSI-X
Nov 01 12:01:41 localhost kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov 01 12:01:43 localhost kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: R
Nov 01 12:01:43 localhost kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Nov 01 12:01:43 localhost dhcpcd[243]: version 5.6.2 starting
Nov 01 12:01:43 localhost dhcpcd[243]: eth0: sending IPv6 Router Solicitation
Nov 01 12:01:43 localhost dhcpcd[243]: eth0: sendmsg: Cannot assign requested address
Nov 01 12:01:43 localhost dhcpcd[243]: eth0: broadcasting for a lease
....[non relevant services]...
Nov 01 12:01:46 localhost dhcpcd[243]: eth0: offered 192.168.10.120 from 192.168.10.1
Nov 01 12:01:46 localhost dhcpcd[243]: eth0: acknowledged 192.168.10.120 from 192.168.10.1
Nov 01 12:01:46 localhost dhcpcd[243]: eth0: checking for 192.168.10.120
Nov 01 12:01:47 localhost dhcpcd[243]: eth0: sending IPv6 Router Solicitation
Nov 01 12:01:50 localhost dhcpcd[243]: eth0: leased 192.168.10.120 for 14400 seconds
Nov 01 12:01:50 IC-1 dhcpcd[243]: forked to background, child pid 275
Nov 01 12:01:50 localhost netcfg-daemon[154]: :: ethernet-dhcp up [done]
Nov 01 12:01:50 localhost systemd[1]: Started Netcfg multi-profile daemon.
Nov 01 12:01:50 localhost systemd[1]: Starting Network.
Nov 01 12:01:50 localhost systemd[1]: Reached target Network.
See 5 lines from the bottom, the hostname briefly changes, then immediately changes back. IC-1 is the dns name assigned by dnsmasq.
I'm using netcfg.service. dhcpcd@ is disabled. I don't have ifplugd installed. There's no net-auto-wired service enabled.
I'm not sure what is calling dhcpcd in this log.
Maybe this should be in a different subforum...
Last edited by tladuke (2012-11-01 19:18:04)

[SOLVED] Hostname not showing in DHCP lease list

This is a brand new installation using the new systemd base.
Installed openbox as window manager and Network Manager.
What did I miss that the hostname of this computer (opus) is not showing up in the DHCP Leases list?
When I connect to the network using Network Manger(DHCP), hostname is not sent to the DHCP server (DNSmasq). It shows up as a "*":
DHCP leases
Hostname    IP-address    MAC-address    Lease expires
*    192.168.10.100    XX:XX:XX:XX:XX:XX Nov 28th, 19:34
*    192.168.10.59    XX:XX:XX:XX:XX:XX Nov 28th, 19:23
alarmpi    192.168.10.69    XX:XX:XX:XX:XX:XX Nov 28th, 16:56
RM696    192.168.10.97    XX:XX:XX:XX:XX:XX Nov 28th, 18:23
(I blanked out the MAC-addresses.)
The first entry is connecting through wireless. The second is wired.
At the command line:
hostname
opus
hostname -f
localhost.localdomain
/etc/hosts:
# /etc/hosts: static lookup table for host names
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost opus
::1 localhost.localdomain localhost opus
# End of file
What file do I need to change and how?
Updated:
1) I created a /etc/dhclient.conf file and added:
send host-name "opus";
request subnet-mask, broadcast-address, time-offset, routers,
domain-search, domain-name, domain-name-servers, host-name;
and rebooted.
This had no effect.
2) Just for kicks, I uninstalled Network Manager and installed Wicd.
This DID send the hostname and it displayed on the DHCP Leases List. But it also had the effect of turning off the WiFi radio.
I did try to turn it back on: Went to the BIOS, made sure it was on (it was). Read some posts about power savings and what to do (tried them, didn't work).
So I uninstalled Wicd, re-installed Network Manager and I am back to where I was.
Last edited by dastagg (2012-11-29 11:15:11)

Sorry, forgot to add this:
https://bbs.archlinux.org/viewtopic.php?id=152376
Follow the instructions on the bottom.

SAP NetWeaver 04s SP7 installation and DHCP server

Hi All,
I am installing SAP NetWeaver on a machine which I use at work. I am little scared whether this installation might harm my computer or the local corporate network. This machine is connected to the local network (uses DHCP) to get the IP address.
Are there any precautions which I need to take before I start practicing on this platform ?
I read this below point in the installation instructions...
=========================================================
If no DHCP server is available on your network (which dynamically determines the IP address) or your computer is not connected to any network, you need to install the virtual interface adapter MS Loopback Adapter. This is described in detail within the contents of the download package.
=========================================================
Now as my computer is using DHCP (unknown location), if I install SAP NetWeaver 04s SP7, do I need to disconnect my comp from the Network and then install the MS loopback adapter ? or Its ok to ignore the DHCP option as my comp is already using DHCP ?
Thanks and Best Regards
Ayub.

Hi Ayub,
U dont need to disconnect ur computer from network. Just install a microsoft loopback adapter and assign it a static ip, and assign that ip and hostname on windows\etc\hosts file. it will installs on loopback adapter and ur local network connection will be as it is.
hope it will help u.
Regards
Subhash

Problem with hostname Solaris 10

I am a complete newbie to Solaris. I purchased a Sun machine with 9 on and upgraded it to 10 without many problems apart from not geting the network to work.
On the install of 10 I was asked for domain name and hostname.
Following much differing and I would say incorrect advice on setting up network on 10 gathered from these pages I used the sys-unconfig to try to get the network to work each time with no problem.
Following advice to create 3 files dhcp.le0, hostname.le0 the last one I forget I rebooted. On reboot there were a number of problems and nothing loaded I removed the files rebooted and then did a sys-unconfig.
Eventually I got the network to work but I had lost the hostname even with placing it is hostname.hme0 and rebooting. I sys-unconfig a number of times but was not asked for the hostname as on previous occasions.
I then went for a total new fresh install but I was not asked for a hostname on trying to use sys-unconfig to install the hostname it somehow on reboot would not load the screen.
I am as typing this on another fresh install of 10 but I have not been asked to give the hostname or domain. This implies when the new install runs it will be as "unknown".
Can anyone point me in the right direction to getting a hostname now that I have cracked the network and Samba.
It appears in my very limited knowledge of Sun and Solaris that the hostname and domaon name are not part of a new software install but are read by the software from somewhere else otherwise why should it miss out on these two crutial pieces of information.
Your help would be much appreciated

Put the desired hostname in the /etc/nodename file, then edit the /etc/default/dhcpagent file and remove "12" from the PARAM_REQUEST_LIST which can be found in the bottom of the list.
The /etc/nodename controls the hostname of the machine, the dhcpagent file instructs your DHCP agent what information it should get from the DHCP server, 12 indicates that it should ask for a hostname, if no hostname is found it will use "unknown".
Personally i'm not much in favour of sys-unconfig, but ive also noticed that a lot of people here likes it..

Infinite Supply and ATP calculations

Hi,
We are using an Unconstrained plan which is ATP enabled.We have setup ATP rule where the Infinite Supply option is set as Cum Total Lead time. Now, we have Purchase Orders that are placed both within and beyond the Cum Total Lead Time. For example, let's say the Cum total LT is 30 days and we have 2 POs, one on the 15th day and the other on the 40th day. When we do our ATP, we are able to see the PO which is on the 15th day but the PO on the 40th day is not seen by ATP since it assumes that since our infinite supply option is 30 days, we can meet any order within 30 days and the system gives an ATP date of 30 days. The requirement here is for ATP to ignore the Infinite Supply option if there is a PO or Intransit available beyond the Cum Total LT and consider that for ATP calculations. So, in the example above, ATP should return a date of 40 days from now.
I have tried using both the options ATP/CTP Based on Planning Output and ATP/CTP Based on Collected data for the profile option INV:Capable to Promise, but it still ignores the POs beyond the Cum Total LT. Please help with your ideas if ATP can be made to look beyond the infinite supply option in the ATP rule.
Regards,
Abhijit

Hi Devesh,
Thanks for your input.
The only problem in having the highest lead time for buy items as the Infinite Supply is that if there's no On-hand, PO or In-transit available for a Demand, ATP will return a date of the highest lead time for all items that is assigned with that ATP rule in that Org. We have our lead times ranging from 10 days to 120 days. If we set the ITF as 120 days (user defined) and enter a sales order for the item which has a total LT of 10 days, ATP will give a date of 120 days if no supply is available. This will not be acceptable as we will be communicating 120 days to the customer whereas actually we can get that item from our supplier in 10 days.
Please correct me if my example is incorrect. Also suggest if we can bypass the scenario above with any other setup.
Regards,
Abhijit

Implement DHCP Option 60 in SPA100 series

Hello,
Is there any plan to implement DHCP Option 60(vendor class id) in SPA100 series devices in future FWs? CISCO SPA5xx series already has this option implemented.
Regards,
Josep.

I'm not sure what exact device you mean saying "SPA100 series devices" but in SPA112 and SPA122 it is implemented already. I'm using it for long time. See catched packet:
    0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
            Hostname Option 12, length 6: "SPA112"
            Vendor-Class Option 60, length 12: "CISCO SPA112"
Don't forget to mark thread as answered if it answers your question ...

ACS 4.2.1 - PEAP Machine Authentication - Hostname different from PC account name in AD

Hello!
I don't really know, whether this issue has been asked before.
I have to configure PEAP Authentication with ACS 4.2.1 for Windows against Active Directory.
ACS ist Member of AD Domain xyz.domainname. The PC account is located in an OU of xyz.domainname.
Hosts get via DHCP a hostname as dhcp.domainname. This also is the name the machine uses for AAA request.
User authentication works fine, because the user account also is hosted in xyz.domainname.
The host authentication fails, because dhcp.domainname is a DNS domain only but no Windows AD subdomain.
Does anybody knows a solution for this special constellation?
Is it possible to strip or rewrite the domain suffix in any way during the authentication process?

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
Hello Jean,
I am guessing that you are using 802.1x wireless.
This is a expected behaving because the AD force the computer to change his password every month and if the computer is not on the domain at that moment the computer won't take that change.
This is a Microsoft issue and unfortunately Cisco does not have any workaround for that.
Please see links below that explain this situation.
http://support.microsoft.com/kb/216393/en-us
http://support.microsoft.com/kb/904943
Hope this helps
Erdelgad
Cisco CSE

Ignoring a DHCP-supplied hostname

Similar Messages

Maybe you are looking for