Login to participate
Endpoint Management & Virtualization BlogsRSS

Windows 2008 X64 + Windows DHCP Server + PXE Server Workaround

Nelo's picture

The scenario is a remote PXE server with the following configuration:

Windows 2008 X64 + Windows DHCP server + PXE Server

Clients do not PXE boot without making a change in the PXE Configuration Utility.

Clients PXE booting receive an error message regarding port 4011 and the PXE booting process stops.

The following are the steps to address the issue:

  1. Launch PXE Configuration Utility from the DS Console or from the Start Menu.
  2. Select the PXE Server Tab.
  3. In the DHCP Server Discovery section select "No DHCP server installed on PXE server (Use DHCP port)".
  4. Click Save to commit the changes. Wait until the progress bar disappears.
  5. Click OK to close PXE Configuration Utility.
Note: This only Applies to DS 6.9 SP1.
Brandon Vincent's picture

@Nelo The problem is that

@Nelo

The problem is that this does not allow the PXE client to automatically boot into preconfigured jobs and requires the user to key F8 at hte DHCP menu

Not very helpful when you have a jobs expecting the client to auto boot into Linux or WinPE or when you are trying to provide a hands free imaging process

I would rather Symantec resolves this matter so that PXE binds on Port 4011 within DHCP

Maciej Pienczyn's picture

I also have this problem.

I also have this problem. My one of servers has configuration:
Windows 2008 X64 + Windows DHCP Server + PXE Server
+ Active Directory role installed.

DS version 6.9 SP3

I've made steps You mentioned above, but still no success. I'm also counting on Symantec employees to resolve this problem.

Below is my LOG from PXE Server (PxeLog_Server.Txt):

Enter: SetupDHCP(...)
E [13:45:55 09/08] (2436): SetupDHCP: Auto Detect, configure option 60.
E [13:45:55 09/08] (2436): SetupDHCP: DHCP Server found.
E [13:45:55 09/08] (2436): SetupDHCP: configure standard server.
E [13:45:55 09/08] (2436): Error cannot modify DHCP Server Global Options to support PXE ClassID

Maciej Pienczyn's picture

Problem SOLVED. Server has

Problem SOLVED.

Server has two interfaces, from two subnetworks.
DHCP offers were also on this two interfaces.
One interface DOWN and problem has gone :)

Brandon Vincent's picture

Hi Maciej Thanks for the

Hi Maciej

Thanks for the response however I 've only ever had one interface on my server.

To date Symantec have not updated the KB article which describes this as a fault
https://kb.altiris.com/display/1n/kb/article.asp?a...
https://kb.altiris.com/display/1n/kb/article.asp?a...

Which means jobs do not automatically select the correct PXE option...

Brandon Vincent's picture

Just an update on this

Just an update on this post.

DS 6.9 SP3 has now resolved this issue and Auto PXE selection now works

Cheers