Chris_ Posted January 17, 2011 Posted January 17, 2011 Hi all. I've done a few searches on this topic, tried a few things mentioned but I've still not had any luck. I'm trying to get some old computers to load thinstation over the network and connect to a terminal server. Options 66 and 67 are set on the DHCP server and the TFtpD service (part of RIS I think) is started on the terminal server but the machines just timeout when trying to find the TFtp server. Any help would be much appreciated. Chris
natm Posted January 19, 2011 Posted January 19, 2011 Hi Chris, Have you had a look through these notes? :: Thinstation FAQ :: When you PXE boot a client does it get an IP? does the RIS menu load? Nat,
Chris_ Posted January 19, 2011 Author Posted January 19, 2011 The PXE client gets an IP from the DHCP server but it then times out when trying to locate the TFTP server/file. Option 66 is set to one of the hostnames of the terminal server, option 67 is set to pxelinux.0
kmount Posted January 19, 2011 Posted January 19, 2011 And you're sure the TFTP service is alive / not firewalled?
Chris_ Posted January 19, 2011 Author Posted January 19, 2011 I start the TFTP service so I assume that it's alive? I believe the Windows firewall is disabled so that shouldn't be blocking it. @Nat, I did look at that RIS guide from Thinstation but I don't think it's actually using the whole RIS service, just the TFTP part of it. On the RM communities nobody mentioned editing all the RIS configuration as stated in that doc.
natm Posted January 19, 2011 Posted January 19, 2011 Option 66 is set to one of the hostnames of the terminal server, option 67 is set to pxelinux.0 Try changing option 66 to hand out the IP of the terminal server and not the hostname, the client might be having a problem resolving the hostname. Also run "netstat -anb" on your TFTP server, you should see an entry showing the service is ready and listening on port 69... UDP 0.0.0.0:69 *:* [tftpd.exe] Nat,
Chris_ Posted January 21, 2011 Author Posted January 21, 2011 Try changing option 66 to hand out the IP of the terminal server and not the hostname, the client might be having a problem resolving the hostname. Also run "netstat -anb" on your TFTP server, you should see an entry showing the service is ready and listening on port 69... UDP 0.0.0.0:69 *:* [tftpd.exe] Nat, I changed option 66 to the IP and the client timed out again. I'll try setting up a TFTP server on a regular workstation to see if it's a restriction on the server.
Chris_ Posted February 19, 2011 Author Posted February 19, 2011 I've been trying to crack this but still had no luck! I've tried using tftpd32 as the tftp server on a regular XP install with no firewall and still no luck. I've followed the guide here and my set up is the same but I am still unable to tftp boot http://www.edugeek.net/forums/thin-client-virtual-machines/70852-thinstation-problem-getting-global-configuration.html#post632197 The computers get their IP from the DHCP server but then timeout when trying to locate the tftp server.
Arthur Posted February 19, 2011 Posted February 19, 2011 Option 66 is set to one of the hostnames of the terminal server, option 67 is set to pxelinux.0 When I used Tftpd32 to PXE boot Windows PE, I had to prefix "pxelinux.0" in option 67 with a forward slash because the boot files were located in the root directory. Might be worth trying?
Chris_ Posted March 1, 2011 Author Posted March 1, 2011 When I used Tftpd32 to PXE boot Windows PE, I had to prefix "pxelinux.0" in option 67 with a forward slash because the boot files were located in the root directory. Might be worth trying? Thanks for the suggestion Arthur. Unfortunately I still had no luck and got the same timeout message.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now