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

Similar Messages

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

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

Apple devices ignoring DHCP rules - using up all my IP addresses on the FiOS-G1100

Your lease time may be causing a bug in the DHCP client on Apple devices. That is an unusually long lease time so I wouldn't be surprised if it was something like an integer vs float vs signed integer problem in the code. Please consider cutting the leases down to 3600 minutes, and then use DHCP Reservation for any devices that you own which you would like to keep on a fixed IP.
Now if this is for guest devices, consider limiting your least time to 30 to 60 minutes. Many devices are mobile and do not need 90 day long leases. That's wasteful of an otherwise limited IP subnet.

Apple devices ignoring DHCP rules - using up all my IP addresses on the FiOS-G1100 Hi all, I have now gone through two of the new quantum gateways and both allow Apple devices of all kinds to bypass the lease time that I set to something like 129600 Minutes for that specific IP Address (which is 90 days, or three months). People using our guest network end up taking all our non-static addresses and then we have none left to issue out to other users or staff. I'm about to receive my third g1100 from Verizon and I'm pretty sure it's not the box but the firmware. I've had to do 2-3 hard resets on both boxes since Jan '15 to erase everything and start over with loading custom settings back in. A Huge pain. Once all addresses are taken up and you login as Admin on the router, half of the UI options have now disappeared. Also in general there is no way to manually force the router to expire LAN IP addresses even after a hard reset. Or is there and I just have never seen this option? Anyone else experience this? I've spent about 3 hours with multiple reps who either don't believe me or have no idea how their product works. I'm beginning to either think I'm crazy or there's a bug and no one has reported it yet. Best,Lockdown

Multiple SSIDs with WDS, custom DHCP addresses, & Web interface

I just bought an Aiport Extreme Base station along with an Aiport Express. So far, everything is great, but I had a few of things I would like configure a certain way, and I am having a little problem.
Just to let you know, I am using the base station as the main router/firewall (with my cable modem). I am using the express basically as a wireless bridge (via WDS).
The way Apple takes care of things with WDS, is by assiging the same SSID to both the base station and express for seamless roaming. However, I would like them both to have their own SSID. I cannot seem to get this working, and I know that some other vendors allow this (Buffalo, Linksys).
The other issue is regarding DHCP on the LAN side. I want to for example hand out IP addresses 192.168.2.50-60 to my internal clients, and I want the base station to have an address of 192.168.2.1 and the express to have 192.168.2.5. It seems this also I am having problems with. It seems like the base station is very rigid on what options I have in this regard.
Lastly, I wondered if there is any other way to administer these guys (like a web browser). Sometimes I need to remotely make changes to the router, and don’t really want to install another app just for this purpose (especially at work, or some other remote location).
Thanks
Mac Mini 1.25 GHz Mac OS X (10.4.3) 1 Gig of RAM

The way Apple takes care of things with WDS, is by
assiging the same SSID to both the base station
and
express for seamless roaming. However, I would
like
them both to have their own SSID.
I don't know why you'd want that but if you are
extending the range of your wireless network with WDS
it isn't possible with Airports.
The other issue is regarding DHCP on the LAN side.
I
want to for example hand out IP addresses
192.168.2.50-60 to my internal clients, and I want
the base station to have an address of 192.168.2.1
and the express to have 192.168.2.5. It seems this
also I am having problems with.
You can set the DHCP range and then assign static
IP's to anything that conforms to that network as
long as it won't conflict with something
automatically assigned by DHCP. As a router NAT must
be enabled so if you want a unique range of numbers
only DHCP is used which won't work in your case.
In other words set the range at 192.168.1.1 and that
is the address of the base station. That can be used
for the statically IP'd device's router and DNS
entries as well like this:
Device 1 IP 192.168.1.101
Device 1 subnet 255.255.255.0
Device 1 router 192.168.1.1
Device 1 DNS 192.168.1.1
Device 2 IP 192.168.1.102
Device 2 subnet 255.255.255.0
Device 2 router 192.168.1.1
Device 2 DNS 192.168.1.1
etc...
Lastly, I wondered if there is any other way to
administer these guys (like a web browser).
Not that I'm aware of. Airport Admin Utility is all
there is. I have seen a java utility but it wasn't
very friendly.
Thanks for the answers. Despite these minor limitations, so far the Apple hardware is some of the best 802.11 stuff I have used (except for maybe a Cisco 1200).

