WDS Server DHCP configuration

Hi,
we have installed WDS server on windows server 2012. Our DHCP is a CISCO 2911 Router. what do we need to configure on the WDS and DHCP server for the clients to have a PXE boot.
Thanks in advance

"If the local DHCP server is not a Microsoft DHCP server, we will have to manually configure the DHCP server to forward the request to the WDS server."
How will the clients ( laptops/desktops) do the PXE boot and pull the image from WDS server ?
"If you have any problem, please configure DHCP option 66 and 67." -- on which device do we need to configure this ?
Thanks

Similar Messages

WDS Server - PXE + Diffrent DHCP Scope + Diffrent Network

Dear All,
I have a WDS Server + DHCP on one server and OS Deployment is working properly.
but i have a different network with different DHCP Server + DHCP Scope and wanted to deploy the WDS images on that.
so please guide me how to do this..
Explanation : DHCP + WDS on 172.27.11.XX (OS Deployment working properly)
DHCP on 172.27.3.XX (Not Able to find PXE Server on this..) all ports are open and tried to add 66 and 67 port with WDS name or IP but did not work.. please help..
Thanks in advance
Dhiraj Gaikawd

Hi,
You should configure IP helper on your router to point to your DHCP and WDS server.
And make sure port 4011 on WDS is reachable accross router.
Hope this helps.

On which port number WDS server will listen & service when installing on server which is also DHCP server?

hi frineds
in documents we read when we install WDS on the server which is also DHCP server, we must select this check mark :
"do not listen on port 67"
it means we instruct the WDS service not to listen on port UDP 67 to avoid a port conflict between WDS server service and DHCP server service.
So now on which port number WDS server will listen & service ?
thanks in advance

Hi john.s2011,
If Windows Deployment Services and DHCP are running on the same physical computer, this means that the DHCP server is listening on port 67 and is responsible ensuring authorization.
The related KB:
How the PXE Server Works
http://technet.microsoft.com/en-us/library/cc732649(v=ws.10).aspx
The related thread:
DHCP is not responding for WDS
http://social.technet.microsoft.com/Forums/windowsserver/en-US/07f98ac7-cc6f-4385-ba21-2e85bb460c03/dhcp-is-not-responding-for-wds
I’m glad to be of help to you!
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.
hi Alex.
sorry for delay
thanks a lot
regards

WDS and DHCP Disabled

I have been unable to configure any AirPort Express, or AirPort Extreme, to function in WDS mode with DHCP disabled. I have an existing wired router running DHCP. After connecting one AX via Ethernet to the router, disabling DHCP on that AX and then adding one or two AXes to the wireless network via WDS, computers joining this network do not receive IP addresses. The hardware topology is that the existing wired router acts as the DHCP server through the Ethernet-connected AX, whereas other AXes are connected as WDS basestations. Macs can join the AirPort network but fail to get IP addresses from the DHCP server.
I suspect that in WDS mode, the AXes do not function in bridge mode, failing to pass on IP address requests from the wirelessly connected Macs.
Macs connecting wirelessly to a single AirPort Express set up with DHCP disabled, but WDS disabled also, have no difficulty receiving an IP address.
I frequently set up similar WiFi networks using Linksys WiFi access points without difficulty, but I've never been able to configure two or more AirPort Expresess to conect to an existing network via WDS unless DHCP is enabled.
MacBook Pro Mac OS X (10.4.8)

Hi Don
I am getting PXE-E53 : No Boot image received. I believe my problem is my Client is in different IP range (10.1.18.1-255) and both DHCP and WDS is in (10.20.1.1-255)
In my environment I cannot change the Router configurations to point to some specific server. Do I just need to specify the option 66, 67 in DHCP or there is more to it.
Please advise
Regards
Sid

SCCM 2012 R2 - No Response from WDS server

