Server 2008 WDS not working on new vlan

[Rav-Singh]

Hello All,

 

We recently split up our network up into 7 separate vlans due to a shortage of ip addresses. A new core switch (HP E5406ZL ) has been installed which seems to work effectively however I cannot seem to get the WDS (Server 2008 R2) working again.

 

The subnets are as follows -

10.122.192.---

10.122.193.---

10.122.194.---

10.122.195.---

10.122.196.---

10.122.197.---

10.122.198.---

 

All the servers (DNS,PDC,WDS etc) are on the same subnet (10.122.196.) Can any one help?

Edited May 15, 2012 by Rav-Singh

[ChrisH]

Are the basics working, can your clients ping the WDS server and vice versa? Have you changed the IP address and not updated group policy?

[andyrite]

What on the WDS can't you get working? PXE?

[themightymrp]

On your DHCP server, set the following 2 Server Options (not scope options):

 

Option 66 - set the IP address of the WDS server

Option 67 - boot\x86\wdsnbp.com

 

I had the same problem when I changed over in February

[Rav-Singh]

Thank you for getting back to me so quick gents, I can ping from the client machines to the WDS and vice versa. The clients (PC's or laptops) do not see the WDS on boot up, it times out and the following message appears -

 

' PXE-53: No boot filename received

PXE-MOF: Exiting HP PXE ROM.'

 

Thanks again

 

Rav-Singh

[themightymrp]

Have you tried what I put?

[maark]

you need to put ip helper-address for wds server in each vlan as well as your dhcp address

[Rav-Singh]

It works !!!!!!! Many thanks fella !!!

[Rav-Singh]

Have you tried what I put?

Yep it works now just deploying an image as we speak Thanks again !!!

 

 

Rav-Singh

[themightymrp]

Excellent news

[Rav-Singh]

WDS PS setting.docxE540621-J8697A.txtHello every body !

 

After having successfully used the WDS server to image different machines\laptops on the network all last week, I shut it down on Friday. I powered it up today and found the client machines had the same error message appear -

 

"PXE-53: No boot filename received

PXE-MOF: Exiting HP PXE ROM."

 

I am unable to connect to machines I imaged on Friday but am able to ping the WDS server from them.

 

To get it working the first time I followed the instructions given by themightyMrP (Option 66 - set the IP address of the WDS server,as can be seen in word doc attached) and it worked a treat. As nothing has changed I dont understand why it has stoped working.

 

We are using a HP E530621 (J8697A) as a core switch ip 10.122.196.1, the WDS is on 10.122.196.59, the DNS (10.122.196.55) and DHCP (10.122.196.43) are all in the same (VLAN)subnet.

 

Maark suggested that I 'need to put ip helper-address for wds server in each vlan as well as your dhcp address' but as the WDS server was working I thought this step was not required. However today when I checked the core switch configuration report, this command is already been used for DHCP (please see attached swicth configuration report if I dont make sense)

 

Please help !!!

 

Many thanks for all your advice and support.

 

 

Rav Singh

[Rav-Singh]

[ATTACH]14119[/ATTACH][ATTACH]14120[/ATTACH]Hello every body !

 

After having successfully used the WDS server to image different machines\laptops on the network all last week, I shut it down on Friday. I powered it up today and found the client machines had the same error message appear -

 

"PXE-53: No boot filename received

PXE-MOF: Exiting HP PXE ROM."

 

I am unable to connect to machines I imaged on Friday but am able to ping the WDS server from them.

 

To get it working the first time I followed the instructions given by themightyMrP (Option 66 - set the IP address of the WDS server,as can be seen in word doc attached) and it worked a treat. As nothing has changed I dont understand why it has stoped working.

 

We are using a HP E530621 (J8697A) as a core switch ip 10.122.196.1, the WDS is on 10.122.196.59, the DNS (10.122.196.55) and DHCP (10.122.196.43) are all in the same (VLAN)subnet.

 

Maark suggested that I 'need to put ip helper-address for wds server in each vlan as well as your dhcp address' but as the WDS server was working I thought this step was not required. However today when I checked the core switch configuration report, this command is already been used for DHCP (please see attached swicth configuration report if I dont make sense)

 

Please help !!!

 

Many thanks for all your advice and support.

 

 

Rav Singh

 

Happy times !!!! After conducting some switch jiggery pokery I have found the cause of the problem. A port on the access layer swicth,used by the client machine has become fautly (may be someting to do with the lightening strike last year).

 

Many Thanks once again !!

 

Rav Singh

[newpersn]

Sorry to dig this topic up from almost a year ago.

 

But this worked for us. But now we are having problems. We boot up and select our optation to install an os from an image.

 

Downloads and gets stuck on "setup is starting"

 

We get an error with optaining an ip address

 

 

Any ideas?

[maark]

have you run out of addresses? - right click scope on dhcp server and select display statistics to see if you have any left to allocate

[newpersn]

Nope ive not ran out of address. I have a feeling its a bad driver as other drivers work fine thoughout the school. I will replace the driver and try again.

[themightymrp]

I'd say that was a network card driver, the initial IP address from boot won't care what card is there as long as it supports PXE. At this GUI stage though it will need a windows driver available for that model of card.

[Darylrese]

Where do I find the server options please?

 

We have added a new unauthorised VLAN and now cant build machines with PXE Boot.

 

Many thanks