Windows Server 2012 R2 WDS no DHCP on PXE boot

We upgraded all of our Server 2008 R2 servers with WDS to new OS 2012 R2 with WDS. After upgrade WDS no longer works, all computers will not get an IP address from DHCP after server was upgraded. We are not using DHCP Options since at this
time we have added IPHelper address on each VLan The only change that has been done was a upgrade from 2008 R2 to 2012 R2
Any help would be greatly appreciated
Kent

WDS server and DHCP servers are on different servers. Everything was working fine until upgraded to 2012 R2. Original setup was Server 2008 R2. After upgrade press f12 on the workstation and it just hangs on obtaining IP
depending on your AD configuration, DHCP servers will not function if they have not been authorized in the AD.
Is the DHCP service on the new DHCP service starting correctly?
If not starting, the event logs on the server will reveal if not authorized.
If starting and authorized, is the DHCP server showing requests arriving, and leases being issued?
If so, are the DHCP responses/offers being sent from DHCP, and being received by the client?
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

WDS and DHCP issues

Hi
I have a series of 1200 series access points, set-up for WDS infrastructure mode to ACS and client authentication to Microsoft IAS.
When set up in WDS mode, clients authenticate to the IAS server (and event viewer confirms this), but clients do not receive an ip address - even though they do DHCP requests.
anyone offer advice on any similar issues?

Can you provide more information on the deisgn?
Are you using VLANs in your wireless config? If so, does your router or switch have the ip helper address specified for DHCP requests?
If not, can you obtain an address when the client is plugged into the same port as the access point?

PXE, WDS and DHCP Option 66 and 67 PXE-M0F: Exiting

Hello,
I have configured DHCP options 66 and 67 to point to my site server running WDS and SCCM 2012 R2 with a DP with PXE enabled.
My DHCP server is on 10.1.54.199 and my sccm server is on 10.1.184.60 whilst my client is on 10.1.141.245. I have set the options in DHCP to 10.1.184.60 and SMSBoot\x86\wdsnbp.com
When i boot my client I get
Client MAC:xxxx GUID:xxxxxClient IP: 10.1.141.245, MASK: 255.255.254.0, DHCP IP: 10.1.54.199Gateway IP: 10.1.140.1TFTP.PXE-M0F: Exiting Intel Boot Agent.
Can anyone offer any help on where to begin troubleshooting this? Previously this has all worked but the server was recently moved to a new IP address and VLAN where IP helpers are not configured. This method worked a treat for us in 2007 but for whatever
reason not in 2012?
Any advice would be greatly appreciated.

