- This topic is empty.
13. July 2007 at 14:43 #511
I rebuilt the laptop I used to use to re-image our 3150’s but hadn’t saved the downloaded WSI setup.
After re-downloading it from Wyse, I’ve found that the guide has changed and WSI no longer handles DHCP-Turbo! Why?? This was so useful!
I still have the old hard-copy of the guide but now I’ve no idea how to configure DHCP turbo. Rather than go through the process of figuring it out, it would be easier if I could just lay my hands on the original WSI installer.
Does anyone have a copy?14. July 2007 at 2:08 #9863
You can still use DHCP turbo with the newer version, it now has a DHCP Proxy service so you don’t need all the option tags in the DHCP scope.
– Set the ip of your notebook to 10.1.1.12 as always (have it plugged into a hub too before the next step)
– Install DHCP turbo and set up a simple scope of IP address from 10.1.1.13 – 10.1.1.17 and set the lease life to 1 day
– Install WSI
And that’s all there is to it!
-TT16. July 2007 at 8:03 #9871
That kind of worked.. the Wyse client is now leasing an IP address of 10.1.1.13, but after installing and starting WSI and hitting submit, I restart the client as requested but it just reboots – it’s not imaging.
I do have it connected via a crossover cable as I don’t have a hub, but I’m sure this is how I used to have them connected…
Any other ideas?16. July 2007 at 9:46 #9872
Check the DHCP Proxy service is running and the firewall is off. Also make sure the boot order on the terminal is set to LAN first. Check that TFTP32 has “10.1.1.12” as the IP it is listening on – sometime it grabs the wrong IP if you start WSI before the network cable is plugged into an active device.
-TT16. July 2007 at 12:06 #9873
Ok, I confirmed the DHCPProxyService status is Started, but I did have McAfee Desktop Firewall running which I’ve now disabled (still no difference).
TFTPD32 does indeed list 10.1.1.12 as the server interface and I’m making sure the client is powered on and leasing an address before I start WSI.
It must be the boot order thing… I know there’s a way to get into the client’s BIOS as I’ve done it in the past, but I’ve tried every key I can think of and it’s still booting normally. What’s the shortcut key to enter setup?16. July 2007 at 12:27 #9874
Sussed it.. It is DEL, but I wasn’t pressing it quick enough.
Now it’s PXE booting but TFTPD32 returns an error!
Connection received from 10.1.1.13 on port 2070
Read request for file . Mode octet
Peer returns ERROR -> aborting transfer
Connection received from 10.1.1.13 on port 2071
Read request for file . Mode octet
TIMEOUT while waiting for Ack block 1. file
Connection received from 10.1.1.13 on port 2072
Unexpected request 4 from peer
Returning EBADOP to Peer
The client returns the following:
BOOT SERVER IP: 10.1.1.12
PXE-T04: Illegal TFTP operation
PXE-E36: Error received from TFTP server
PXE-M0F: Exiting PXE ROM.
Any ideas?16. July 2007 at 21:26 #9875
Man, we are making hard work of this!!!
Go into the TFTP32 settings and set security to none and give this a go. Also check the path the tftp is set to for the boot file – it looks like tftp can not find the requested files, I think its meant to point to the tools/sa directory,
-TT17. July 2007 at 7:39 #9878
I have set TFTPD32’s security to None, but I get the same result.
The Base Directory is set to C:InetPubftprootRapportToolssa, which was the default path.
I’ve no idea why this is so difficult to get working this time round, when it has worked perfectly in the past (albeit with the older version of WSI).17. July 2007 at 11:35 #9879
Yep – I have to say I am running out of idea’s here – sorry!17. July 2007 at 15:26 #9881
Here are a few more things to check:
– is the rapportitf.0 file in the toolssa folder?
– TFTP settings:
TFTP Configurationtimeout = 3
TFTP ConfigurationMAX Retransmit = 40000
TFTP ConfigurationTFTP Port = 69
Advanced TFTP Options Option Negotiation = Enabled
Advanced TFTP Options All Other Options = Disabled
Global Settings TFTP Server = Enabled
Global Settings All Other Options = Disabled
– What version of WSI are you using?17. July 2007 at 15:27 #9882
One more: Is your install running in a virtual or physical enviroment?8. January 2008 at 10:45 #11257shinanigansMember
- Total Post: 1
The issue you are having, is the exact problem I had trying to image an X90e wyse laptop.
Everything you have tried is correct, but what is causing the issue, is the DODGY TFTP program!
Download Solarwins TFTP program, go into options and ensure send/receive is selected, and also ensure the TFTP root directory is set to c:inetputftprootRapport. (this is where the reportif.0 file lives)
Close and reopen Solarwins TFTP, and VOILA!14. February 2009 at 17:50 #15162minnjjMember
- Total Post: 1
Was this problem ever resolved? I am facing the same issue.14. February 2009 at 18:00 #15163
What exact problem do you have? Which WSI version are you trying? Which client?
CG4. December 2009 at 9:35 #17135
- You must be logged in to reply to this topic.