We upgraded our SCCM 2012 sp1 servers to R2 and have we are now receiving the following error on our remote PXE enabled DP;
Have performed the usual processes;
Removed the PXE enabled DP
Uninstalled the WDS service
Rebooted server
Deployed the PXE-DP from the site server (letting the site server also install WDS)
Checked the WDS service start OK
Distributed the Boot images to the PXE-DP
Checked the content status has succeeded
Checked that the PXE booting clients are looking at the correct server IP
Checked the smsdpprov.log:
[AC8][Wed 03/19/2014 15:04:50]:Registry key creation successfull
[AC8][Wed 03/19/2014 15:04:51]:CSMSDPInstProv::RegisterDPHealthMonTask: Schedule is '00011700001F2000'
[AC8][Wed 03/19/2014 15:04:51]:1998-01-01T00:00:00Z
[AC8][Wed 03/19/2014 15:04:54]:A DP health monitoring task has been registered successfully
[AC8][Wed 03/19/2014 15:04:54]:CSMSDPInstProv::EnableDPUsageStatsGathering entered
[AC8][Wed 03/19/2014 15:04:59]:Failed to enable IIS logging for DP usage task. Error code: 0x80041013
[AC8][Wed 03/19/2014 15:05:00]:CcmInstallPXE
[AC8][Wed 03/19/2014 15:05:00]:RegQueryValueExW failed for Software\Microsoft\SMS\DP, PxeInstalled
[AC8][Wed 03/19/2014 15:05:00]:RegReadDWord failed; 0x80070002
[AC8][Wed 03/19/2014 15:05:00]:Running: C:\SMS_DP$\sms\bin\vcredist_x64.exe /q /log "C:\SMS_DP$\sms\bin\vcredist.log"
[AC8][Wed 03/19/2014 15:05:00]:Waiting for the completion of: C:\SMS_DP$\sms\bin\vcredist_x64.exe /q /log "C:\SMS_DP$\sms\bin\vcredist.log"
[AC8][Wed 03/19/2014 15:05:10]:Run completed for: C:\SMS_DP$\sms\bin\vcredist_x64.exe /q /log "C:\SMS_DP$\sms\bin\vcredist.log"
[AC8][Wed 03/19/2014 15:05:10]:Created the DP mutex key for WDS.
[AC8][Wed 03/19/2014 15:05:10]:Finding Wimgapi.Dll
[AC8][Wed 03/19/2014 15:05:10]:MsiEnumRelatedProducts failed
[AC8][Wed 03/19/2014 15:05:10]:FindProduct failed; 0x80070103
[AC8][Wed 03/19/2014 15:05:10]:MsiEnumRelatedProducts failed
[AC8][Wed 03/19/2014 15:05:10]:FindProduct failed; 0x80070103
[AC8][Wed 03/19/2014 15:05:10]:Found C:\Windows\system32\wimgapi.dll
[AC8][Wed 03/19/2014 15:05:10]:Wimgapi.dll is already installed.
[AC8][Wed 03/19/2014 15:05:10]:Path to smsdp.dll is 'C:\SMS_DP$\sms\bin\smsdp.dll'
[AC8][Wed 03/19/2014 15:05:10]:PXE performance counters have been initialized
[AC8][Wed 03/19/2014 15:05:10]:Machine is running Windows Server. (NTVersion=0X601, ServicePack=1)
[AC8][Wed 03/19/2014 15:05:10]:WDS is INSTALLED
[AC8][Wed 03/19/2014 15:05:10]:WDS service is already installed.
[AC8][Wed 03/19/2014 15:05:10]:Machine is running Windows Server. (NTVersion=0X601, ServicePack=1)
[AC8][Wed 03/19/2014 15:05:10]:WDS is INSTALLED
[AC8][Wed 03/19/2014 15:05:10]:Machine is running Windows Server. (NTVersion=0X601, ServicePack=1)
[AC8][Wed 03/19/2014 15:05:10]:Setting TFTP config key as: System\CurrentControlSet\Services\WDSSERVER\Providers\WDSTFTP
[AC8][Wed 03/19/2014 15:05:10]:Configuring TFTP read filters
[AC8][Wed 03/19/2014 15:05:10]:SetupComplete is set to 0
[AC8][Wed 03/19/2014 15:05:10]:RegQueryValueExW failed for Software\Microsoft\Windows\CurrentVersion\Setup, REMINST
[AC8][Wed 03/19/2014 15:05:10]:RegReadDWord failed; 0x80070002
[AC8][Wed 03/19/2014 15:05:10]:REMINST not set in WDS
[AC8][Wed 03/19/2014 15:05:10]:WDS is NOT Configured
[AC8][Wed 03/19/2014 15:05:10]:Share (REMINST) does not exist. (NetNameNotFound) (0x00000906)
[AC8][Wed 03/19/2014 15:05:10]:GetFileSharePath failed; 0x80070906
[AC8][Wed 03/19/2014 15:05:10]:REMINST share does not exist. Need to create it.
[AC8][Wed 03/19/2014 15:05:10]:Enumerating drives A through Z for the NTFS drive with the most free space.
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: A:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: B:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: C:\
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: D:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: E:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: F:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: G:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: H:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: I:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: J:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: K:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: L:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: M:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: N:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: O:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: P:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: Q:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: R:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: S:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: T:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: U:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: V:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: W:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: X:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: Y:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Checking Drive: Z:\
[AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
[AC8][Wed 03/19/2014 15:05:10]:Drive 'C:\' is the best drive for the SMS installation directory.
[AC8][Wed 03/19/2014 15:05:10]:Creating REMINST share to point to: C:\RemoteInstall
[AC8][Wed 03/19/2014 15:05:10]:Succesfully created share REMINST
[AC8][Wed 03/19/2014 15:05:10]:Removing existing PXE related directories
[AC8][Wed 03/19/2014 15:05:10]:Registering WDS provider: SourceDir: C:\SMS_DP$\sms\bin
[AC8][Wed 03/19/2014 15:05:10]:Registering WDS provider: ProviderPath: C:\SMS_DP$\sms\bin\smspxe.dll
[AC8][Wed 03/19/2014 15:05:10]:DoPxeProviderRegister
[AC8][Wed 03/19/2014 15:05:10]:PxeLoadWdsPxe
[AC8][Wed 03/19/2014 15:05:10]:Loading wdspxe.dll from C:\Windows\system32\wdspxe.dll
[AC8][Wed 03/19/2014 15:05:10]:wdspxe.dll is loaded
[AC8][Wed 03/19/2014 15:05:10]:PxeProviderRegister has suceeded (0x00000000)
[AC8][Wed 03/19/2014 15:05:10]:Disabling WDS/RIS functionality
[AC8][Wed 03/19/2014 15:05:10]:PxeProviderUnRegister
[AC8][Wed 03/19/2014 15:05:10]:
[AC8][Wed 03/19/2014 15:05:10]:Found privilege otifyPrivilege on service WDSServer
[AC8][Wed 03/19/2014 15:05:10]:Found privilege SeRestorePrivilege on service WDSServer
[AC8][Wed 03/19/2014 15:05:10]:Found privilege SeBackupPrivilege on service WDSServer
[AC8][Wed 03/19/2014 15:05:10]:Found privilege SeSecurityPrivilege on service WDSServer
[AC8][Wed 03/19/2014 15:05:10]:Privilege SeTakeOwnershipPrivilege NOT found service WDSServer
[AC8][Wed 03/19/2014 15:05:11]:ChangeServiceConfig2 succeeded for WDSServer. Added privilege SeTakeOwnershipPrivilege
[AC8][Wed 03/19/2014 15:05:11]:ChangeServiceConfig succeeded for WDSServer. StartType: 0x2
[AC8][Wed 03/19/2014 15:05:24]:WDSServer status is 4
[AC8][Wed 03/19/2014 15:05:24]:WDSServer is STARTED
[AC8][Wed 03/19/2014 15:05:24]:Running: WDSUTIL.exe /Initialize-Server /REMINST:"C:\RemoteInstall"
[AC8][Wed 03/19/2014 15:05:25]:Waiting for the completion of: WDSUTIL.exe /Initialize-Server /REMINST:"C:\RemoteInstall"
[AC8][Wed 03/19/2014 15:05:27]:Run completed for: WDSUTIL.exe /Initialize-Server /REMINST:"C:\RemoteInstall"
[AC8][Wed 03/19/2014 15:05:27]:Machine is running Windows Server. (NTVersion=0X601, ServicePack=1)
[AC8][Wed 03/19/2014 15:05:27]:No need to configure the firewall
[AC8][Wed 03/19/2014 15:05:27]:CContentDefinition::GetAllPackagesFromLib failed; 0x80070003
[AC8][Wed 03/19/2014 15:05:27]:ProcessBootImages failed; 0x80070003
[AC8][Wed 03/19/2014 15:05:27]:CcmInstallPXE: Deleting the DP mutex key for WDS.
[AC8][Wed 03/19/2014 15:05:27]:Installed PXE
[AC8][Wed 03/19/2014 15:05:27]:Registry key creation successfull
[D48][Wed 03/19/2014 15:08:12]:Registry key creation successfull
[D48][Wed 03/19/2014 15:08:13]:Registry key creation successfull
[D48][Wed 03/19/2014 15:08:13]:Registry key creation successfull
[D48][Wed 03/19/2014 15:08:14]:Registry key creation successfull
[F20][Wed 03/19/2014 15:08:26]:CcmInstallPXE
[F20][Wed 03/19/2014 15:08:26]:PXE provider is already installed.
[F20][Wed 03/19/2014 15:08:26]:Installed PXE
[F20][Wed 03/19/2014 15:08:26]:CSMSDPInstProv::EnableDPUsageStatsGathering entered
[F20][Wed 03/19/2014 15:08:26]:1998-01-01T00:00:00
[F20][Wed 03/19/2014 15:08:27]:A DP usage gathering task has been registered successfully
[BB8][Wed 03/19/2014 15:10:59]:Content 'ASC0000E.8' for package 'ASC0000E' has been added to content library successfully
[BB8][Wed 03/19/2014 15:10:59]:Expanding C:\SCCMContentLib\FileLib\24E7\24E71E7B8DBA522A60756D1C2329EE616A364DAB121FFB7A7117D30D4F77A0EC from package ASC0000E
[BB8][Wed 03/19/2014 15:10:59]:Finding Wimgapi.Dll
[BB8][Wed 03/19/2014 15:10:59]:MsiEnumRelatedProducts failed
[BB8][Wed 03/19/2014 15:10:59]:FindProduct failed; 0x80070103
[BB8][Wed 03/19/2014 15:10:59]:MsiEnumRelatedProducts failed
[BB8][Wed 03/19/2014 15:10:59]:FindProduct failed; 0x80070103
[BB8][Wed 03/19/2014 15:10:59]:Found C:\Windows\system32\wimgapi.dll
[F20][Wed 03/19/2014 15:10:59]:Content 'ASC0000A.7' for package 'ASC0000A' has been added to content library successfully
[BB8][Wed 03/19/2014 15:10:59]:SetNamedSecurityInfo() failed.
[BB8][Wed 03/19/2014 15:10:59]:SetObjectOwner() failed. 0x80070003.
[BB8][Wed 03/19/2014 15:10:59]:SetFileSecurity() failed.
[BB8][Wed 03/19/2014 15:10:59]:Expanding ASC0000E to C:\RemoteInstall\SMSImages
[F20][Wed 03/19/2014 15:11:00]:Successfully expanded package ASC0000A to
\\ASC-DP1.LTCHARITY.ORG.UK\SMSPKGC$\ASC0000A
[F20][Wed 03/19/2014 15:11:00]:Waiting for another PXE operation thread to finish.
[F20][Wed 03/19/2014 15:11:05]:Finished waiting.
[F20][Wed 03/19/2014 15:11:11]:Expanding C:\SCCMContentLib\FileLib\DD54\DD5448253B423537C13072C96F3659FF0D1D51FDA5102BC7A68E4949269A0CA5 from package ASC0000A
[F20][Wed 03/19/2014 15:11:13]:Finding Wimgapi.Dll
[F20][Wed 03/19/2014 15:11:13]:MsiEnumRelatedProducts failed
[F20][Wed 03/19/2014 15:11:13]:FindProduct failed; 0x80070103
[F20][Wed 03/19/2014 15:11:13]:MsiEnumRelatedProducts failed
[F20][Wed 03/19/2014 15:11:13]:FindProduct failed; 0x80070103
[F20][Wed 03/19/2014 15:11:13]:Found C:\Windows\system32\wimgapi.dll
[F20][Wed 03/19/2014 15:11:19]:SetNamedSecurityInfo() failed.
[F20][Wed 03/19/2014 15:11:21]:SetObjectOwner() failed. 0x80070002.
[F20][Wed 03/19/2014 15:11:21]:SetFileSecurity() failed.
[BB8][Wed 03/19/2014 15:11:44]:Waiting for another PXE operation thread to finish.
[F20][Wed 03/19/2014 15:11:44]:Expanding ASC0000A to C:\RemoteInstall\SMSImages
[BB8][Wed 03/19/2014 15:11:49]:Finished waiting.
[BB8][Wed 03/19/2014 15:11:49]:CcmInstallPXE
[BB8][Wed 03/19/2014 15:11:49]:PXE provider is already installed.
[BB8][Wed 03/19/2014 15:11:49]:Installed PXE
[BB8][Wed 03/19/2014 15:11:49]:CSMSDPInstProv::EnableDPUsageStatsGathering entered
[BB8][Wed 03/19/2014 15:11:54]:1998-01-01T00:00:00
[BB8][Wed 03/19/2014 15:11:57]:A DP usage gathering task has been registered successfully
[BB8][Wed 03/19/2014 15:12:22]:Content 'ASC00003.4' for package 'ASC00003' has been added to content library successfully
[F20][Wed 03/19/2014 15:13:08]:CcmInstallPXE
[F20][Wed 03/19/2014 15:13:08]:PXE provider is already installed.
[F20][Wed 03/19/2014 15:13:08]:Installed PXE
[E7C][Wed 03/19/2014 15:13:08]:CSMSDPInstProv::EnableDPUsageStatsGathering entered
[E7C][Wed 03/19/2014 15:13:10]:1998-01-01T00:00:00
[E7C][Wed 03/19/2014 15:13:10]:A DP usage gathering task has been registered successfully
[F20][Wed 03/19/2014 15:13:33]:Content 'ASC00027.7' for package 'ASC00027' has been added to content library successfully
[F20][Wed 03/19/2014 15:13:33]:Expanding C:\SCCMContentLib\FileLib\4681\4681E1F7B35C465F8ADF176C71B2B4CCDA890F2857796DC81EA83B6FC05DBDC3 from package ASC00027
[F20][Wed 03/19/2014 15:13:33]:Finding Wimgapi.Dll
[F20][Wed 03/19/2014 15:13:33]:MsiEnumRelatedProducts failed
[F20][Wed 03/19/2014 15:13:33]:FindProduct failed; 0x80070103
[F20][Wed 03/19/2014 15:13:33]:MsiEnumRelatedProducts failed
[F20][Wed 03/19/2014 15:13:33]:FindProduct failed; 0x80070103
[F20][Wed 03/19/2014 15:13:33]:Found C:\Windows\system32\wimgapi.dll
[F20][Wed 03/19/2014 15:13:33]:SetNamedSecurityInfo() failed.
[F20][Wed 03/19/2014 15:13:33]:SetObjectOwner() failed. 0x80070002.
[F20][Wed 03/19/2014 15:13:33]:SetFileSecurity() failed.
[F20][Wed 03/19/2014 15:13:33]:Expanding ASC00027 to C:\RemoteInstall\SMSImages
[AF4][Wed 03/19/2014 15:14:03]:Waiting for another PXE operation thread to finish.
[AF4][Wed 03/19/2014 15:14:08]:Finished waiting.
[AF4][Wed 03/19/2014 15:14:08]:CcmInstallPXE
[AF4][Wed 03/19/2014 15:14:10]:PXE provider is already installed.
[AF4][Wed 03/19/2014 15:14:10]:Installed PXE
[AF4][Wed 03/19/2014 15:14:10]:CSMSDPInstProv::EnableDPUsageStatsGathering entered
[AF4][Wed 03/19/2014 15:14:19]:1998-01-01T00:00:00
[AF4][Wed 03/19/2014 15:14:22]:A DP usage gathering task has been registered successfully
[F20][Wed 03/19/2014 15:15:13]:Content 'ASC00002.4' for package 'ASC00002' has been added to content library successfully
[A9C][Wed 03/19/2014 15:15:56]:CcmInstallPXE
[A9C][Wed 03/19/2014 15:15:56]:PXE provider is already installed.
[A9C][Wed 03/19/2014 15:15:56]:Installed PXE
[A9C][Wed 03/19/2014 15:15:57]:CSMSDPInstProv::EnableDPUsageStatsGathering entered
[A9C][Wed 03/19/2014 15:15:57]:1998-01-01T00:00:00
[A9C][Wed 03/19/2014 15:15:58]:A DP usage gathering task has been registered successfully
================================================================================
Checked the SMSPXE.log:
<![LOG[================= PXE Provider loaded. =====================]LOG]!><time="15:05:22.792+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="smspxe.cpp:137">
<![LOG[Machine is running Windows Longhorn. (NTVersion=0X601, ServicePack=1)]LOG]!><time="15:05:22.792+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="provsettings.cpp:1112">
<![LOG[Cannot read the registry value of MACIgnoreListFile (00000000)]LOG]!><time="15:05:22.792+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="provsettings.cpp:353">
<![LOG[MAC Ignore List Filename in registry is empty]LOG]!><time="15:05:22.792+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="provsettings.cpp:468">
<![LOG[Begin validation of Certificate [Thumbprint 901708992FC1A759502B2BB7155E20FD7A1385D8] issued to 'dde18d94-b6ea-41d7-8e15-54844518c1b1']LOG]!><time="15:05:22.823+00" date="03-19-2014" component="SMSPXE" context=""
type="1" thread="2720" file="ccmcert.cpp:1662">
<![LOG[Completed validation of Certificate [Thumbprint 901708992FC1A759502B2BB7155E20FD7A1385D8] issued to 'dde18d94-b6ea-41d7-8e15-54844518c1b1']LOG]!><time="15:05:22.823+00" date="03-19-2014" component="SMSPXE" context=""
type="1" thread="2720" file="ccmcert.cpp:1803">
<![LOG[Initializing PXEPerfObject.]LOG]!><time="15:05:22.823+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="smspxe.cpp:399">
<![LOG[Could not load logging configuration for component ccmperf. Using default values.]LOG]!><time="15:05:22.823+00" date="03-19-2014" component="SMSPXE" context="" type="2" thread="2720"
file="stdlogging.cpp:480">
<![LOG[Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown.]LOG]!><time="15:05:24.414+00" date="03-19-2014" component="SMSPXE" context="" type="1"
thread="2720" file="ccmutillib.cpp:373">
<![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
]LOG]!><time="15:05:24.742+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="libsmsmessaging.cpp:6346">
<![LOG[PXE::CBootImageInfo::CBootImageInfo: key=]LOG]!><time="15:05:24.742+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="bootimagecache.cpp:60">
<![LOG[PXE::CBootImageInfo::CBootImageInfo: key=]LOG]!><time="15:05:24.742+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="bootimagecache.cpp:60">
<![LOG[CContentDefinition::GetAllPackagesFromLib failed; 0x80070003]LOG]!><time="15:05:24.836+00" date="03-19-2014" component="SMSPXE" context="" type="3" thread="2720" file="contentlibrary.cpp:925">
<![LOG[Begin validation of Certificate [Thumbprint 901708992FC1A759502B2BB7155E20FD7A1385D8] issued to 'dde18d94-b6ea-41d7-8e15-54844518c1b1']LOG]!><time="15:05:24.851+00" date="03-19-2014" component="SMSPXE" context=""
type="1" thread="2720" file="ccmcert.cpp:1662">
<![LOG[Completed validation of Certificate [Thumbprint 901708992FC1A759502B2BB7155E20FD7A1385D8] issued to 'dde18d94-b6ea-41d7-8e15-54844518c1b1']LOG]!><time="15:05:24.851+00" date="03-19-2014" component="SMSPXE" context=""
type="1" thread="2720" file="ccmcert.cpp:1803">
<![LOG[PXE Provider finished loading.]LOG]!><time="15:05:24.851+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="smspxe.cpp:184">
<![LOG[Cannot read the registry value of MACIgnoreListFile (800703e5)]LOG]!><time="15:05:29.048+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2700" file="provsettings.cpp:353">
<![LOG[MAC Ignore List Filename in registry is empty]LOG]!><time="15:05:29.048+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2700" file="provsettings.cpp:468">
<![LOG[Cannot read the registry value of MACIgnoreListFile (800703e5)]LOG]!><time="15:06:04.490+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="1408" file="provsettings.cpp:353">
<![LOG[MAC Ignore List Filename in registry is empty]LOG]!><time="15:06:04.490+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="1408" file="provsettings.cpp:468">
<![LOG[================= PXE Provider shutdown. =====================]LOG]!><time="15:06:39.371+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="smspxe.cpp:223">
==============================================================================
Have we missed something in these logs?
Can anyone help with this issue please?

