Jump to content

Recommended Posts

Posted

I've been trying to set up WDS

 

client PC's cant find DHCP but I setup option 60 66 and 67 in DHCP which is on a different server from WDS

 

have I missed somthing?

 

I've just tried with 2 other systems and the same, no dhcp found. dhcp works fine in windows.

 

thanks

 

Rageriot

Posted
if they are on the same network then remove the option 60/66/67 they arnt needed they are only required if you have to cross subnets or its installed on the dhcp server i believe
Posted
I've been trying to set up WDS

 

client PC's cant find DHCP but I setup option 60 66 and 67 in DHCP which is on a different server from WDS

 

have I missed somthing?

 

I've just tried with 2 other systems and the same, no dhcp found. dhcp works fine in windows.

 

thanks

 

Rageriot

 

At which point cant they find the DHCP server?

 

Can you get the machines to download your deployment image or will then not find the DHCP server at the PXE boot screen?

Posted
At which point cant they find the DHCP server?

 

Can you get the machines to download your deployment image or will then not find the DHCP server at the PXE boot screen?

they dont find DHCP

 

if they are on the same network then remove the option 60/66/67 they arnt needed they are only required if you have to cross subnets or its installed on the dhcp server i believe

I thought thats a requirement fo PXE to work

 

I've tried 3 different models

Asus and VYes to test.

 

The PCs I wanted to re image are in the IT suite.

Posted
thats what ive just fixed here i was moving wds from the main server to a server thats basically a glorified nas box (but as it has the capacity to run wsus/wds/mdt takes a load of the main server and is 08r2) and it would get an ip lease with the old server but not the new one, as soon as i removed options 60/66/67 it went straight to the new server (after uninstalling wds of older server) so dhcp just has options 3/6/15/44/46 with anything against them and wds now works (currently transfering mdt)
Posted (edited)

ok I've just removed those options ( Unticked them)

and it stil didnt work.

 

heres the following setup

 

Server 1: Intel P4 3.2Ghz 3Gb Ram

DHCP

DNS - Seconday

AD

Print Management

 

Server 2: Intel Xeon Quad 2.4Gz 4GB Ram

DNS - Primary

AD

ESET ERSA (antivirus server)

WDS

Most of schools network shares

 

just options 3 5 & 6 set on DHCP

Edited by RageRiot
Posted

ok it suddenly started working to a point.

 

I'v got tt saying

 

PXE-E53: no boot filename received

 

is this refering to a boot file in WDS ?

 

in the guide I have been given to setup WDS is states to check

'do not listen on port 67'

'configure DHCP option 60 to indicate that this server is a PXE server'

 

Obiovusly that latter option is releative if WDS was on the same Server as DHCP which is isnt but the first check box always becomes unchecked.

Posted
I've been trying to set up WDS

 

client PC's cant find DHCP but I setup option 60 66 and 67 in DHCP which is on a different server from WDS

 

have I missed somthing?

 

I've just tried with 2 other systems and the same, no dhcp found. dhcp works fine in windows.

 

thanks

 

Rageriot

 

I have the ssame setup , but i'm pretty sure you DONT set the DHCP options, unless DHCP and WDS are on the same server

I cannot check without killing SCCM....

Posted

Ok heres an update.

 

It started working on 2 other machines.

 

But the whole point of this setup was to re image the itsuite machines and these fail to boot on PXE every time.

 

They claim a dhcp cannot be found but it clearly works on the other 2 machines I tried.

Posted
WDS and DHCP should be on the same server so it takes DHCP in a WDS deployment.

shouldnt matter. Most of mine are running on the dhcp server (but mainly as most schools i support have 1 server) school i was at today now have 3 and it seems to run quite happily from a member server and in our office its on a pc running 08r2 again not the dhcp server and that works fine. I think its supposed NOT to be run on the same pc.

  • Thanks 1
Posted

as for the machines I wanted to image. since PXE on them doesnt work can they be flashed? or is PXE portion usually Read only.

 

I'm guessing like BIOS they can be flashed, just a question of weather the manufacture suply an update.

 

reason I figure they are broke is because 2 completly different systems ( very old and Very new) booted eventually despite earlyer problems.

 

just unfortuate the systems that boot with it are brand new and wont need imaging for a while.

 

Thanks goes out to all the help so far !

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...