Homepage › Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Set up remote shell
- This topic has 14 replies, 8 voices, and was last updated 12 years, 8 months ago by Anonymous.
-
CreatorTopic
-
October 27, 2010 at 4:11 pm #52074Davin StuderParticipant
Does anyone know how to set up the shell window to work remotely? I have turned on the Telnet service on the cloverleaf box and I can connect, however, it doesn’t seem that any of the environment variable are being loaded so I cannot run any of the hci… commands. I am using a Windows 2003 server and Windows XP client. Thanks. -
CreatorTopic
-
AuthorReplies
-
-
October 27, 2010 at 5:36 pm #72965Sam CraigParticipant
You have to login to the telnet session as user hci.
-
October 27, 2010 at 5:58 pm #72966Davin StuderParticipant
Thanks a ton for the reply.
We don’t have a user called hci. Do you mean hciuser? I tried that user and was able to log in. Then I tried to run mktclindex on the tclprocs folder to reindex the procs, and it didn’t work. It works if I do this from the actual server. So, I’m thinking the environment is still not totally set up.
-
October 27, 2010 at 7:09 pm #72967Sam CraigParticipant
We run the Cloverleaf server on an AIX system.
There is a user called hci that is setup on the server during Cloverleaf install.
When logging in as the hci user in AIX, there is a .profile file that runs and sets up the environment variables.
Here is a quote from the .profile file……
# This file is used to set up a per-user login environment. Since this# .profile is in the hci user’s home directory, it is used to set up the
# environment for the hci user.
Found this in the Windows system install instructions.
hciuser accountThe hciuser account must be created before Cloverleaf
-
October 27, 2010 at 7:13 pm #72968Davin StuderParticipant
Yeah, I was able to log in with the hciuser user … it just seems the rest of the environment stuff is not being set when I log in. Thanks for the help though.
Anybody on a Windows Server platform have any experience with this? Thanks.
-
October 28, 2010 at 8:00 am #72969Robert KersemakersParticipant
How about starting the Cloverleaf IDE from the workstation, then under ‘Runtime’ click on ‘Shell Window’ to open a shell window. Should work from there.
Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands
-
October 28, 2010 at 5:50 pm #72970Davin StuderParticipant
Um, that is what I am referring to. On a remote client the shell doesn’t set up all th environment stuff needed to work correctly. On the server it works fine, but I would rather not have to go to the server every time I need to do something through the shell. Is there anybody out there working with a windows Cloverleaf server that knows how to set this up correctly?
-
October 28, 2010 at 6:31 pm #72971Jeff AndersonParticipant
From Microsofts Tech site (http://technet.microsoft.com/en-us/library/cc730627%28WS.10%29.aspx):
To allow Telnet Client to send an environment variable
1.
Open Registry Editor. Click Start, and then type regedit in the Start Search box.
2.
If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
3.
In the navigation pane, open HKEY_LOCAL_MACHINESoftwareMicrosoft.
4.
If the key TelnetClient does not exist, then create it. To do so, right-click Microsoft, then click New, and then click Key.
5.
Type TelnetClient as the name of the new key.
6.
Right-click TelnetClient, click New, and then click Multi-String Value.
7.
Type AllowedEnvVariables as the name of the new entry.
8.
In the details pane, double-click the new AllowedEnvVariables name.
9.
In the Edit Multi-String dialog box, type the names of the environment variables that the Telnet server must be able to query on this client. Type each variable name on a new line.
10.
Click OK to save your completed list.
-
October 29, 2010 at 10:10 am #72972Robert KersemakersParticipant
Ah ok, I thought you were trying a telnet session from a command prompt. I now understand the problem: you can open a shell window from the IDE on the server, but not from IDE on the workstation.
We have a small Windows server with CL5.6 on it and we always work from the server. I have installed the 5.6 client on a Win XP workstation to run the IDE from there. When starting a shel window from the workstation, a Telnet-box appears, but disappears again immediately.
So it doesn’t work for me either. But my problem is that I am not allowed to telnet to this windows server. When I try to telnet from a command prompt on the workstation, I get a ‘Can’t connect’ error message. And I’m not able to change this, as this will be a security issue.
Weird thing is, that if you run a command prompt on the server, you can’t invoke hci-commands as well, even though you’re logged on as hciuser. You will need to start a shell window in the IDE for this to work; it sets a lot of variables that way.
Maybe you can try to add the required variables to the environment of hciuser.
Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands
-
December 13, 2011 at 2:30 pm #72973Ronald OrtizParticipant
Was this issue ever resolved? I’m on a Windows 2008 R2 Standard server and would like to have this setup.
Currently, when I click on the Shell Window in the IDE it will prompt me to enter my user ID/password. Our server is using HCIUSER/*******. I can telnet into the server but the environment variables aren’t automatically set. I’d have to manually type this in every time.
-
December 13, 2011 at 6:12 pm #72974Davin StuderParticipant
Nope. I never got it resolved.
-
December 13, 2011 at 6:37 pm #72975Charlie BursellParticipant
See if this helps
http://technet.microsoft.com/en-us/library/cc771907(WS.10).aspx
-
December 13, 2011 at 7:12 pm #72976Davin StuderParticipant
Ok, that helps somewhat but really I could do this by just running a batch file after connecting. The real kicker is that there are a SLEW of environment variables to set to get it to actually work. That is the real issue.
-
December 14, 2011 at 3:49 pm #72977Terry KellumParticipant
Easy fix: Install Linux 😀
(I really just couldn’t help myself. I hereby submit myself for noodle-whipping!)
-
December 30, 2011 at 9:53 am #72978AnonymousInactive
Hi,
Maybe this will help?
Code:cd ITPSquovadxqdx5.3integratortest_prod
call setroot c:ITPSquovadxqdx5.3integrator test_prod
# test_prod is the thread folder name
hciprocstatusI use it, when I want to perform a hci command from a Windows command line (but on the QDX server).
-
-
AuthorReplies
- The forum ‘Cloverleaf’ is closed to new topics and replies.