Hi Gerry, Yes When I added the second DP to the All DPs Distribution Point Group it then went and distributed some 70 or so packages, among these were the boot images. I just double checked and the second DP is listed in the content locations tab for both
boot images.
Hi Jason,
Not yet but when i tried this earlier (16:00 ish where I am) the date modified time of the log had not changed (it reported sometime like 14:30). I will have a look in the log... It has indeed changed...
It seems to be looping through a process of:
Begin Validation of Certificate thumbprint...
Completed Validation of Certificate thumbprint...
PXE Client Certificate Valid...
Purging Old Images 0...
Purging Old Images 0...
There are a few lines above from a few hours earlier (when i installed the second DP and enabled PXE) where it shows it adding files to install que, No errors though. Further up the log I can see errors...
Initializing PXEPerfObject. SMSPXE 18/02/2014 14:21:18 3164 (0x0C5C)
Failed to get logging settings for 'ccmperf' from Registry (80070002) SMSPXE 18/02/2014 14:21:18 3164 (0x0C5C)
Could not load logging configuration for component ccmperf. Using default values. SMSPXE 18/02/2014 14:21:18 3164 (0x0C5C)
Client is set to use HTTPS when available. The current state is 224. SMSPXE 18/02/2014 14:21:19 3164 (0x0C5C)
CLibSMSMessageWinHttpTransport::Send: URL: primary-site-server.co.uk:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 18/02/2014 14:21:19 3164 (0x0C5C)
RequestMPKeyInformation: Send() failed. SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
Failed to get information for MP: http://primary-site-server.co.uk. 80004005. SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
PXE Provider failed to initialize MP connection.
Unspecified error (Error: 80004005; Source: Windows) SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
CLibSMSMessageWinHttpTransport::Send: URL: primary-site-server.co.uk:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
RequestMPKeyInformation: Send() failed. SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
Failed to get information for MP: http://primary-site-server.co.uk. 80004005. SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
PXE::CPolicyProvider::InitializeMPConnection failed; 0x80004005 SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 18/02/2014 14:21:21 3164 (0x0C5C)
I am not sure if the above is relevant but it is the only stuff marked red in cmtrace in SMSPXE thats around the timeframe where I was testing it earlier today.
Any suggestions?
EDIT: I dont think I have imported the web server certificate on the second DP or configured IIS to use this cert for https, I am guessing that is what these error are all about? Not sure why this would effect PXE though especially as it should be getting the
content from the first DP. I will crack on sorting this cert problem tomorrow and see if it fixes the issue I am having with PXE with no IP Helper.
EDIT 2: I also changed the DHCP option 67 from SMSBoot\x86\wdsnbp.com to SMSBoot\\x86\\wdsnbp.com. It may have been the \\ in here that also helped solve my problem.

WDS PXE DHCP, Clients on different subnet

