[THIN] Re: conditional setting for home drive
- From: "Rick Mack" <Rick.Mack@xxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Wed, 29 Sep 2004 08:25:48 +1000
Hi Pavlo,
Sounds a bit like the LBS (location based security) telnet product that
Queensland Health used to use (called Hibiscus). It either required a unique
IP address or IP/port address combination for every user.
On the unix side, lbs was handled by appropriate entries in /etc/services and
/etc/inetd.conf together with a perl script to generate a unique plid (physical
location id).
This required some way (we used a user/port lookup table (kix and ini file) to
assign a unique port address to a user on a TS system.
In your case, sounds like remote.cmd does it, but it can't handle UNC paths.
Note that the script is most likely being run by a macro in Accuterm 97 so
looking at the Accuterm setup may solve things.
While I'd be tempted to have a look at the total process and try and make
things a bit slicker, an easy approach would be to use the subst command during
login to substitute a drive letter for the UNC path, eg
subst p: '\\profile_server\profile_share\username'
Since applications see a substituted drive as a "real" local drive, things then
should work as advertised.
regards,
Rick
Ulrich Mack
Volante Systems
________________________________
From: thin-bounce@xxxxxxxxxxxxx on behalf of Pavlo Ignatusha
Sent: Wed 29/09/2004 5:14 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: conditional setting for home drive
Rick,
This is what I found.
This software in unix database ported to Windows. It is running it's own
telnet server (telnetd). Currently it is installed on W2K server box. Users
launch telnet client (Accuterm 97) from Citrix and establish telnet session
with this server. Because each user uses unique port range every user has to
have a unique remote.cmd script put into his/her homedrive. This script
contains user port range and other software-specific things. So far when
things were implemented consultants set all these user accounts to have
local homedrive mapped in AD to d:\users\username. This way on this w2k
server there is a d:\users folder that has subfilder for each user that
contain only remote.cmd.
If I try to point user's home drive to network share in AD I get this error
upon logging into the telnet session:
jBase Telnetd server Version 3.6.8
NT User ID: USERNAME
Password:
CMD.EXE was started with '\\profile_server\profile_share\username' as the
current directory path.
UNC paths are not supported.
Defaulting to windows directory.
Microsoft Windows 2000 bla-bla-bla
I'm not that experienced with telnet servers but it looks like it is
hardcoded in the server to look for a remote.cmd file in users home folder.
If there is no folder it defaults to %systmroot% and looks for the same
file. If I place my remote.cmd in the %systemroot% and have home drive still
mapped to the network share everything works fine.
I guess it means I may have to set homedrive in AD to d:\users\%username%
for this telnet to work and for all TS sessions overwrite it in logon script
with smth like this:
net use u: \\profile_server\profile_share\username
set home=U
set homepath='\\profile_server\profile_share\%username%
Any other suggestions?
Thanks,
Pavlo Ignatusha
Systems Network Coordinator
Pembroke General Hospital
Tel. (613) 732-3675 ext.6150
Fax. (613) 732-9986
www.pemgenhos.org
"All that matters is love and work" - Sigmund Freud.
#####################################################################################
This e-mail, including all attachments, may be confidential or privileged.
Confidentiality or privilege is not waived or lost because this email has been
sent to you in error. If you are not the intended recipient any use,
disclosure or copying of this email is prohibited. If you have received it in
error please notify the sender immediately by reply email and destroy all
copies of this email and any attachments. All liability for direct and
indirect loss arising from this email and any attachments is hereby disclaimed
to the extent permitted by law.
#####################################################################################
Other related posts:
