Thursday, March 11, 2010
Deployment Forum HomeDeployment Forum ArticlesDeployment Forum Download LibraryDeployment Forum Member BlogsDeployment Forum Community Forums
Member Login
StandardLiveID


Register
Forgot Password ?



Guests can view and read messages in the community forums, but you must register and log in to Deployment Forum before you can post messages. Click Register at the top of this page. Before posting messages, please read the forum guidelines at the bottom of this page.

Subject: WDS Client Issue
Prev Next
You are not authorized to post a reply.

AuthorMessages
Kev SUser is Offline

Posts:2

Send Message
01/21/2010 11:02 AM  

Hi All

I have had a problem with deploying an image to one particular model of PC at work. I have stepped closer to solving the issue but I have once again hit a road block.

I will start with the background of the problem so you know what I have already tried and where I am up to in this issue.

A few months ago we needed to re-image the entire organisation's computers due to, upgrade, virus and performance reasons. I have set up a WDS server on a Windows Server 2003 SP2 machine. This setup worked on all the computers from our supplier manufactured 2005 - 2008. Which have been PXE version 2.0.

However this year's delivery are using Gigabyte G31M-ES2L motherboards. The info for the built in Ethernet card is as follows (some of which is shortened):

Intel UNDI PXE-2.1 (build 82)

Covered Patients... etc

Realtek PCI Express Gigabit Ethernet Controller Series v2.25 (090106)

 

To begin with the computer would not detect the WDS server at the stage of searching for the IP address at PXE BIOS level. After a conversation with our supplier they suggested using Options 66 & 67 on our DHCP server. So, I configured the options as follows:

Option 66 - (WDS Server IP address)

Option 67 - boot\x86\pxeboot.com

 

When booting the machine into PXE the client then discovered the WDS sever and would load the boot image. Once in the boot image an error message occured:

WDSClient: An error occurred while obtaining an IP Address from the DHCP Server

 

After investigating using the SHIFT+F10 shortcut to try and renew the ip address, I found the ethernet controller would not appear after entering the command. I took the boot image and used WAIK to inject the correct Ethernet Drivers to this image.

I have now added this boot image to the WDS server and booted the client from it. I now recieve this error message:

WDSClient: There was a problem initialising WDS Mode.

 

I also have enable Spanning Tree on all of our backbone and edge switches as this was also causing the DHCP request to fail.

I am using an editted boot image from a Windows Vista CD

I have tried adding a delay to the PXE response (currently on 0)

 

I cannot figure out why this is still showing an error.

Could anyone assist with this issue, either if they have extensive knowledge of WDS or have solved this problem by encountering it themselves?

If you need anymore information to assist, please ask. Any help will be greatly appreciated.

Hugo RUser is Offline

Posts:1

Send Message
02/07/2010 5:55 AM  
Hi,

I've a similar problem to Kev S with one interesting difference. I've been doing some lab testing on a machine and consequently Windows has been installed on the same hardware any number of times. Each time the OS is changed its being installed by a Windows 2008 R2 WDS server. I've been happily installing Vista x64 Ult and Win7 x64 Ult several times over the weekend.

For some reason Vista installs have just stopped working. The machine PXE Boots, I select the boot image, which loads no problem but then get the message WDSClient: An Error occurred while obtaining an IP Address from the DHCP Server Win7 still works.


Nothing has changed, same hardware, same WDS Server, same DHCP, switches, cables etc. Using the same cable as the test machine on a laptop it all works.


Any help would be greatly appreciated.
You are not authorized to post a reply.



ActiveForums 3.7
Forum Policies
Minimize

These forums are a user-supported community for IT professionals to exchange deployment tips, solutions, and techniques. For the benefit of all Deployment Forum members, please observe the following guidelines when posting to these forums:

  • We reserve the right to remove any message. Our moderators will remove all messages that are not respectful or productive. Profanity, racism, prejudice, and flaming are not tolerated.
  • Do not advertise products or services. Our moderators will remove all advertisements or service announcements. Product and service recommendations from active Deployment Forum members are encouraged, however.
  • Make sure your question isn't already answered. Before posting questions, search the forums. After ensuring that your questions are unique, post them to the most appropriate forum. This will help reduce noise in the forums.
  • Help make the most of each thread. Do not post unrelated messages to a thread. Also, if you've resolved a question outside of these forums, please share the solution with other members by posting it back to the thread.
  • Do not share confidential information. Confidential information includes product keys and addresses. Our moderators will edit any message containing confidential information, so double-check messages and their attachments before posting them.
  • Post messages using only the English language. For the benefit of all Deployment Forum members, please post your messages using the English language.

We hope that you enjoy using this community. Please submit your comments and feedback on the Comments and Feedback page or post them to the Comments, Feedback forum.



Privacy Statement  |  Terms Of Use
© 2007 Jerry Honeycutt