Hello,
We are having a lot of trouble trying to get pxe imaging working from our WDS server on different subnets. We have an existing Zenworking imaging setup working as of right now, but WDS is causing more issues than I care to troubleshoot. I have read
blog after blog, forum post after forum post and everyone says just install it and it works! I guess we have run into some sort of problem that nobody else has.
Enviroment:
2x DC's, Server 2012 R2, both run DNS, 10.5.0.101, 10.5.0.102
1x DHCP Server, 2012 R2, 10.5.0.105
1x WDS Server, 2012 R2, 10.5.0.41
If I put a client on the same subnet as all of the servers it seems to work, except for the fact that it takes a while for the client to get an IP and continue to load wdsnbp.com. I would say around 20-30 seconds. In our zenworks enviroment it takes
no more than 1 second to get an IP. As for the dhcp server itself, clients receive normal dhcp offers instantly. So that part is working properly.
Now when I try an access the WDS pxe server from a different subnet other than the one that all of the servers are on, noting that I do have the ip helper address setup on our layer 3 switch:
interface Vlan2025
ip address 10.200.20.1 255.255.255.0
ip helper-address 10.5.0.105
ip helper-address 10.5.0.41
It always says failed to receive boot file. But as I said earlier, clients in windows receive dhcp leases from 10.5.0.105 without issue.
Setting the client options in the DHCP server with options 66 and 67 works sortof, but we found that it was unreliable and often finicky. Like having the system repeatedly ask to press f12, and even if you did press f12 it would still ask to press f12
again.
So I continued to do a wirehark packet capture on the port where the device was trying to get the dhcp/pxe info from the DHCP / WDS servers. The first packet here is from the DHCP server and the second is from the WDS server.
Bootstrap Protocol
Message type: Boot Reply (2)
Hardware type: Ethernet (0x01)
Hardware address length: 6
Hops: 0
Transaction ID: 0xd6c565d2
Seconds elapsed: 0
Bootp flags: 0x8000 (Broadcast)
Client IP address: 0.0.0.0 (0.0.0.0)
Your (client) IP address: 10.200.20.117 (10.200.20.117)
Next server IP address: 10.5.0.105 (10.5.0.105)
Relay agent IP address: 10.200.20.1 (10.200.20.1)
Client MAC address: Hewlett-_c5:65:d2 (78:e7:d1:c5:65:d2)
Client hardware address padding: 00000000000000000000
Server host name not given
Boot file name not given
Magic cookie: DHCP
Option: (53) DHCP Message Type
Length: 1
DHCP: Offer (2)
Option: (1) Subnet Mask
Length: 4
Subnet Mask: 255.255.255.0 (255.255.255.0)
Option: (58) Renewal Time Value
Length: 4
Renewal Time Value: (21600s) 6 hours
Option: (59) Rebinding Time Value
Length: 4
Rebinding Time Value: (37800s) 10 hours, 30 minutes
Option: (51) IP Address Lease Time
Length: 4
IP Address Lease Time: (43200s) 12 hours
Option: (54) DHCP Server Identifier
Length: 4
DHCP Server Identifier: 10.5.0.105 (10.5.0.105)
Option: (3) Router
Length: 4
Router: 10.200.20.1 (10.200.20.1)
Option: (6) Domain Name Server
Length: 8
Domain Name Server: 10.5.0.101 (10.5.0.101)
Domain Name Server: 10.5.0.102 (10.5.0.102)
Option: (15) Domain Name
Length: 8
Domain Name: domain.com
Option: (255) End
Option End: 255
Bootstrap Protocol
Message type: Boot Reply (2)
Hardware type: Ethernet (0x01)
Hardware address length: 6
Hops: 0
Transaction ID: 0xd2c565d2
Seconds elapsed: 4
Bootp flags: 0x8000 (Broadcast)
Client IP address: 0.0.0.0 (0.0.0.0)
Your (client) IP address: 0.0.0.0 (0.0.0.0)
Next server IP address: 10.5.0.41 (10.5.0.41)
Relay agent IP address: 10.200.20.1 (10.200.20.1)
Client MAC address: Hewlett-_c5:65:d2 (78:e7:d1:c5:65:d2)
Client hardware address padding: 00000000000000000000
Server host name: wds1.domain.com
Boot file name not given
Magic cookie: DHCP
Option: (54) DHCP Server Identifier
Length: 4
DHCP Server Identifier: 10.5.0.41 (10.5.0.41)
Option: (97) UUID/GUID-based Client Identifier
Length: 17
Client Identifier (UUID): eb8daa31-8e62-11df-bbd8-d1c565d278e7
Option: (60) Vendor class identifier
Length: 9
Vendor class identifier: PXEClient
Option: (53) DHCP Message Type
Length: 1
DHCP: Offer (2)
Option: (255) End
Option End: 255
What I find interesting is that the WDS server is not handing out a boot file name:
"Boot file name not given"
Could this be the reason why we receive the no boot file received error when trying to boot a client into pxe?
The other thing that I noticed was that the WDS server is also responding with the:
" Option: (60) Vendor class identifier
Length: 9
Vendor class identifier: PXEClient
Why would it be responding with this, when the dhcp is on a separate server. Is this option only if you have DHCP and WDS on the same server?
Any help would be appreciated as there has been too much time already spent on getting nowhere.
Thanks,
Dan.

Dan,
10 months later and not one reply... I'm having the same issue, did you ever figure this out? DHCP server is my Cisco Switch, WDS/PXE is on another network. The WDS and PXE is working fine as I can do so from the same network as the WDS/PXE
server. I can also get the WDS/PXE to work if I have a MS DHCP server on a different network and populate the option 66 and option 67. I cannot get this to work using Cisco ip helper-address for some reason.
Thanks,

SPA941 ignoring DHCP Option 66,150

I've configured a HTTP provisioning server and have set up a Cisco ASA to send out the address via DHCP. Currently this setup works for the SPA504Gs which will get the address and provision correctly. The SPA941s however won't co-operate. They don't seem to get the settings from these options, however they do get the IP address via DHCP.
Any help would be grateful thanks!