Have you distributed both boot images (x86 and x64) to the PXE-enabled DP?
Torsten Meringer | http://www.mssccmfaq.de

WDS Server Service won't start - 'An error occurred trying to start the Windows Deployment Services Server.'

I'm having issues installing starting the WDS server service on Win 2008 R2, this is happening on multiple (all 2008 R2) systems on this domain so I'm beginning to think it's either AD or network related, in event viewer I get the following error.
'An error occurred trying to start the Windows Deployment Services Server.'
Error Information: 0x0906
EventID : 257
single domain, single forest, 2008 R2 functional level, both system are virtual plugged into same vswitch on a flat network.
any ideas what might be the issue? I've never had an issue getting this working on many occasions before today and I've come to many a dead end looking at other articles thus far...
With WDS tracing enabled I get the following error information:
[4304] 09:22:11: ===>Starting logging of module [WDSServer]
[4304] 09:22:11: [UDPPorts] Policy: 1, Dynamic Port Range: 64001-65000.
[4304] 09:22:11: [RPC] Using Tcp Port 5040 for Rpc Calls.
[4304] 09:22:11: [RPC] Client Impersonation Logging=Disabled
[4304] 09:22:11: [RPC] Host Name: sccm.domain.local
[4304] 09:22:11: [RPC] NTLM/Kerberos Spn: ldap/sccm.domain.local
[4304] 09:22:11: [RPC] Initialized
[3756] 09:22:11: [RPC] Server Started.
[4304] 09:22:11: [BINLSVC][RPC][Ep={5F4FB9F0-C0E3-41C1-AA00-9A7C690AC3A3}] Registered
[4304] 09:22:11: [BINLSVC] Provider Initialized.
[4304] 09:22:11: [WDSDDPS][RPC][Ep={FA0A27E1-C2BA-4B3B-94B2-025E82FFAA6D}] Registered
[4304] 09:22:11: [WDSDDPS][RPC][Ep={011D24AC-CB3A-4739-A339-5D2E1B5306CE}] Registered
[4304] 09:22:11: [51][WDSDDPS] [d:\w7rtm\base\ntsetup\opktools\wds\ddp\server\ddpprovider.cpp:196] Expression: , Win32 Error=0x906
[4304] 09:22:11: [WDSDDPS][RPC][Ep={FA0A27E1-C2BA-4B3B-94B2-025E82FFAA6D}] Closed
[4304] 09:22:11: [WDSDDPS][RPC][Ep={011D24AC-CB3A-4739-A339-5D2E1B5306CE}] Closed
[4304] 09:22:11: [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsprovider.cpp:144] Expression: , Win32 Error=0x906
[4304] 09:22:11: [WDSDDPS] Initialization Failed (rc=2310)
[4304] 09:22:11: [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsprovhdl.cpp:172] Expression: , Win32 Error=0x906
[4304] 09:22:11: [WDSDDPS] Deleted.
[4304] 09:22:11: [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsservice.cpp:178] Expression: , Win32 Error=0x906
[4304] 09:22:11: [Udp] Listen Shutdown.
[3756] 09:22:11: [RPC] Server terminated (rc=0)
[4304] 09:22:11: [RPC] Listen Stopped.
[4304] 09:22:11: [BINLSVC] Shutting down
[4304] 09:22:11: [BINLSVC][RPC][Ep={5F4FB9F0-C0E3-41C1-AA00-9A7C690AC3A3}] Closed
[4304] 09:22:11: [BINLSVC] Deleted.

