Forum Replies Created
-
Posts
-
Hi,
For information. I got my Wyse client back from repair (infocare). It has been reflashed. I probably used not a right image.
I did image it again (in fact conversion from V30 to V10). It worked well with my Windows 2003 server.
I never managed to use the XP computer I had to my disposition. I really think the cause is the DHCP-proxy that is not activated.
I will check more around that but I think I will stick to the use of Win2003.rope
Hi CG,
Now I did the installation on the Windows 2003, and can the the DHCP proxy started.
Then I could this time the process og loading files from the terminal, with a lot of information on the screen and the tftp which shows that root.i2u, env.i2c were exchanged.
So fo me, the installation on the XP doesn’t work at all on my computer.But after the whole process now my terminal can’t bott at all. (i nevertheless downloaded an image for my terminal from the Wyse support).
Now the terminal rings all the time without showing anything on the screen…can’t find any reset button neither find rith keybord button? Is there a way to go further?
thanks.
Hi again,
I understand now the DHCPProxyService should be installed. I see this program in Program files – DHCP Proxy.
What I don’t find out is how to check if it is working.
netstat -a doesn’t show it, neither Services.
Do you know how I can check that and how to start it if is is not working?When this dhcp proxy is supposed to be started?
Thanks in advance.
Rodolphe.
Hi CG,
Thanks for help.This computer had nothing specific installed before. I uninstalled all that was firewall and antivirus.
I just followed the procedure for WSI 1.3.6, for XP, with FTP services, DHCP turbo and WSI.
During the procedure I was asked to confirm the folder where FTP is installed, but not where Turbo DHCP is.
In older procedures I saw it was required as well to confirm DHCP installasjon folder, but I didn’t see it along the installation. I assume it is no more required.But if I don’t fill any DHCP option in the Turbo DHCP (yes, noting should be filled in following the documentation…), then I get the message that “boot file “PXE-E53 no boot file recieved”.
And when I see the trace I just see in that case that the terminal request via DHCP en boot fil but the DHCP server answer with nothing regarding bootfil.If there is a proxy that should answer, then I don’t know how to check if it works or not, if there is a service started for that.
I am confused with the installation guide..is that really how it should be done?
Rodolphe
Hi CG,
thanks.My real error message is this ome:
Contacting Server [4001] (02)
Searching for interface ..+—+—+–+Rapport HTTP Service Not detected
Failove Asigned: =10,1,1,12, =80(TFTP)
MY IP 10.1.1.13, Server IP 10.1.1.12, =80(TFTP)
RTY_Hservr IP 10.1.1.12, RTI_Hport=80
server found [4001] (01)
Uploading 00806460314 [4002] (02)
Launch attempt (1) ‘00806460314:’
Launch attempt (2) ‘00806460314:’
Launch attempt (3) ‘00806460314:’And when I see it is mentioned 80 (TFTP) in the message, I wonder if there should a server responding on the 80 pot. I followed the procedure and it is not mentioned anything regarding that port, just tftp and ftp.
Have I mised something here?
You said WDI act as a dhcp proxy, but does it mean WSI is a process running during the installation?
Have done several reinstallation and still get that same message.
Thanks.
Hei,
I assume you mean the WSI 1.3.6, that’s the latest I found in the V30 download section?
Cause following that installation guide for Windows XP with DHCP turbo and WSI, that was nomally indeed not requested to fill any option in DHCP.
Then I did a trace when starting the terminal, having the XP-DHCP-TFTP started, I never see any information exchanged regarding bootfile, option 43.Do you mean the WSI installation should configure those option self to the DHCP or that these optin are not required all?
It’s not very easy to check if the WSI/DHCP have been well installed or not.
thanks for information.
flyfisher,
Got exactly the same error. I understood there were some problems regarding the DCHP information transmitted and try to get another DHCP server to work (seems the Turbo DHCP is limited regarding for example the use if option 43 – specific product information – not able to take HEX values).
The DHCP build native in windows gives better posibilities.What values did you use on the DHCP server
option 66:ip adress or name of the server?
option 43: 3c:04:49:54:46:00:43:09:72:6f:6f:74:2e:69:32:75:00:00
option 67: apportitf.0Thanks for information.
Rodolphe.
