Thinstation Setup Help

[Ric_]

Also check that you haven't run out of TS CALs. I have found Windows to be very poor in its communicating this to you. IIRC the only way to find out is to go into the Licensing console and look how many are left. TS also has a habbit of holding on to CALs for a while (90 or 120 days!).

[ICTNUT]

Ric_:

 

This is a new TS Server with 150 CALS non of which ahve been used yet, they have been activated and are ready.

 

I have not yet got the reconnect thing sorted however I have install 2X ThinClient Server and it appears to have an error when trying to login - No route To Host - aand I wonder iof this is also causing the other method to fail.

 

Looking into the reason now and maybe shed some light on the matter !

[Ric_]

@ICTNUT: Can you connect to the box via the client in Windows?

[ICTNUT]

Yes no probelm at all

[Ric_]

I take it that whe nyou connect from a Windows client, you don't log in as an administrator?

 

Also, can the terminal server definitely 'see' the license server?

 

Also, it's worth checking DNS... it's always DNS

[ICTNUT]

1 - No logged in as a student.

 

2 -The license server is the same TS server

 

3 - DNS shows an entry for the TS Server with the correct IP.

 

Inever expected it to be this difficult to setup, but I suppose there is a steep leraning curve happening here.

 

I can understand why people go out and buy hardware based TS clients that just plug and play if this is whatus required to get one up and going.

[Ric_]

@ICTNUT: I didn't have any problems like this. I must admit that the clients do occasionally get to the reconnection box that you mention and go no further but a quick reboot fixes it.

 

Have you tried using the TS-O-Matic onthinstation.org? Have you tried booting off the live CD too just to test the connection?

[ICTNUT]

I have used the tsomatic facility and got the boot splash to work and have also got the menu "replimenu" facility to work also but both result in the dreaded re-connect box.

 

I will try a live cd when I get back into the office tomorrow and let you know how it goes.

[CyberNerd]

try logging into the console of the TS (ctrl-alt-F1 ?F2? F3?) as root and see if you can ping the rdp server and/or telnet to it on rdp port.

also try AUTOSTART=off to see if you get any more info. Also if you built TS with a gui (blackbox) you might be able to diagnose using rdesktop from a shell.

[ICTNUT]

@cybernerd:

 

Logged in console as root and could NOT ping the RDP server but can ping the DNS servers (internal) but not external like google.co.uk.

 

On my PC (WInXP) I can ping the RDP server, DNS Servers, and External so I plugged the TS box into the same port (we use VLANS here) but no change which leads me to beleive that the TS box must be the problem.

 

Very strange though......

[Ric_]

Appears to be a routing problem then really... or maybe a temperamental NIC in the server. You could maybe try substituting it for a different one for testing purposes.

[Geoff]

I'd check your VLAN setup too if you use them.

[ICTNUT]

I am using a 3com in the ThinClient and I am going to change it to an Intel Gb Card and try that.

 

the TS server only has one NIC onboard and I don't really want to pull that out just yet, although I may need to ;-)

[ICTNUT]

Have swapped cards on the TS Server and the Thinclient box but still no joy

 

I am going to try another PC and see if that works.

 

@Geoff: VLANS are ok My PC is on our backbone VLAN and the ThinClient PC was on the Student VLAN however when I plug the thinclient box into the port my PC is on this made no difference so we can rule out the VLANS being at fault.

[Geoff]

I'd get out the packet sniffer at this point.

[ICTNUT]

Success :-)

 

Checked out the PC got another one and straight in on the TS server, Very fast too from POST to TS Login screen 20 seconds very nice.

 

Thanks all for your help, much apreciated, now onto boot splash screens