- This topic is empty.
-
Posts
-
We just got some Blazer Conversion Kits. We purchased the kits for 3125 and 3235 devices that are in the field. We were told that all we would need was our FTP server to get WTOS on the devices in the field but I am not seeing any way to do that with NetXfer. Has anyone else tried to do this?
Hi 7h1n,
You will need both to convert them, netXfer will be used to load the initial BIOS boot code and the terminal will then use ftp to load the code.
You can press the P key to start the BOOTP process. netXfer can be configured to run on any IP address via the btptab file. It is also possible to force remote bootp with a rapport script (I can post this if you need it)
Cheers,
-TTThe Rapport script would be great. I’m not sure if it will solve my problem though. If I can’t run NetXfer on the “production” network then I don’t know how I am going to convert devices that are in the field over the WAN. I assume the reason they say not to run it on the corporate network is because BOOTP would interfer with DHCP…
I’ve converted a 3125 locally (off network) and it works great though. The only thing that is weird is that at boot up there is a 30 second delay at “Looking up IP address from DHCP…”
Hi,
I have run netXfer in prod to do conversions no problem, I generally bind a second IP to a server and run it from there. Unless you have another BOOTP service it is not an issue.
The delayed start up may be caused from the switch calculating spanning tree. (Cisco does this). Setting up portfast will resolve this slow start problem. There is an article on this site about port fast,
Cheers,
-TTHere’s the Rapport BootP Script download:
http://www.freewysemonkeys.com/downloads/Addon … _B0009.exe
And the PortFast info:
http://www.freewysemonkeys.com/site/modules.php?name=News&file=article&sid=30
Thanks but I don’t really understand what to do with it other than that it can be installed on my 3235 devices. What then? Sorry…
In the meantime we have run into problems when trying this via crossover cable. Everything appears to work and reports from both end that the file (bootp.bin) upload is successful but they don’t reboot and then when we force a reboot they come back up with CE…
What I did in the past was this:
– Configured the 161 and 162 Option tags
– Put netXfer on a computer on the same LAN as the devices and set it up with the appropriate IP
– From Rapport send the BootP addon, all this does is tell the device to restart and do a bootp request
– This should start the netXfer process loading the code (mini ROM)
– when the device re-boots it will have a small version of Blazer, enough to read the DHCP option tags and load the rest of the code for the full upgrade
– The kit comes with old code, make sure you contact Wyse and get the latest WTOS 5x code. USB key support will be out later this year (hey, you paid for it!)
I am not sure why it will not work with a crossover cable, make sure you are using the correct code for the 3235 conversion. Its not the same as the 3200 conversion code. Also try a different device, maybe you have a problem one. Generally I have found the crossover cable conversion very easy.
Cheers,
-TTThanks. That makes since. What’s frustrating is that I have a ticket open with Wyse and no one has offered updated code which would be a nice thing to try given our scenario…
The updated code is only after the netXfer is finished so you need to get over that issue first…
Awesome, hopefully you think it was worth the effort – ICA/RDP should be allot faster now 🙂
- You must be logged in to reply to this topic.