Solved

PXE-E53 No boot filename received trying on WDS Windows 2008 R2 x64

Posted on 2012-04-12
13
2,249 Views
Last Modified: 2012-07-15
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?
0
Comment
Question by:tails71
  • 8
  • 5
13 Comments
 
LVL 12

Expert Comment

by:ryan80
ID: 37838943
did you configure the bootfile name in dhcp?
0
 

Author Comment

by:tails71
ID: 37838993
No the only thing I added in DHCP was the TFTP server IP address.
0
 
LVL 12

Expert Comment

by:ryan80
ID: 37839004
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.
0
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 

Author Comment

by:tails71
ID: 37842912
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\sources\boot.wim
   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\windows7-32bit\sources\boot.wim

I have tried about every available path syntax for bootfile.  Any ideas?
0
 
LVL 12

Expert Comment

by:ryan80
ID: 37842923
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/sources/boot.wim
??
0
 

Author Comment

by:tails71
ID: 37843058
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.
0
 
LVL 12

Expert Comment

by:ryan80
ID: 37843445
I would think that /windows7-32bit/sources/boot.wim would be what you want and that you will need to allow anonymous access to the file. you could test it with a tftp client to see if you can access the file.
0
 

Author Comment

by:tails71
ID: 37843660
when I just use a TFTP client to copy a single file, I get an access violation
0
 
LVL 12

Expert Comment

by:ryan80
ID: 37843695
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.
0
 

Author Comment

by:tails71
ID: 37844767
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?
0
 

Author Comment

by:tails71
ID: 38071981
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.
0
 

Accepted Solution

by:
tails71 earned 0 total points
ID: 38172701
Finally got WDS to work.  Successfully deploying machines.  Here's what I ended up doing:

1) Moved DHCP scopes from core switch to our Windows 2008 DC.  (included options 66 and 67 for boot file name and TFTP path).

2) On Cisco core switch, had to edit our VLANs as follows:
          ip helper-address 10.38.38.17   (our DHCP server)
          ip helper-address 10.38.38.27   (our TFTP server)

I had to put both entries in, even though I added options 66 & 67 in the DHCP scope.
I had to make sure that the DHCP server was listed first.  If the TFTP server was listed first, I got inconsistent results.
0
 

Author Closing Comment

by:tails71
ID: 38187158
Things became much simpler to diagnose once the DHCP service was moved from the switch to a Windows server.
0

Featured Post

The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Converting TV to Network (Muli-User) Web front. 8 63
GPO and server 2008 R2 7 32
Windows Folder Permissions 9 42
SBS2008 and windows updates 2 7
We recently endured a series of broadcast storms that caused our ISP to shut us down for brief periods of time. After going through a multitude of tests, we determined that the issue was related to Intel NIC drivers on some new HP desktop computers …
An article on effective troubleshooting
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

816 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now