With DHCP, you will need either option 150 or 66 configured. When the Phone boots and gets information from the DHCP Server the following order if followed to connect to the TFTP Server and download the configuration.
1) Hardcoded TFTP Address
2) DNS lookup of CiscoCM1
3) Option 150
4) DHCP si_addr field
5) DHCP sname field
6) Option 66

DHCP WDS Error

Hi. Im having a problem where I get the error 'An error occurred while obtaining an IP address from the DHCP server. Please check to ensure that there is an operational DHCP server on this network segment'when booting from a standard WDS boot.wim image taken
from a Windows 7 DVD.
I am using Server 2008 R2 and am adding the drivers to the boot using WDS, but also have the problem if the drivers are injected beforehand using DISM.
When the error occurs I can shift + F10 and IPCONFIG and see it HAS picked up an internal IP from DHCP. Seems maybe it is timing out before it gets the IP?
As per some fixes I have read I enabled RSTP on my switches but that didnt help.
I have included the end of setupact.log to see if any of you have any ideas.Seems to be failing but as I say, the network IS initialized as I can see the internal IP assigned by DHCP when running IPCONFIG.
I dont suppose theres any way of increasing the timeout?
Thanks.
2011-04-11 17:26:31, Info       [0x0b0022] WDS    StartNetworking: Trying to start networking.
2011-04-11 17:26:31, Info                  WDS    Network service dhcp not running or could not be queried: 264d00 1 1
2011-04-11 17:26:31, Info                  WDS    Network service lmhosts not running or could not be queried: 264e18 1 1
2011-04-11 17:26:31, Info                  WDS    Network service lanmanworkstation not running or could not be queried: 264d00 1 1
2011-04-11 17:26:31, Info                  WDS    Network service bfe not running or could not be queried: 264e18 1 1
2011-04-11 17:26:31, Info                  WDS    Network service ikeext not running or could not be queried: 264d00 1 1
2011-04-11 17:26:31, Info                  WDS    Network service mpssvc not running or could not be queried: 264e18 1 1
2011-04-11 17:27:24, Info                  WDS    Installing device pci\ven_14e4&dev_1691&subsys_04aa1028 X:\WINDOWS\INF\oem37.inf succeeded
2011-04-11 17:27:25, Info                  WDS    No computer name specified, generating a random name.
2011-04-11 17:27:25, Info                  WDS    Renaming computer to MININT-VN2P876.
2011-04-11 17:27:25, Info                  WDS    Acquired profiling mutex
2011-04-11 17:27:25, Info                  WDS    Service winmgmt disable: 0x00000000
2011-04-11 17:27:25, Info                  WDS    Service winmgmt stop: 0x00000000
2011-04-11 17:27:25, Info                  WDS    Service winmgmt enable: 0x00000000
2011-04-11 17:27:25, Info                  WDS    Released profiling mutex
2011-04-11 17:27:25, Info                  WDS    Acquired profiling mutex
2011-04-11 17:27:25, Info                  WDS    Install MS_MSCLIENT: 0x0004a020
2011-04-11 17:27:25, Info                  WDS    Install MS_NETBIOS: 0x0004a020
2011-04-11 17:27:25, Info                  WDS    Install MS_SMB: 0x0004a020
2011-04-11 17:27:25, Info                  WDS    Install MS_TCPIP6: 0x0004a020
2011-04-11 17:27:26, Info                  WDS    Install MS_TCPIP: 0x0004a020
2011-04-11 17:27:26, Info                  WDS    Service dhcp start: 0x00000000
2011-04-11 17:27:26, Info                  WDS    Service lmhosts start: 0x00000000
2011-04-11 17:27:26, Info                  WDS    Service ikeext start: 0x00000000
2011-04-11 17:27:26, Info                  WDS    Service mpssvc start: 0x00000000
2011-04-11 17:27:26, Info                  WDS    Released profiling mutex
2011-04-11 17:27:26, Info                  WDS    Spent 967ms installing network components
2011-04-11 17:27:28, Info                  WDS    Spent 2247ms installing network drivers
2011-04-11 17:27:38, Info                  WDS    QueryAdapterStatus: no operational adapters found.
2011-04-11 17:27:38, Info                  WDS    Spent 10140ms confirming network initialization; status 0x80004005
2011-04-11 17:27:38, Info                  WDS    WaitForNetworkToInitialize failed; ignoring error
2011-04-11 17:27:38, Info                  WDS    GetNetworkingInfo: WpeNetworkStatus returned [0x0]. Flags set:
2011-04-11 17:27:38, Error      [0x0b003f] WDS    StartNetworking: Failed to start networking. Error code [0x800704C6].[gle=0x000000cb]
2011-04-11 17:27:38, Info       [0x0640ae] IBSLIB PublishMessage: Publishing message [WdsClient: An error occurred while obtaining an IP address from the DHCP server. Please check to ensure that there is an operational DHCP server
on this network segment.]

