tails71
asked on
PXE-E53 No boot filename received trying on WDS Windows 2008 R2 x64
I am trying to set up PXE boot at our site. I get the famous "PXE-E53 No boot filename received" message with trying to PXE boot from a laptop.
Here's the steps I've got so far:
1) On a Windows 2008 R2 x64 server:
a) Installed SolarWinds TFTP Server. Configured to point to directory with *.wim files
b) Installed WDS Service.
2) DHCP is running from Cisco switch.
3) There are three different VLANS involved:
Switch - VLAN 10, 10.38.36.*)
Servers - VLAN 30, 10.38.38.*
Workstations - VLAN 201, 10.38.46.*
4) DHCP setup for workstation VLAN 201:
ip dhcp pool vlan_201
network 10.38.46.0 255.255.255.0
next-server 10.38.38.16 (IP of my TFTP server)
default-router 10.38.46.1
dns-server 10.38.38.17 10.38.0.134
5) One boot image of Windows 7 32-bit (all workstations are running it) loaded in WDS.
Does anyone have ideas on my next steps to diagnose the problem?
Here's the steps I've got so far:
1) On a Windows 2008 R2 x64 server:
a) Installed SolarWinds TFTP Server. Configured to point to directory with *.wim files
b) Installed WDS Service.
2) DHCP is running from Cisco switch.
3) There are three different VLANS involved:
Switch - VLAN 10, 10.38.36.*)
Servers - VLAN 30, 10.38.38.*
Workstations - VLAN 201, 10.38.46.*
4) DHCP setup for workstation VLAN 201:
ip dhcp pool vlan_201
network 10.38.46.0 255.255.255.0
next-server 10.38.38.16 (IP of my TFTP server)
default-router 10.38.46.1
dns-server 10.38.38.17 10.38.0.134
5) One boot image of Windows 7 32-bit (all workstations are running it) loaded in WDS.
Does anyone have ideas on my next steps to diagnose the problem?
did you configure the bootfile name in dhcp?
ASKER
No the only thing I added in DHCP was the TFTP server IP address.
I believe that I had the same issue before and the problem was that the bootfile name was not specified. It is option 67 for dhcp.
ASKER
Okay that helped. I added the bootfile option on my cisco switch (dhcp server):
ip dhcp pool vlan_201
network 10.38.46.0 255.255.255.0
bootfile \build\windows7-32bit\sour
next-server 10.38.38.16
default-router 10.38.46.1
dns-server 10.38.38.17 10.38.0.134
domain-name dwight.k12.il.us
lease 0 8
I'm now getting new errors:
PXE-T04: Access violation
PXE-E36: Error recieved from TFTP server
My TFTP server (2008 R2) has the following set up:
The BUILD share (\\{servername}\BUILD) is not on the C: drive. I don't know if that matters. So the boot file is at \\{servername}\build\windo
I have tried about every available path syntax for bootfile. Any ideas?
ip dhcp pool vlan_201
network 10.38.46.0 255.255.255.0
bootfile \build\windows7-32bit\sour
next-server 10.38.38.16
default-router 10.38.46.1
dns-server 10.38.38.17 10.38.0.134
domain-name dwight.k12.il.us
lease 0 8
I'm now getting new errors:
PXE-T04: Access violation
PXE-E36: Error recieved from TFTP server
My TFTP server (2008 R2) has the following set up:
The BUILD share (\\{servername}\BUILD) is not on the C: drive. I don't know if that matters. So the boot file is at \\{servername}\build\windo
I have tried about every available path syntax for bootfile. Any ideas?
I am not to familiar with PXE, but I believe that the file format for TFTP uses forward slashes? Maybe try bootfile /build/windows7-32bit/sour
??
??
ASKER
Here is more info:
I have identified my root path for my TFTP server as D:\BUILD in my TFTP config on my 2008 R2 server. That directory is also shared as \\{servername}\BUILD.
I have tried forward slashes, backward slashes, double slashes, adding the BUILD directory to the path, removing the BUILD directory to the path.
I have identified my root path for my TFTP server as D:\BUILD in my TFTP config on my 2008 R2 server. That directory is also shared as \\{servername}\BUILD.
I have tried forward slashes, backward slashes, double slashes, adding the BUILD directory to the path, removing the BUILD directory to the path.
I would think that /windows7-32bit/sources/bo
ASKER
when I just use a TFTP client to copy a single file, I get an access violation
I would look at the permissions of the tftp server and also the permissions of the file itself in windows. The tftp service credentials should have access to the directories and boot file.
ASKER
The TFTP service is running under an id in the DOMAIN ADMINS group (for now). I have checked the folder, and the DOMAIN ADMIN group has full rights for the folder. I have restarted the service, and am still getting the error. Any thoughts?
ASKER
I have finally been able to get back to this issue. I discovered a couple of things after some trial and error.
1) Turned the Firewall off on the server.
2) When I stopped the Windows Deployment Service (WDS), I was able to open a command prompt, and use the TFTP client to get a file from my TFTP server.
3) When I restarted WDS, I get the access violation again.
Our DHCP is currently set up on our core switch (Cisco), NOT through a Windows Server.
1) Turned the Firewall off on the server.
2) When I stopped the Windows Deployment Service (WDS), I was able to open a command prompt, and use the TFTP client to get a file from my TFTP server.
3) When I restarted WDS, I get the access violation again.
Our DHCP is currently set up on our core switch (Cisco), NOT through a Windows Server.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Things became much simpler to diagnose once the DHCP service was moved from the switch to a Windows server.