- This topic is empty.
-
Posts
-
hi,
previously i was using v4.4.1 and the PXE on my 9150 and S90 clients was working well.
Now i have a new server with WDM v4.5.2 – the PXE is not working any more and the 9150 and S90 clients does not pick up an IP at boot up.
any thoughts?
thanks.
i hate to ask such a dumb question but this happen to me when i upgraded to 4.5.1 some how or another the firewall got activated and i was getting the same issue it took me like 3 hours to relize and i felt so dumb afterwards but hay if it helps out just check on that
thanks for your reply mate…but the firewall is turned off.
any other thoughts pls?
you can only have one PXE server on your network at a time. Is your old 4.4.1 server still alive? I was not sure if you updated your old server or brought up a whole new server….?
my 4.5.2 is a brand new VM box with a different IP and machine name.
my old 4.4.1 istill exists but i have stopped all rapport and ftp services.
i have also changed my dhcp option tag 186 to point to my new 4.5.2.
dont know if i am missing something…
thanks.
If you had any IP Helpers configured on your routers to help your clients find your PXE server, they may still be pointing to the old server. They will need to be changed, too.
While I’ve never worked with the clients you have, when you attempt a PXE boot, the IP address it attempts to boot from is usually shown on the screen. Does it possibly show your old server still?
hi,
i spoke to my network guy and he said IP helpers is configured for the PXE boot but the Rapport Server IP is stored no where on the Routers – so he said there is no old Rapport server IP configured on the Routers.
Also, when my client boots up it does not pick up an IP at all – it says “No Boot FIle Name Found” – and all my 9150 and S90’s in the 4.5.2 console it shows imageable as No.
I am sure there is somewhere where it is still pointing to the old Rapport Server IP – but can’t figure out where.
Help. Thanks.
Hi,
Open up the WDM console and there will be a icon in the task tray, click this to access the WDM log viewer. Under the TFTP section you will see a entry when the XPe device boots – can you see this?
Put the XPe device on the same network segment as the WDM server to rule out IP helpers and test. Also make sure portfast turned on if you use Cisco switches.
Finally to make sure WDM 4.5.2 installed OK locate the original download and copy the WDMv4.5.2_RTM_WYSEswreptools folder to your server inetpubftprootrapport folder.
Check the event log on the WDM server for errors and make sure Microsoft DEP is only turned on for essential Windows services,
Cheers,
-TThi,
in the whole conversation i forgot to mention i thing – in the past everything was working fine when i was using Rapport v4.4.1 but during that time my devices and the Rapport server was in the same network.
The old Rapport v4.4.1 is now shutdown and my new rapport server v4.5.2 has been moved to the Data Centre now and on a different network – will this make any difference?
i also confirmed with my network guy and cisco portfast and ip helpers is all in place.
so the big difference with my problem is my new Rapport is in different netwrok.
any thoughts pls?
Yes, this makes a huge difference.
If you ave confirmed that the IP helper is pointing to the new WDM server and portfast is enabled you next need to confirm the WDM server is receiving the DHCP broadcast from the terminal.
If all of the devices say PXE enable – no in the WDM console you will need to figure out where the broadcast is being blocked. Try installing Ethereal/WireShark on the WDM server and see if the broadcast is received.
Also, check to see if you have other PXE servers that may also be responding to the Wyse devices as this can cause a problem.
I hope this helps!
Cheers,
-TThi,
you mentioned above to check “Under the TFTP section you will see a entry when the XPe device boots” – i checked this and this column is empty.
nothing is logged in TFTP when XPe boots up. the only place where is logs is in the “Web Services Log” column as device checked in.
OK, this means the server did not receive the DHCP broadcast from the client.
Its time to check the IP helpers again a start look at the network to see whats blocking the UDP DHCP packet,
Cheers,
-TT
- You must be logged in to reply to this topic.
