@x23piracy Nice work. Changing option 66 from the hostname to the IP address did trick. Clients are booting fine now.

@x23piracy I will. Thank you.

@x23piracy Nice work. Changing option 66 from the hostname to the IP address did trick. Clients are booting fine now.

@x23piracy Is this what you are referring too? This is screenshot of the server’s DHCP Manager. DHCP Manager.

@Jaymes-Driver I would prefer to get it working. The only thing that has changed is the IP address of the DHCP server. It has to be a simple fix. I’m not sure where to make that change. Is it possible to view the contents of the pxelinux.0 file? I do not see a way to open it.

@x23piracy

• Windows DHCP Server 2012 R2.

• Using pxelinux.0 file.

• Error:
  PXE-E32 TFTP open timeout
  PXE-M0F: Exiting Intel Boot Agent

@x23piracy Yes. Those are configured in DHCP. Really nothing has changed except the DHCP server name and IP address.

Server

• FOG Version: 0.32
• OS: Ubuntu 10.04 LTS

Client

• Service Version: 0.1
• OS: Windows 7

Description

Clients are getting stuck upon PXE boot at TFTP (open timeout). I configured a new DHCP server yesterday by exporting DHCP settings from the old server and importing DHCP settings to the new server. The scope options haven’t changed. Is there a setting on the FOG server that could be pointing to the old server? …maybe the pxelinux.0 file or something else? Or could there be a TFTP setting on a Cisco switch pointing to the old server? I set FOG up 7 years ago and use it all the time, but I a bit “foggy” regarding the configuration. Pun intended : - ) It’s been too long to remember the configuration.