Thanks for the reply. I have came across the post about removing setup.exe etc but thats a nasty hack and Id rather get the thing working properly.
For my own testing to prove I had added the drivers correctly I booted off a base boot.wim with no drivers injected. There was no IP when running IPCONFIG. End of setupact.log shows
2011-04-13 09:09:20, Info WDS Spent 936ms installing network components
2011-04-13 09:09:23, Info WDS Spent 2355ms installing network drivers
2011-04-13 09:09:23, Error [0x0b003e] WDS QueryAdapterStatus: no adapters found.[gle=0x000000cb]
2011-04-13 09:09:23, Info WDS Spent 0ms confirming network initialization; status 0x80004005
2011-04-13 09:09:23, Info WDS WaitForNetworkToInitialize failed; ignoring error
2011-04-13 09:09:23, Info WDS GetNetworkingInfo: WpeNetworkStatus returned [0x0]. Flags set:
2011-04-13 09:09:23, Error [0x0b003f] WDS StartNetworking: Failed to start networking. Error code [0x800704C6].[gle=0x000000cb]
2011-04-13 09:09:23, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [WdsClient: An error occurred while starting networking: a matching network card driver was not found in this image. Please have your Administrator add the network driver for this machine to the Windows PE image on the Windows Deployment Services server.]
Next, I injected the latest Broadcom drivers into another base boot.wim file. IPCONFIG shows an IP address. End of setupact.log shows
2011-04-13 09:17:38, Info WDS Spent 936ms installing network components
2011-04-13 09:17:40, Info WDS Spent 2309ms installing network drivers
2011-04-13 09:17:50, Info WDS QueryAdapterStatus: no operational adapters found.
2011-04-13 09:17:50, Info WDS Spent 10140ms confirming network initialization; status 0x80004005
2011-04-13 09:17:50, Info WDS WaitForNetworkToInitialize failed; ignoring error
2011-04-13 09:17:50, Info WDS GetNetworkingInfo: WpeNetworkStatus returned [0x0]. Flags set:
2011-04-13 09:17:50, Error [0x0b003f] WDS StartNetworking: Failed to start networking. Error code [0x800704C6].[gle=0x000000cb]
2011-04-13 09:17:50, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [WdsClient: An error occurred while obtaining an IP address from the DHCP server. Please check to ensure that there is an operational DHCP server on this network segment.]
Windows IP Configuration
Host Name . . . . . . . . . . . . : minint-2eljtfg
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : correct.co.uk
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : correct.co.uk
Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
Physical Address. . . . . . . . . : 78-2B-CB-93-11-F8
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::a098:117a:a1fd:a4b9%2(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.78(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, April 13, 2011 9:17:57 AM
Lease Expires . . . . . . . . . . : Thursday, April 21, 2011 9:17:57 AM
Default Gateway . . . . . . . . . : 10.0.0.66
DHCP Server . . . . . . . . . . . : 10.0.0.21
DHCPv6 IAID . . . . . . . . . . . : 41429963
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-37-93-19-78-2B-CB-93-99-F8
DNS Servers . . . . . . . . . . . : 10.0.0.21
10.0.0.6
NetBIOS over Tcpip. . . . . . . . : Enabled
See the difference? 'no adapters found' vs 'no operational adapters found'.
However this time I did notice that when I typed IPCONFIG straight away after the error message poped up it only showed an IPV6 address. Then when I tried 1 second later it had picked up the DHCP address.
Seems that the network card takes some time to initialize and the deployment setup is too impatient and falls over?

Mdt 2012 + WDS service on the same server. DHCP question

Hi,
I am using MDT 2012 on Server 2008.
Boot images are placed on 6 years old WDS server running on 2003.
I need to remove WDS server (2003).
Cannot find exact instructions for enabling PXE for MDT2012.
I don't need introduction guides. But clear few lines of instructions.
From quickly checking web I understand that I need:
1. install WDS services on the same MDT2012 server 2008.
2. import Lite Touch boot images from Deployment Share
The only point I am missing is DHCP question. In Microsoft prerequisites for WDS services, DHCP should be present on the same server were WDS is...
I watched one video on web and the guy just installs WDS on the MDT server and not mentioning DHCP at all.
Sure that there is DHCP server serving multiple subnets on the network.
My confusion about DHCP on WDS prerequisite comes from not having DHCP services installed on old WDS 2003 machine.
So why it is required on WDS service in server 2008/2012?
Can somebody confirm that DCHP must exist on the same server were MDT and WDS services are enabled.
And is it a valid option to have all 3 on one Server machine if DHCP is really needed for enabling PXE in MDT environment?
I saw the info about ports 67 (should be disabled) and 60 for PXE enabled.
Will appreciate DHCP part explanation and how to...
Thanks.
"When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

RL69,
in my environment DHCP serves multiple subnets. For now no need to serve client machines on different subnets. The Deployments will be done on subnet were MDT resides. If necessary PXE relay could be enabled on Core switch (or where necessary).
So if I understand correctly for a scenario above all what I need to do for PXE enabled MDT is:
to add WDS role/service on the same MDT server and import boot images.
Right?
Will do it right after your confirmation :)
"When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

WDS, DHCP and WSUS on same server, Virtuals find WDS and start up process, Physicals get PXE-X55 error.

I have a Windows 2012 R2 server that has the WSUS, WDS and DHCP roles installed. I also have a SCVMM (Win2012R2) server on different machine and it has been connected to the WDS server
Followed many different guides on the internet to configure the WDS server but if I have option 60 configured the virtual machines will find and do a PXE boot successfully, but the physical systems will fail with a E55 error.
I take out option 60 and both fail.
Did I miss a niggly bit some where?

Have you tried this (from article):
Custom-made Option 60 – String – PXEClient
Predefined Option 66 – IP or Hostname of the WDS Server (in our case 10.150.150.1)
Predefined Option 67 – boot\x86\wdsnbp.com
and this in WDS properties:
and
Many people remark this as solution:
WDSUTIL /Delete-AutoAddDevices /DeviceType:ApprovedDevices

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.

SCCM 2012 R2, DHCP and WDS and PXE same server

hi
I am using DHCP and PXE on same server and getting error PXE-E55: proxyDHCP did not reply to request on port 4011

HI,
To get WDS and DHCP to work on the same machine, you need to configure WDS to share the same server as DHCP, here is how it is done.
You must have a functioning DHCP server with an active scope. WDS will utilize PXE which requires a DHCP server.
Whether you plan to co-host WDS and DHCP on the same server or use two different servers you must configure WDS to listen on a specific port. DHCP and WDS both require port number 67. If you have co-hosted WDS and DHCP you can move DHCP or the PXE site role
to a separate server or use the procedure below to configure the WDS server to listen on a different port.
Modify the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE
Set the registry value to:
UseDHCPPorts = 0
For the new configuration to take effect run the following command on the co-located DHCP and WDS server:
WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes
https://technet.microsoft.com/en-us/library/bb680753.aspx
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

WDS ignores DHCP

Similar Messages

Maybe you are looking for