It seems I've found out the solution myself, the issue seems to be caused when DHCP and WDS are on the same server, The installation must identify this during the first installation of WDS but not on subsequent installations, the method to
get it working again is:
1.
Install WDS Role (using defaults)
2.
Make the following registry change:
HKLM\SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSPXE\UseDhcpPorts = 0
3.
Run the following command line to initialize Windows Deployment Services:
wdsutil /initialize-server /reminst:D:\RemoteInstall
4.
Run the following command to enable the DHCP port registry setting
wdsutil /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes

How can I use Powershell to "Complete dhcp configuration" ?

I installed the DHCP Server feature with Powershell and now I'm wondering how to "Complete dhcp configuration" also with Powershell?
Here's what I did (example):
Install-WindowsFeature DHCP -IncludeManagementTools
Add-DhcpServerv4Scope -name "Corpnet" -StartRange 10.0.0.100 -EndRange 10.0.0.200
-SubnetMask 255.255.255.0
Set-DhcpServerv4OptionValue -DnsDomain corp.contoso.com -DnsServer 10.0.0.1
Add-DhcpServerInDC -DnsName dc1.corp.contoso.com
"Server Manager |> DHCP" now informs me that "Configuration required for DHCP Server at DC1" and by selecting "More" I can "Complete dhcp configuration". So, how do I complete the task with Powershell?
Thanks!

