Hey all

This is a total edge case, but I thought it may be interesting to some.

We have thin clients, which RDP to a Windows Terminal Server, through which users SSH (using PuTTY) into our Linux server.�� This isn't flexible (for good reasons which I won't go into here).�� However, to talk properly to our new EFTPOS units, we need to know the IP of the thin client.�� Of course, through SSH you only get the IP of the client, which is the Terminal Server.

Here's how I fixed it:

1) Add the following line to /etc/ssh/sshd_config, and restarted ssh:

������ AcceptEnv CLIENTNAME

2) Added the following to the Windows login script:

������ REG ADD HKCU\Software\SimonTatham\PuTTY\Sessions\DG\ /v Environment /d "CLIENTNAME="%CLIENTNAME% /f

3) Result:

������ ~ $ env | grep CLIENTNAME
������ CLIENTNAME=eric-lmde

��

>From there, we can do what we needed with the EFTPOS!

Eric

--------------------------------------------
Q: Why is this email five sentences or less?
A: http://five.sentenc.es

_______________________________________________
wlug mailing list | wlug@list.waikato.ac.nz
Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug