Ok, excuse my ignorance...*blush*
PXE - You say it should list the name or IP, it doesnt, just says PXEClient...should there be more?
Martin - Don't quite understand what IP's you are looking for. The one im getting from the PXE Boot failiure is the wrong server to where i ghost from...
Is this not a dodgy NIC problem?
ARGH!.......
If your DHCP has Option 60 set to "PXEClient", when a computer tries to PXE-Boot the DHCP Server will reply with an IP address (for the client) and the client will then try to go back to the DHCP server to (try too) load the PXE image (Ghost).Originally Posted by Little-Miss
Yup, and this is probably because Option 60 has been set (for this client). If you remove Option 60 the Ghost server should hopefully respond to the client, but you need to understand why Option 60 was set in the first place - because it could break something else
The wierd this is that your workstation does not appear to be getting an Option 60 - so could it be in a different DHCP scope?
mb
just for the pure hell of it i've plugged in another laptop into exactly the same cable etc...
That took me to the PXE menu without issue. Subnet is the same etc. Again the only thing thats different is the faulty one is showing a different DHCP address....
help?
Little-Miss, probably not - but.
When the laptop boots do you have a 'ctrl-a' (or some key combo) for PXE boot options before it tries for an ip address? if it does, check these settings against another, good laptop that gets to the PXE menu.
You never know......
'fraid not...
If you can plug in another laptop and it works, then this does suggest the problem is with the repaired laptop. There must be a difference in the two. maybe settings, but keep trying to find any differences. Look closely at the boot process and look in manual /search google for any PXE boot options / key combos for menus.
Keep going Girl...
Little-Miss (26th April 2010)
I'd bet cash that the problem is literally either:
1) BIOS configuration
2) Dodgy NIC
As we've ruled out that it can't be the servers, switches, cables and damned near everything in between.
I'm leaning toward the BIOS as #2 will require you to send it back... again.
Have a look in Vistas' control panel for the Toshiba BIOS utility, unfortunately I don't have one here to check otherwise I could tell you exactly what to look at and what to change
Az
It sounds as if your (failing) laptop is being sent different information from the DHCP server to that for the working clients.
Can you PXE-boot the Tosh and note all IP addresses that appear in the preboot screen - there should be three. Press the <pause> key to, er, pause things.
After the DHCP twirly propeller completes, it should show a "Client IP" and a "DHCP IP" (or similar wording). I expect the "DHCP IP" will be the **.***.***.55 one for your DC?
There should then be a third "Server IP" address which is where it is trying to PXE-boot from, which should be your Ghost server but will probably be your DC because you have Option 60 set.
If that is the case, and other clients can PXE-boot OK, then there probably is something in your DHCP configuration that is specific to the failing Tosh.
Also, double-check that there are no rogue DHCP or PXE servers on the network.
mb
what i cant understand is... what's changed?!?
This laptop has been on this network before it went away for repair, other Toshiba's are happy to PXE!! WHY NOT THIS ONE, DAMNIT WHY!!! lol!!
Try this: http://support1.toshiba-tro.de/tedd-...0916103428.zip
(Can't recall if I sent you that link already)
This should be the HWSETUP tool you need - also your EduGeek Inbox is full :P
Az
I think i tried that one....
Hmm. What was wrong with the Tosh? If the board has been replaced and the nic is onboard then the mac address would surely change. If the WDS is set to only respond to known clients then maybe you need to pre-stage the tosh laptop. This puts the machine in the AD already and then the client is known. It should then pick up the image and rename the client according to what is in the AD.
I may be barking up the wrong tree though. Not used WDS /RIS in years.
It's the only thing i can think of since you say you haven't changed anything and nothing else has been tinkered with.
Little-Miss,
Can you confirm the three IP addresses that i mentioned in #25?
If the Toshiba is being given the IP address of your DHCP server to boot from (which you hinted at earlier) it sounds like your DHCP configuration is setup incorrectly.
mb
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