I installed the DHCP Server feature with Powershell and now I'm wondering how to "Complete dhcp configuration" also with Powershell?
Here's what I did (example):
Install-WindowsFeature DHCP -IncludeManagementTools
Add-DhcpServerv4Scope -name "Corpnet" -StartRange 10.0.0.100 -EndRange
10.0.0.200 -SubnetMask 255.255.255.0
Set-DhcpServerv4OptionValue -DnsDomain corp.contoso.com -DnsServer 10.0.0.1
Add-DhcpServerInDC -DnsName dc1.corp.contoso.com
"Server Manager |> DHCP" now informs me that "Configuration required for DHCP Server at DC1" and by selecting "More" I can "Complete dhcp configuration". So, how do I complete the task with Powershell?
Thanks!
For a very belated answer, you need to set a registry value to tell it that the configuration has been completed.
Set-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\ServerManager\Roles\12 -Name ConfigurationState -Value 2;
Restart-Service DHCPServer;

Trouble booting to WDS server to deploy or capture image

Hello, we have an existing WDS server running Server 2008 R2 with SP1. I am having trouble getting a Surface Pro 3 to boot to the WDS (even after creating updated deploy and capture boot images). I can get the Surface to PXE boot, and I am
able to choose the Deploy or Capture boot image, but then I get the message that an error occurred obtaining an IP address from the DHCP server. During the PXE boot, the device does obtain an IP address in the correct range. I tried adding the
Surface ethernet adapter drivers to the boot wims but since they are not signed I get errors that they cannot be added. Any suggestions?

