[mdt] PXE Boot Issue

[GRitchie]

Hello,

So, I've posted about this before however I'm still having problems with it.

 

Basically, I have MDT set up through WDS for imaging machines.

Practically every machine in the network will image with no issues aside from these 'ERGO AS1' machines

 

This is what appears on screen;

 

Intel UNDI, PXE-2.1 (build 082)
Copyright (C) 1997-200 Intel Corporation

For Realtek RTL8111B/8111C Gigabit Ethernet Controller v2.10 (071105(

CLIENT MAC ADDR: 00 90 F5 8C 21 E6 GUID: FFFFFFFF-0C0C-0000-0000-000000000000
PXE-E51: No DHCP or proxyDHCP offers were received.

PXE-M0F: Exiting PXE ROM.

 

Why is this? Is there an easy fix?

I have to image an entire suite like this and they all have the same issue, if I can't get it to work, I'll have to use the Windows 7 disc!

 

Please help!

[themightymrp]

I can tell you what it isn't - it's not because you are missing a driver from the MDT database. That wouldn't kick in until after it starts to pull things down from the server.

 

At the point you are showing it should be using generic drivers to obtain an IP address. The fact that it isn't suggests an error with your VLAN or switch configuration. Can you plug a different model of machine into the same data socket and see if that will boot?

[themightymrp]

Or...... could be this:

 

PXE-E51 "No DHCP or DHCP Proxy Offers received" er... - HP Enterprise Business Community

 

It could be something as simple as what it mentions

[GRitchie]

I can tell you what it isn't - it's not because you are missing a driver from the MDT database. That wouldn't kick in until after it starts to pull things down from the server.

 

At the point you are showing it should be using generic drivers to obtain an IP address. The fact that it isn't suggests an error with your VLAN or switch configuration. Can you plug a different model of machine into the same data socket and see if that will boot?

 

No - the port is fine, I've JUST imaged a Fujitsu with the same cable in the same port.

We don't VLAN, but I'd presume the switch is fine if the Fujitsu worked?

[themightymrp]

Have you read the info on that link? Apparently some network adapters have a shorter timeout than others and if your switch has spanning tree enabled you might have to enable portfast or the equivalent to make the link active instantly.

[GRitchie]

Have you read the info on that link? Apparently some network adapters have a shorter timeout than others and if your switch has spanning tree enabled you might have to enable portfast or the equivalent to make the link active instantly.

 

Hello, yes - but it doesn't seem to be one of those issues.

Also, if one machine would image, why would the next one not - clearly not an incorrect switch configuration.

How would you adjust the network adapter? And/or do I need to upgrade the PXE version?

[themightymrp]

Hi. It wouldn't be a change to the network adapter or the PXE version (which I don't think you can do anyway).

 

From what you said in the opening post, you are only getting the fault with this one model of machine - is that correct? If so, the reason it works fine for one machine and not another is down to the model of the machine. It is these ERGO AS1's that are being peculiar. Whatever it is about these ERGO's and their network adapter must have a short timeout.

 

If you check the config of the switch that these data sockets go back to you should be able to find out if Spanning Tree is enabled on it. If it is, then you will need to enable PortFast (or the equivalent) on the ports that you will be PXE booting these ERGO's on. This will stop the switch running the spanning tree calculation (to prevent network loops) and will allow the network connection to be enabled quicker, therefore sorting out the short timeout issue.

 

If you don't have spanning tree then I'm not sure??

[themightymrp]

Did you get anywhere with this?

[GRitchie]

Did you get anywhere with this?

 

Unfortunately not no! :-/

[themightymrp]

Did you check the spanning tree mode on the switch?

[GRitchie]

Did you check the spanning tree mode on the switch?

 

No - I didn't. I'm not too sure how to, also, would that matter if other machines have worked on the same switch?

[themightymrp]

Other machines of a different model probably wouldn't be affected by this issue. It seems to be just these things.

 

Do you know what make/model of switch they connect to?

[sted]

No - I didn't. I'm not too sure how to, also, would that matter if other machines have worked on the same switch?

 

diferent network cards have different tolerances/issues.

 

A while back i know but at a school had some dells upgraded the switch they were conected to and they wouldnt get gpo until you forced the network card to any mode in windows (so 10mb half duplex workde best) auto took so long it gave up looking for a network. After fiddling updated the switch firmware and it worked as its supposed to with cards left on auto i think someone else here had the same issue and updated the cards firmware that also fixed it

 

might be worth checking for bios updates for the pcs or just on 1 get a 8 port switch and plug it through that see if that eases the problem it might be something as simple as its not getting a reply as fast as it needs from the upstream switch (or if they are laptops try moving it and using a different brand/model switch see what happens)

[GRitchie]

Other machines of a different model probably wouldn't be affected by this issue. It seems to be just these things.

 

Do you know what make/model of switch they connect to?

 

Hm, I'm not 100% but I'm presuming it's a Netgear switch. Most are here!

[themightymrp]

@sted makes a good point about possibly updating the BIOS or trying those machines in a different model of switch. Could you take one PC to a part of the school which uses something else and see if they PXE boot?

 

I would suggest a firmware update on the switch but that might be a bit extreme. Are you able to connect to the switches for management? i.e. via a web interface?

[GRitchie]

I've tried in different locations; still no luck.

There seems to be no BIOS upgrades available for these machines, even on the official website!

 

Yes, a switch firmware upgrade won't be possible.

[chilbs]

Have you tried pausing the PXE process just when it starts to try to find a DHCP, leave it about 10 seconds then unpause. Has worked for me in the past.

 

Chilbs

[sted]

I've tried in different locations; still no luck.

There seems to be no BIOS upgrades available for these machines, even on the official website!

 

Yes, a switch firmware upgrade won't be possible.

 

try plugging in the crummiest 8/4 port switch you have in as well so wall socket to 8 port to pc sometimes a poor switch helps because it cant even try to do anything clever

[daveyboy]

Are these machines Clevo A9100's ?.......

[GRitchie]

Are these machines Clevo A9100's ?.......

 

No, they're ERGO AS 1's.

[daveyboy]

Are they these....

 

http://www.ergo.co.uk/Products/All-in-One-PC/Documents/Ergo_As1_lowres.pdf

[daveyboy]

If they are are, then........

 

CLEVO - Download

 

Model A9100/A9105 - you'll find all the manuals there too. If you want a service manual - PM me.

[IAMCloud_Curt]

Try this in your WDS Server Properties

 

Pasteboard — Uploaded Image

[GRitchie]

If they are are, then........

 

CLEVO - Download

 

Model A9100/A9105 - you'll find all the manuals there too. If you want a service manual - PM me.

 

Only just got these messages, sorry, yes they are those AS1's!

[GRitchie]

Try this in your WDS Server Properties

 

Pasteboard — Uploaded Image

 

Yes - the settings are like that already!