ICE
TCP/IP Products => TCP-PRO => Topic started by: Bob on December 22, 2003, 12:18:43 pm
-
This thread will be for common info on shortcuts and other tips for using ICE.TCP.PRO
-
When making modifications to items in the host edit box (i.e. autoconnect), be sure to hit exit instead of the upper right corner x. Exit here means SAVE and EXIT. The x will leave without making changes.
-
Note: This pertains only to ICE.TCP Pro profiles, NOT to network or windows profiles.
The following lets you create one profile and distributes it to other computers so that everyone runs with the same profile configuration.
Here's how to use global profiles:
1. Run TelnetPro. Pull down menu item "Profiles" and Select "Organize Profile"
2. Create or edit the profile(s) to be made global.
3. Export them to a file or files with a "g_" prefix and a
".cfg" extension. (The profile name(s) inside do not necessarily match the file name.)
3. Copy the file(s) to the Pro program directory in every machine you want them to load. The program will load the user's profile first, then load the profiles from any "g_*.cfg" file in the program directory.
NOTE:
*-The program will siliently overwrite any user's profile whose name matches a global profile (including 'default' profile).-*
An administrator can deter users from modifying the global profiles by fiddling with the global file's properties (ie. read-only, hidden, permission flags, etc), or by restricting the program directory.
-
Here is a way to print directly to a device in ICE.TCP Pro. It requires version 5.1.01 or newer.
Don't attempt this if you are not familar with the use of regedit!!
Underneath
Current User -> Software -> J. River -> ICE.TCP ->5.0
You need to create 2 new entries.
One is a DWORD called DirectPrinterPort
Set the value of this to 1 to use direct printing (0 to use normal windows spooling).
The second is a string called DirectPrinterPortName
Set the value of this to the name of the port you want to direct print to, usually LPT1:
The next time you run TelnetPro the direct printing values will be used.
-
The Licenses folder under the TCP5_USER share from the license admin machine MUST be writable to get a sequence number. See the 2,0 error message in the following message.
http://yabb.jriver.com/ice/index.php?board=2;action=display;threadid=12
To test to see if the license file is writable, from the client machine, BROWSE to the TCP5_USER share on the admin server and then into the Licenses folder. Right click on an empty space in that folder and do new -> folder. If that FAILS you don't have write permissions in that folder and will have to correct this before you can get a sequence number. This is a windows permissions issue, NOT an indication of a problem with ICE.TCP.
After you can verify that you can write to the Licenses folder from the client computer, BROWSE to the Configwizard program on the admin computer. It's under the TCP5_USER share in TCP4-32 for the classic version or TCP-Pro version for the 5.1 client. Double click on the appropriate Configwizard icon to get a sequence number.
If you still can't run ICE.TCP Pro or Classic after that you have a registry problem on the client machine, probably because of installing on the client WITHOUT administrator priviledges (don't forget to take domains into account if you are using a domain controller). See:
http://yabb.jriver.com/ice/index.php?board=2;action=display;threadid=14
-
This is an example of a simple ICELP script that does text printing (converts Unix style end of lines to printer style end of lines)
There are also some comments in here for binary only printing as well (for example, if you are printing postscript or graphics)
Follow this link to download it
ftp://ftp.jriver.com/pub/TECH.SUPPORT/icelptext.Z (ftp://ftp.jriver.com/pub/TECH.SUPPORT/icelptext.Z)
Also, make sure you pull this directly to your unix machine or if you use a windows machine and then move it to a unix machine, make sure both ftp transfers are binary. After transferring to the unix machine, use uncompress to uncompress the file.
For info on installing print spool files for ICELP on systems not covered in the manual, see the ICELP section on the support page: http://jriver.com/support/tcp.html
-
If you have version > 5.1.0 you can see what sequence number your PC is using.
Only attempt this if you are familar with the use of regedit.
Run regedit and go to:
HKEY_LOCAL_MACHINE
SOFTWARE
J.River
ICE.TCP
5.0
License
The sequence number is TempUserID
The value will look something like 0x000014 (20)
In this example, 20 is the decimal value of the sequence number.
Obviously, it should match the machine info in that user slot reported by LicenseAdmin.
This is a read-only key, changing it does NOT change the sequence number.
-
The default port for icelpd is 2346.
If you are logged into the unix machine you can do a couple of quick tests to see if you have installed icelpd properly.
First type:
icelpd -c
you should get back:
Icelpd - ICE.TCP Print Server.
Version 4.07b.
By Roman Oliynyk.
(C) 1994 James River Group, INC.
All rights reserved.
Then try:
telnet 127.0.0.1 2346
if you get "connection refused" you do not have icelpd installed in the inetd or xinetd config files properly. See the manual for more info.
if you get a connection you can try typing in:
ICELP*
and hit ENTER
you should get back
HI_ICELP
If you don't you still don't have icelp installed properly, check the
manual for more info.
-
> >
> > How do I tell Telnet Pro to use Port 1234?
There is a fluke in the edit Host List box (the grid with all the hosts and all the host fields) that prevents a user from entering a new port value. To enter a port value that has never been used (on that machine), connect once by typing in the host name in the host box on the main window, and typing in the new port value in the box to the right of host box (and the SSH check box); the one that usually has the value "telnet." After connecting once this way, the new port value will be available in the pull down box when editing any host's port value in the edit Host List.
-
Is anyone able to assist me with creating Global Profiles.
When I create the required profile and export it with g_ into the TCP5 Directory TelNet Pro is not detecting these profiles automatically.
I can however go to import profile and select the newly created Global Profile and it imports OK.
You need to copy the g_ file to the program directory for each machine (after the normal installation).
Here are the complete instructions and caveats:
-----------------------------------------------------------
Here's how to use global properties:
1. Create the profiles to be made global.
2. Save (Export?) them to a file or files with a "g_" prefix and a ".cfg" extension. (The profile name(s) inside do not necessarily match the file name.)
3. Copy the file(s) to the Pro program directory in every machine you want them to load. The program will load the user's profile first, then load the profiles from any "g_*.cfg" file in the program directory.
*-The program will siliently overwrite any user's profile whose name matches a global profile (including 'default' profile).-*
An administrator can deter users from modifying the global profiles by fiddling with the global file's properties (ie. read-only, hidden, permission flags, etc), or by restricting the program directory.
-
We did several tests of build 21 vs 22 vs 23 vs 1.0.24 (current). Build 21 does have the older ssh code in it however in our tests all of the builds acted the same.
The results indicate that if the PC goes into sleep mode and WOL (wake on lan) is NOT enabled AND the remote unix host has keepalives turned on THEN after the keepalive times out (about 15 minutes after sleep mode starts) the connection will drop.
This IS proper behavior under the circumstances. If you do not like this behavior you need to change one of the paramters. The best place to change it is on the PC. Enabling WOL (if you can) should keep the session alive as would configuring your PC so that it will not go into sleep mode for anything other than the display (could require bios and/or windows setting changes depending on the windows version).
Alternately one could try to disable the keepalives in UNIX however this could have the unwanted side effect of preventing dead sessions from being harvested so I would not recommend it.
-
Put a blank floppy in your A: drive on the machine that has the license server.
Go to Program Files->J River->ICETCP5 SERVER->TCP5_USER
Copy the "Licenses" folder to the A: drive.
Copy the "Data" folder to the A: drive.
Copy TCP-Pro/configwizard.exe to the A: drive (for 5.x).
Copy TCP4-32/configwizard44.exe to the A: drive (for classic 4.4).
Take the floppy to the remote machine. Open the A: drive and run either configwizard.exe or configwizard44.exe depending on which client you have installed.
Repeat the step above for each remote machine that needs a sequence number.
When finished, take the floppy back to the license server and copy the Licenses folder from the A: drive back to Program Files->J River->ICETCP5 SERVER->TCP5_USER overwritting the Licenses folder there.
You are finished. At this point the licenseadmin program on the license server machine should show the remote client users (as well as any lan users that were there before).
-
If you have a situation where an application requires the use of control keys that would normally be intercepted by windows to provide shortcuts you can turn off that behavior so that the keys will be passed directly to your application.
With PRO running, look at profiles (on the title bar) and select the profile you want to change (most will be using default).
Select the Keyboard icon on the left then uncheck the checkbox that says:
Allow use of CTRL-C and CTRL-V for copy and paste operations
This will free up control-c and control-v for your unix apps as well as other windows shortcut keys like control-a
Of course if you change a profile you will need to stop and restart PRO for the change to take effect.
-
If you have a version of Windows older than XP and are connected to the internet, you can use Network Toolbox to sync your PC clock to internet time. (XP has it's own timesync).
To do this (in Win 2k for example):
Open control panel->scheduled tasks
Start add scheduled task
Using the wizard, browse to network toolbox \Program Files\J River\ICETCP5 and double click on NetBox (the one that looks like a toolbox)
Choose Daily for perform this task and put in timesync as the name of the task and click on next
Change the time to run this task to a time your computer will usually be on and the perform this task to Every Day and click on next.
On win2k you'll need to enter your password here a couple of times and click next
On the final wizard screen, check the box that says Open advanced Properties ... and click finish
Under advanced properties and in the run box after the last " add a space, then the following:
/TIMESYNC -time-a.nist.gov
and click on ok
You should be all set.
Notes:
You are connecting out on the time protocol, port 37. You may have to have your network admin open you firewall for outgoing access if this doesn't immediately work.
The server listed above time-a.nist.gov (a dash in front of the name is required for Network Toolbox) may not be the best server for you to use. Your company may have an internal server you are supposed to use or one of the internet servers may be closer to you. Check the following page to see other available servers.
http://tf.nist.gov/service/time-servers.html
-
First make sure the host(s) you want are already created and in the host list.
Second, open the ICETCP.INI file in your WINDOWS directory with notepad.
Third, add lines similar to the following to the bottom of the file:
[Dejawint:mylinux]
SelectedHost=oldbb
AutoConnect=1
TerminalLines=25
TerminalType=LINUX
[Dejawint:mysco]
SelectedHost=smooth
AutoConnect=1
TerminalLines=25
TerminalType=ANSI
In the examples above, oldbb is the name of one host in the hosts lists and smooth is the name of the other hosts in the hosts list. mylinux is the name of one profile and mysco is the name of the other profile. Alternately, you can create the profiles using the setup tab in iceconfig however it can be difficult to get the order of operations correct when creating profiles in iceconfig.
Fourth, make a couple of shortcuts on the desktop to plus' deja32.exe program. Change the shortcut names to something descriptive like mylinux and mysco. Then in the properties for the shortcut, in the target, after the trailing " add a space and the profile name. Mine looks like this:
"E:\Program Files\J River\ICETCP4\deja32.exe" mysco
You should be good to go. Note that the lines I listed above are the minimum to get a connection. After connecting, a bunch of other lines will be added automatically to each profile specifying stuff like the selected colors, printer, screen size, etc. You can change those too if you want to customize anything else...
-
Problem:
The keymapping file in the 5.1 PRO client can't handle the return (enter, 13 decimal, 0D hex) code properly.
Workaround:
Enter each CR as a CR/LF pair. This will be translated to a bare CR when sent.
For example, to send "hi" then 2 CR's then "mom" then another CR. In the parameters section of the key you are trying to program in the keymap editor, do:
hi\0D\0A\0D\0Amom\0D\0A
(control codes are sent by putting in a \ followed by the code in hexadecimal)
-
Start->Run type in regedit and hit enter.
Find HKEY_CURRENT_USER->Software->J. River
Right click on the J.River folder and export it. Call it jriver and save it to the desktop.
Take the resulting jriver.reg to another computer and just double-click on it. It will import all settings to the new computer!