Added drivers to boot images using DISM with the /ForceUnsigned override.

Windows 2008 DNS & DHCP configuration steps for 11gR2 GI install with GNS

Hi,
I have windows 2008 R2 server with DNS & DHCP services installed. I am planning to install 2 node RAC with GNS option.
The problem is i could not find any document to setup the windows 2008 DNS server for the below steps.
a. Configure GNS VIP : add a name resolution entry in a DNS for the GNS virtual IP address in the forward Lookup file.
gns-server IN A <virtual_IP>
where gns-server is the GNS virtual IP address given during grid installation.
b. Configure the GNS sub-domain delegation: add an entry in the DNS to establish DNS Lookup that directs the DNS resolution of a GNS subdomain to the cluster.
clusterdomain.example.com. NS gns-server.example.com.
where clusterdomain.example.com is the GNS subdomain (provided during grid installation) that you
delegate and gns-server.clustername.com resolves to GNS virtual IP address.
I am aware that this configuration steps has to be taken care by the System administrator. Here is what he tried and the results.
My SA was able to Configure GNS VIP in the DNS and the Nslookup works fine for this.
When he Configures the GNS sub-domain delegation the nslookup fails when trying to resolve the SCAN name.
Any step by step tutorial for this windows 2008 DNS & DHCP configuration for Oracle GNS setup would be highly appreciated.
Thanks,
Ashok Kumar.G

Hi Guys,
Any help on this request will be very helpful.
Thanks,
Ashok Kumar.G

Boot an ESX 5.1 VM to my SCCM 2012 (WDS) server?

Hi folks,
I just got my SCCM 2012 server installed, configured a distribution point, published new boot.wim to distribution point.
I am trying to test booting up a 'bare metal' ESXi 5.1 VM to my SCCM 2012 (WDS) server, but fails with attached error.
Configuration Manager is looking for policy.
Anyone have a suggestion?
Thanks, romatlo

Thank you so much for responding! I must admit that this is my first install. :)
I could not find that option, so I deleted/recreated my task sequence, then found it as part of Deploy option.
I deployed the task sequence to unknown computers but I still get that message and will not boot up correctly.
I've pasted last part of my SMSPXE.log in case you see something definitive.
I did not have my WDS server role installed when enabling PXE on my DP, maybe that messed me up.
Thanks again, I may snapshot my VM here and start over on install if there is not a clue.
<![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
]LOG]!><time="22:34:31.229+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="libsmsmessaging.cpp:6346">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: device is in the database.]LOG]!><time="22:34:31.229+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
]LOG]!><time="22:34:31.273+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="libsmsmessaging.cpp:6544">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: no advertisements found]LOG]!><time="22:34:31.273+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: No boot action. Aborted.]LOG]!><time="22:34:31.319+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: Not serviced.]LOG]!><time="22:34:31.319+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
]LOG]!><time="22:34:33.422+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="libsmsmessaging.cpp:6544">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: no advertisements found]LOG]!><time="22:34:33.422+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">

Anchor Guest controller and DHCP configuration

I checked the cisco documentation about the DHCP configuration but I´m not 100%sure which DHCP server address I must use.
I used as example the scope 10.240.97.0/24 for our Guest Users. In this range are the DHCP scope and the Guest interface configured. For the management I used as example the range 10.240.96.0/24.Now I configured our Guest WLC and I insert on the Guest interface as Primary DHCP address the Guest interface address. After I applied I got the message I can´t use this DHCP address. Now I checked the cisco and found following description:
“If DHCP services are to be implemented locally on the anchor controller, populate the primary DHCP server field with the management IP address of the controller"
Means it now I must insert as the IP for the Primary DHCP Server on the Guest interface the IP from the management
Interface and the controller will then forward the traffic to the internal DHCP scope on the Guest subnet and wil sent it back ?
( DHCP proxy is on the Guest WLC enabled ) .
Thanks
Al

For Anchor you can use either internal or external dhcp server.
Means it now I must insert as the IP for the Primary DHCP Server on the Guest interface the IP from the management
Interface and the controller will then forward the traffic to the internal DHCP scope on the Guest subnet and wil sent it back ?
Yes. WLC forwards the unicast dhcp req to management ip for guest interface. All cpu generated traffic by default uses management interface as source address i.e., snmp, radius, ping...
Is your question whether you need routing between guest and management interface.
No, routing is not required in this case bcoz the interface residing on WLC's management. Also for proxy it uses the virtual ip address for dhcp instead of actual dhcp ip. And only wireless client can get ip from WLC's internal dhcp server.
If you're using dhcp proxy on wlc and having external dhcp server on different vlan then yes you need routing between the two vlans.

WDS ignores DHCP

We just recently upgraded our PXE server since I handle some Windows imaging issues to Server 2012 R2 due to MDT and special imaging upgrades for Windows 8.1.
The server was installed clean to a virtual machine, but now I have a weird issue with the Server 2012 R2. I have installed WDS and DHCP, but whatever I do the outcome is the same. All computers successfully make contact to the WDS server and
all our Legacy machines run properly on connecting to WDS to our MDT server. However, the UEFI machines won't make contact.
On our Samsung Ultrabooks on UEFI w/secure boot off
This happens
>>Start PXE over IPv4
Station IP address is 10.108.0.38
Server IP address 10.72.10.217
NBP filename is boot\x86\wdsnbp.com
NBP filesize is 30832
Downloading NBP File.
Succeed to download NBP File.
Downloading NBP File
Succeed to download NBP File
Downloading NBP File
Succeed to download NBP File
The boot menu comes back up.
On our Samsung Ultrabooks on UEFI w/secure boot on
All I get is an error message. Image failed to verify with *Access Denied*. Press any key to continue
On our Samsung Ultrabooks on Legacy
It boots into MDT normally without issue.
I know the problem lies here NBP filename is boot\x86\wdsnbp.com, but the DHCP on the server doesn't seem to be affected by it. I can have it disabled and the results are the same.
Any ideas?

Hi,
This might be an incompatibility issue.
The following thread may give you some hints:
http://social.technet.microsoft.com/Forums/en-US/3a91050c-b5fc-4f4c-8e0f-e96e7bfe6f3f/sccm-2012-sp1-pxe-boot-lenovo-thinkpad-tablet-2?forum=configmanagerosd

Airports fail to serve DHCP addresses

I am having trouble reconfiguring an existing network with 2 Airport devices -- switching to having the Airports serve addresses via DHCP is failing, and would appreciate help determining what I'm doing wrong here.
Details:
I have a network with a 16-IP public address space x.x.x.208-223. My DSL router/firewall is at x.209, and I have various devices with manually assigned statics IPs in the x.210-x.218 range. The router is configured to serve up the last 4 IP addresses x.219-x.222 via DHCP. Within the static IP range, I have a Time Capsule at x.210 and an Airport Express at x.214, located at far ends of the house, and running differently named wireless networks. They have so far been configured with [Connection sharing: Off (Bridge Mode)] Under Internet > Internet Connection and appropriate manual settings under Internet > TCP/IP.
All has worked fine with this configuration to-date. Our few devices without a static IP were assigned DHCP addresses from the 219-222 range, whether connected via our hard-wired ethernet network, or over either wireless network -- the addresses picked up from the router at 209.
While the 4 addresses available by DHCP were previously sufficient, with the proliferation of mobile devices in my family, it's not enough anymore, and I am trying to reconfigure the Airports to serve up private network blocks 10.0.x.x and 10.0.y.y via DHCP [Connection sharing: Share a public IP address]. This is not working. When I reconfigure either Airport in this manner, network devices connecting via wireless no longer can connect to the internet. Connection to the wireless network itself is fine, but the device is unable to get a DHCP address from the Airport. Instead, after a short delay it gets a self-assigned address in the 169.254.x.x range. This happens with either Airport base station, and both with my iPhone 4 as well as my MacBook Pro.
Thinking that having the router serve DHCP within the public space might be interfering with the Airport DHCP in its own private block, I tried disabling DHCP at the router. Even so, I cannot get the Airports to start serving IP addresses to their wireless clients.
Any suggestions ?

Hi Linc,
I appreciate the discussion. Let me reply in-line
Linc Davis wrote:
I'm having a lot of trouble understanding your questions. Rather than trying to figure it out, let me tell you how it should work.
You have a DSL modem that is also a router. It gets an address for its WAN interface from your ISP's DHCP server, or it has a static address -- doesn't matter which.
My router has a static WAN IP address, which is in my ISP's subnet. The LAN is my own public subnet 209.128.72.208/28, and the router's LAN IP address is 209.128.72.209.
It had better not be serving DHCP on the WAN, or you may get kicked off by your ISP. I'd be surprised if you were even able to configure it that way.
No, it's not serving DHCP on the WAN. It is serving DHCP only on the LAN, in the 209.128.72.219-222 range.
The router's LAN interface has a fixed private IP address that you configure. It serves DHCP to other devices on the LAN.
Yes, that is how it is.
The AE can get an address from the router for its Ethernet port from the router, or it can have a fixed address, whichever you want.
Yes, it is configured with its own static, manually configured address, which is 209.128.72.214, outside of the DHCP range served by the router.
Set it to operate in bridge mode, which means that the wireless network will be like an extension of the wired network, with the same address pool. Wireless devices will get their addresses from the router.
Yes. To-date I have operated it in bridge mode, exactly that way. And it's worked great up until now. Devices with manually assigned IP addresses in the 209.128.72.210-218 range have worked fine either when connected by ethernet or wireless, and those without (iPhones, etc) have picked up DHCP addresses from the router just fine.
The AE does not need to be a DHCP server.
Unless your needs are very unusual, that setup will work for you.
And so it has worked that way for a while. However, my needs have changed recently. The range of available IPs for DHCP from the router is limited to 4 devices (209.128.72.219-222). That worked fine when we had only 4 devices (iPhone, iPad, Roku, and Blackberry). Now, the kids have wireless devices (iPod touch and an old iPhone). The available range is not sufficient for 6 devices. So, rather than serve wireless devices with addresses from the limited remaining IPs in the public subnet, I want to have the AE serve DHCP in a private network 10.1.x.0/24 , which obviously has alot more room.
I'm willing to try turning off DHCP on the router completely. That doesn't seem to help -- I've tried it twice.

Make ap 1600 as server dhcp

i have issue with my AP 1602i SAP i wanna to configure server dhcp to allow ip addresses dynamically so can any one told me if it's possible to make my access point as server dhcp for the client dhcp

Hi,
You can configure an autonomous AP as a dhcp server. A typical configuration would be as below.
AP# configure terminal
AP(config)# ip dhcp excluded-address 172.16.1.1 172.16.1.20
AP(config)# ip dhcp pool wishbone
AP(dhcp-config)# network 172.16.1.0 255.255.255.0
AP(dhcp-config)# lease 10
AP(dhcp-config)# default-router 172.16.1.1
AP(dhcp-config)# end
Hope that helps.
Regards
Najaf

DHCP configuration options

Can anyone tell me how to change the DHCP configuration options - the same information found in dhclient.conf in linux/unix - under OSX? A corporate client of mine provides wireless internet at all their facilities, but no one with a Mac has ever been able to connect. The wireless connection comes up and is stable, but the Mac never receives an IP address. I am fairly certain they forward DHCP requests to a centralized server that handles multiple LAN segments. I suspect something in the format of the DHCP packet, perhaps one of the many options, is causing their router to drop the Mac's DHCP request packet. I have captured DHCP requests from OSX and Win2K using Ethereal, so I have some idea what options to try changing, but I need to know how to go about it. I've tried adding a dhclient.conf file, but OSX seems to ignore this.
Needless to say, this is not a simple question and I realize I'll be fiddling at low levels. However, I've tried everything there is to try with the control panel, command lines, etc. I generally have no problems getting WiFi to work across Mac and windoze whether at home, in hotel rooms, or at corporate locations, but this one really has me stumped. Any help is appreciated.

How are you connecting to the wireless network? Is it a closed network with security, or an open network? There are a lot of different protocols in play with a wireless connection, particularly with Cisco equipment. It's possible Macs don't support one of the protocols where Windows does. There may be extra security such as DHCP client IDs, or using DHCP reservations only. There could be MAC address security setup on the wireless APs.
I would ask one of your PC buddies help you find an unused address. Set that manually and see if everything works. If it does you know you have a DHCP problem. If it doesn't there's a problem with the wireless connection

WDS Server DHCP configuration

Similar Messages

Maybe you are looking for