Q. How can I start a ThinAnywhere session?
Q. How can someone collaborate with me in a ThinAnywhere session?
Q. When I open an application in a ThinAnywhere session, everything is larger and almost too big to use. Is there something I can set to make things more manageable?
Q. What OPENGL32.DLL files do I install for RDP and Citrix ICA?
Invalid Login.
iipadmin: Error: Connect status: 9.
GeoProbe
Q. How do I change the Host Name on my ThinAnywhere server?
Q. My keyboard isn’t working correcly in the ThinAnywhere session after installing new client software. What do I need to change?
Q. We have changed the IP Address of our ThinAnywhere server and now our license doesn’t work. What can we do?
Q. I really want to track who logs in on the ThinAnywhere server, when and for how long. How can this be accomplished?
Q. We’ve just installed the new 3D hardware accelerated ThinAnywhere server software.
When we try to login the connection doesn’t complete.
server. When I start a session, the connection is completed but nothing appears in the ThinAnywhere widnow. Then, when
I move the mouse, the connection immediately closes. Q. I’m using the web based User Application Panel tool and trying to make a
toolbar for a user, but when I select the user name, I receive the message “Error: No user name selected”. Networking
Q. I’m having some connection problems that may be caused by my network. What tests can I run to eliminate the various possibilities?
Q. Where can I find the patch for the GL+ 24-bit mode?
Q. How can I start a ThinAnywhere session?
Q. I’m attempting to connect to Windows desktops using RDP and I’m getting errors from t-connect. What could be the problem?
Q. I have some disconnected sessions that I would like to kill, where can I do that?
Linux Server
Q. How do I access help for the ThinAnywhere client
software?
A. To access help for the ThinAnywhere client software, start the ThinAnywhere client software. When the
“Session Login” window appears, notice that on the right side of the title bar there is a button with a “?“. Simply
click on the “?” button and then click on the word “ThinAnywhere” directly below. This will open a “ThinAnywhere
Client Help” window. You can choose from a list of help topics or click the “Index” tab and search for a topic.
ThinAnywhere session?
A. To access “Collaboration Help” while you are in a ThinAnywhere session, press the “Shift + F1” keys.
To close the help window, click “Ok”.
Close the help window before trying to execute any of the keystroke commands or they will have no effect.
A. The following are shortcut keystrokes that you can use during a ThinAnywhere session.
Some keystrokes are only valid for Originators.
— Displays help dialog including Session I.D.
— Disables collaboration input. (Originator only.)
— Disables and or disconnects collaborator. (Originator only.)
— Enables collaboration input. (Originator only.)
— Enables collaboration for this session. (Originator only.)
— Displays close dialog.
— Enables Local Mode.
— Invert cursor colors. Allows viewing of cursors that blend into background.
— Displays Session Statistics dialog.
— Toggles Full Screen mode. Session must be started in full screen.
— Displays close dialog.
A. To login on a ThinAnywhere server, open the ThinAnywhere client software on the remote computer and from the Session Login screen:
1. Enter your
user nameand
password.
2. Enter the
address of the ThinAnywhere server
you want to connect to.
3. Enter the
.
4. Enter the
. The Server Code is an optional parameter that acts much like another password for the server.
Not all servers will make use of a server code.
5. Select the
of your internet connection.
6. Choose your
settings.
7. Click the “
” button to start the connection process.
At this point a connection will be established to the server. If you fail to connect to the server, please contact
your ThinAnywhere Network Administrator to confirm the login information you have entered is correct.
so I don’t have to keep entering the same information into the session login window?
A. Yes, you can save the parameters for any session that you originate by saving the session’s “.iip” file.
Here is how you save a “.iip” file:
1. Login on the desired application server using the ThinAnywhere client. For example, you may want to login on
System 8 using a display of 24 bit true color.
2. After the session has been established, click the icon on the left side of the title bar of the ThinAnywhere window
and choose “
“.
3. Name the file (Example: sys8_24bit_truecolor.iip) and click “
“.
By default the file will be saved to the “My Connections” folder inside the “My Documents” folder on your windows
machine. You may want to make a link on your desktop for the connections that you most frequently use.
4. When you want to connect again to System 8 using 24 bit true color, simply double click the
“sys8_24bit_truecolor.iip” icon and you will automatically be logged in using the saved session parameters.
A. Connectivity to a Microsoft Server is built into the software
via RDP and configurable through the “Advanced” button on the client. Please follow the steps below:
1. Fill out the Session Login screen in the normal manner.
2. Click on the “
Advanced” button and select the “
RDP” tab.
3. Select the “
” box.
4. Select either “
” or
specify the width and height of the window.
5. Enter the
and
host I.P. of the Windows system you are connecting to.
6. To start a specific program on the Windows system, enter the complete path and program name using a “/” forward
slash in the path. When you close the program the ThinAnywhere connection will exit.
A. The XDMCP X Display Manager, Control Protocol is a convenient method for connecting to other local UNIX systems
via Xdm on the LAN. It provides a graphical login mechanism similar to logging into the console.
1. To use XDMCP, start the ThinAnywhere client and fill out the Session Login screen with the same parameters as you
would to connect to a ThinAnywhere server.
Remember that all connections, even to local UNIX servers, still go through the ThinAnywhere server.
2. Click on “
” and select the XDMCP tab.
3. Click on the “
” pulldown menu and select either “
query“, which gives a direct login on the local UNIX system or
“
” which will display a “
chooser” program from the local UNIX system.
4. In the “
” box, enter the I.P. address or host name of the local UNIX system you want to connect to.
5. The “
” address should be the I.P. address of the local interface of the ThinAnywhere system.
If the ThinAnywhere system is not being used in a multi-homed configuration, the “From” address will not be
needed. If the ThinAnywhere system is configured with multiple interfaces, this feature will allow ThinAnywhere to
connect to UNIX systems that span multiple networks. You may need to ask your system administrator for this
parameter depending upon the configuration.
6. Click the “
” and “
Ok” buttons and then click “
Connect“.
When the connection is made, you will be greeted with either a direct login on the local UNIX system or a chooser program generated from the local UNIX system.
If a login does not appear after the connection is made, probable causes are:
1. The “Host” address is invalid.
2. The “From” address is invalid.
3. The local UNIX system has XDMCP turned off or is not configured. Most SUN and SGI systems are turned on by
default and need little if any configuration.
4. A firewall is blocking XDMCP requests. (port 177)
5. The SUN or SGI system is not on the same network or there is no route between these systems and the ThinAnywhere
server.
Is there any way to start an XDMCP session using a Linux or UNIX client?
A. We are sorry, but the Unix / Linux clients don’t support XDMCP from the session login GUI at this time. There is
a work-around however, if you have a Windows client available.
1. Login on the desired application server using the Windows client and XDMCP.
2. After the session has been established, click the icon on the left side of the title bar of the ThinAnywhere window
and choose “
“.
3. Name the file (Example: xdmcp_sys5.iip) and click “
“. The file will be saved to the “My Connections” folder
inside the “My Documents” folder on your windows machine.
4.
Start the ThinAnywhere client with the “.iip” file as the first
argument.
ThinAnywhere Linux TAW client 6.0 release?
A. There is another client on our web site that includes OpenMotif. That is the one you need. Remove the client
that you are using now and install the other client. It is at the following Web address:
http://www.thinanywhere.com/downloads/clients/thinanywhere_om.gz
A. Collaboration is a convenient and powerful tool available through the ThinAnywhere server. The following steps will
walk you through the steps of establishing a collaboration session.
1. Ask the prospective collaborator to open the ThinAnywhere client software on his computer.
2. If the collaborator has an account on the ThinAnywhere server, he will enter his “
” and “
Password“.
(For any collaborator who is outside of company security, we suggest that you set up a generic collaboration account on
the ThinAnywhere server and give the collaborator the “User Name” and “Password” for the generic collaboration account).
3. Give the collaborator the “
” and “
Port Number” of the ThinAnywhere server.
4. The collaborator must enter the “
” of the ThinAnywhere session he will be connecting to.
(The Session ID Number is found in the title bar at the top of the ThinAnywhere window. Example: SID:1234).
5. If the ThinAnywhere server has a “
“, it must be entered by the collaborator.
There is no need for the collaborator to set the “Bandwidth” or “Display” parameters for the session; they will be
picked up from the original session.
6. Click “
.
When the collaborator clicks the “Connect” button on the ThinAnywhere client, the session originator will receive a
popup request in his session. The session originator must “Grant” permission for the collaborator to enter the
session before the request times out.
Normally, the display information is picked up from the original session, but when using either
“8/24 bit-Multimode” or “GL+:8/24 bit-Multimode”, it is best for the collaborator to select this parameter before
connecting.
Go back to the top
is larger and almost too big to use. Is there something I can set to make things more manageable?
A. It sounds like you have a conflict in the screen resolutions between the Windows client machine and the
application server.
on the desktop of the Windows client machine to access the “
Display Properties“
and go to the “
” tab. Set the “
Screen Resolution” to at least
1024 x 768and the “
Color Quality” to
32 bit.
Now when you start a new ThinAnywhere session, in the “Session Login”, set the “Display width and height to
. When you login, everything should look fine.
Go back to the top
to a scalable window?
A. After you have established a full screen ThinAnywhere session, you can toggle between the
full screen and a scalable window by pressing the “Atl + Enter” keys.
The session must be established as a full screen session for the toggle option to function. The user cannot
establish a session with a defined window and then toggle into a full screen display.Go back to the top
screen client computer?
A. ThinAnywhere servers support dual screens by allowing for double-width sessions. When you open the ThinAnywhere
Client to start your session, set the display height to it’s normal size and set the width to double the screen size.
A scrollbar will allow you access to the entire server area.
A. In the output of “lspci” find the two lines that represent each card’s PCI address. The odd thing with an FX4500x2 is that one card is seen as a “VGA compatible controller” (as usual) and the other is a “3D controller”. (In the case of two separate cards, they may both be seen as the same type of device.)
. . 0a:00.0 VGA compatible controller: nVidia Corporation: Unknown device 029f (rev a1)
. . 0b:00.0 3D controller: nVidia Corporation: Unknown device 029f (rev a1)
In either case, we know the addresses are “0a:00.0” and “0b:00.0”.
Next, edit the XF86Config file (or xorg.conf if on RHEL 4.x / RHEL 5.x).
NOTE: The config file expects addresses in decimal (not hex) and uses all colons instead of colons and periods.
. . 0a:00.0 becomes “PCI:10:00:0”
. . 0b:00.0 becomes “PCI:11:00:0”
Make the following changes to the config file. Notice there is a new Device and Screen section (in blue). Other changes are in red.
When X is restarted, it will have :0.0 on one card and :0.1 on another.
. . Section “ServerLayout”
. . . . Identifier . . . . . . “PCI”
. . . . Screen . . . . . 0 . “Screen0”
. . . . Screen . . . . . 1 . “Screen1” RightOf “Screen0”
. . . . InputDevice . . . .“Mouse0” “CorePointer”
. . . . InputDevice . . . .“Keyboard0” “CoreKeyboard”
. . . . InputDevice . . . .“DevInputMice” “AlwaysCore”
. . EndSection
. . Section “Device”
. . . . Identifier . . . . . . “Videocard0”
. . . . Driver . . . . . . . .“nvidia”
. . . . VendorName . . “nVidia”
. . . . BoardName . . . “nVidia FX4500x2”
. . . . BusID . . . . . . . .“PCI:10:00:0”
. . . . Screen . . . . . . . .0
. . EndSection
. . Section “Device”
. . . . Identifier . . . . . . “Videocard1”
. . . . Driver . . . . . . . .“nvidia”
. . . . VendorName . . “nVidia”
. . . . BoardName . . . “nVidia FX4500x2”
. . . . BusID . . . . . . . .“PCI:11:00:0”
. . . . Screen . . . . . . . .0
. . EndSection
. . Section “Screen”
. . . . Identifier . . . . . .“Screen0”
. . . . Device . . . . . . . “Videocard0”
. . . . Monitor . . . . . . “Monitor0”
. . . . DefaultDepth . . .24
. . . . Option . . . . . . . “SLI” “Off”
. . . . SubSection . . . .“Display”
. . . . . . Depth . . . . . . 24
. . . . . . Modes . . . . . “1280×1024” “1024×768” “800×600” “640×480”
. . . . EndSubSection
. . EndSection
. . Section “Screen”
. . . . Identifier . . . . . .“Screen1”
. . . . Device . . . . . . . “Videocard1”
. . . . Monitor . . . . . . “Monitor0”
. . . . DefaultDepth . . .24
. . . . Option . . . . . . . “SLI” “Off”
. . . . SubSection . . . .“Display”
. . . . . . Depth . . . . . . 24
. . . . . . Modes . . . . . “1280×1024” “1024×768” “800×600” “640×480”
. . . . EndSubSection
. . EndSection
Lastly, to use both cards in ThinAnywhere, make the following change to the [Xiip] section of /opt/IIPServer/bin/iip.ini:
. . [Xiip]
. . HWDisplay . . :0.0 :0.1
That’s it. (Please be sure the console X-server is restarted or the machine rebooted.)
Go back to the top
A. If you are running the RedHat 3.XX or 4.XX OS, the problem may depend on the level
of the “SELinux” security that you set when installing the OS. Changing the level of that security may
allow XDMCP to connect properly. To change the security level, do the following.
Edit “/etc/selinux/config”
Find the line:
SELINUX=enforcing
Change it to:
SELINUX=permissive
Then reboot. That should fix it.
Go back to the top
A. The following table shows the DLL to use for each possible combination of client and server.
Direct Send
RDP . . . . . . . . . . . . . . . rdp-dll/OpenGL32.DLL . . rdp-dll/x64/OpenGL.DLL
ICA . . . . . . . . . . . . . . . . .ica-dll/OpenGL32.DLL . . (not supported)
Not using Direct Send . . rdp-dll/OpenGL32.DLL . . rdp-dll/x64/OpenGL.DLL
(do not install client- . . .(set NoDirectSend=true) . (set NoDirectSend=true)
side plug-in)
On some networks, Direct Send may not be necessary. When not using Direct Send, you can install the RDP 32-bit or 64-bit DLL. This will allow ICA sessions to run 64-bit applications with ThinAnywhere (just without Direct Send).
Go back to the top
A. This message is generated when the login name, password or server code is invalid or the user does not exist
on the ThinAnywhere server.
A. This message is generated when a TCP/IP connection has been broken between the client and the server.
When the server detects a broken connection, the default behavior is to save the session on the server. Simply re-connect to
the server and select the saved session.
Go back to the top
A. This message is generated when a ThinAnywhere client is unable
to contact a ThinAnywhere server.
Causes may include but not be limited to the following:
1. A personal firewall on the remote client computer may be blocking the client software’s
access to the internet.
2. A firewall on the network where the ThinAnywhere server resides blocking the client
software’s access to the ThinAnywhere server.
3. The client network is blocking outgoing TCP\\IP traffic on port number 27500.
4. The client computer requires a proxy for out-bound traffic.
5. The ThinAnywhere server is down.
6. The client computer is not on the network or networking is not available.
Go back to the top
A. This message is generated for one of the following reasons.
1. The Originator pressed the “Deny” button when requested to accept the collaborator.
2. The Originator did not press the “Grant” button in the allotted time.
3. The Originators session is in “Disable Collaboration” mode. Ask the Originator
to type “Cntrl+Shift+F3” to enable collaboration.
Go back to the top
A. This error is generated when you request more colors for a ThinAnywhere display than your Windows desktop can provide. If this happens, the client will automatically select the correct visual class that your desktop can handle. To change your available colors on your desktop, right click on your desktop and select Properties. Click on the “Settings” tab and under the “Colors” pull-down, select the desired amount of colors.
When the server dete.
Go back to the top
iipadmin: Error: Connect status: 9.
A. Edit the “iip.ini” file found in the “/opt/IIPServer/bin” directory and add the lines listed below. Insert them as a
new section below the [AccessList] section. Replace the words “ip_address…” with the proper IP addresses described.
Example:
[AccessList]
[RemoteControlHosts]
ALLOW 127.0.0.1
ALLOW ip_address_of_this_thinanywhere_server
ALLOW ip_address_of_admin_tool_web_server
Go back to the top
with ThinAnywhere?
A. If you are runnung a version of the ThinAnywhere server software earlier than 7.46, there is a need to set some variables. Here are the additional variables necessary to make GeoProbe work with ThinAnywhere:
setenv GEOPROBE_USEGLX …………………………………. 1
setenv GEOPROBE_FRAGMENT_PROGRAM_TYPE … UNSUPPORTED
setenv GEOPROBE_VERTEX_PROGRAM_TYPE …….. UNSUPPORTED
setenv GEOPROBE_COLOR_TABLE_TYPE ……………. TEXTURECOLORTABLE
Customers using GeoProbe should insert these lines into their GeoProbe start-up script or set them in the environment.
Go back to the top
Q. I’m having font problems when I run OpenWorks. What can I do?
A. OpenWorks is looking for a font that is not on the OS where OpenWorks is running and it is pulling in a default font.
Here is a test for you to try.
The commands below should be run in an x-terminal on the ThinAnywhere server.
Enter this command
Look for a font path that ends with “the system name where the Landmark application is/:7100” If there is one with
this syntax we need to change it. If there is not one at all, we need to add a font path.
In either case, enter this command
Then restart OpenWorks.
Go back to the top
“This machine does not support GL”. Is there something I can change to make this work?
A. Try setting the environment as follows, before actually starting VoxelGeo.
A. We suggest you contact support@thinanywhere.com before changing
the Host Name.
Any change of the server name or IP address requires that you relicense the server and run “ipreconfigure”.
1. Put the host name on the same line as “
” in the
/etc/hosts file.
2.
the ThinAnywhere server.
3.
and answer “
yes” at the prompt.
4.
A. Windows Client
Whenever you start a session or reconnect to a disconnected session, please click on the ThinAnywhere icon in the upper left corner of the session window.
Select “Toggle Int’l Keyboard Support”. This will put your keyboard in the correct mode.
If your server software is earlier than the 7.86 version, please edit the “taw.ini” file or the “.iip” file for that server in the “My Connections” folder.
Locate the line:
#KeyMapNumber 0
Remove the “#” from the beginnig of the line and then save the changes to the file.
If the Line “KeyMapNumber 0” does not exist, it can be added to the end of the [Viewer] section in the “taw.ini” file or the [IIP Client] section in the “.iip” file.
Now when you login, the old keymap will be used.
Edit the “taw.ini” file in the “taw” directory that is in the users home directory on the Linux server.
Locate the line:
#KeyMapNumber 0
Remove the “#” from the beginnig of the line and then save the changes to the file.
Now when you login, the old keymap will be used.
If the “taw.ini” file does not exist in the “taw” directory that is in the users home directory, please contact ThinAnywhere Support.
Go back to the top
license doesn’t work, what can we do?
A. Please contact support@thinanywhere.com
Once you have contacted support and received an answer, you may need to re-license your server.
Here is how to activate your license on the server:
Make sure the ThinAnywhere server has Internet access.
Login as “
“
If your server licensing includes additional 5 user packs,
DO NOTexecute the following command.
Please contact ThinAnywhere Support. Execute: :> license.taw(This will remove
EVERYHTING from the license file)
Fill in
User Name, Password,and
User ID fields.
From the “
” menu, select the type of license that you have purchased.
Click “
” and wait for response.
Click “
” when complete.
Starting ThinAnywhere from the licenses directory:
for how long. How can this be accomplished?
A. Here’s how to turn on logging:
Edit the “
iip.ini” file, under the
[iIPLogin] section, set the following:
This will log each time a user logs on or logs off. The log file will be identified by the “LogFile” line. It is
usually at “
“. You can print this file to get the information you need.
If you have a very old version of the server (3.06 or older?), this may not work.
Go back to the top
When we try to login the connection doesn’t complete.
A. The problem is, the x-server is not being started when the server is booted or restarted. This can be remedied by
editing the “Xsetup_0 file… Here’s how.
1. Login on the server as “
root“.
2. Edit the file
3. Add
xhost + as the first exacutable line in the file and save the file.
4. Reboot the ThinAnywhere server.
Now you can login.
Go back to the top
server. When I start a session, the connection is completed but nothing appears in the ThinAnywhere widnow. Then, when
I move the mouse, the connection immediately closes.
A. It appears that you have an older device driver for your video card and need to do an update.
Please go to http://www.nvidia.com/content/drivers/drivers.asp
to find and install the latest version of the device driver for your video card. You will be looking for the
Linux IA32 version of the driver. At the time this page was published, the most recent Linux Display Driver – IA32
was Version: 1.0-6111.
Go back to the top
toolbar for a user, but when I select the user name, I receive the message “Error: No user name selected”.
A. This will occur with the RedHat 9.0 Opperating System. Please download the following patch to the “tmp” directory on the ThinAnywhere server.
To install the patch,
Execute: tar zxvPf tawuap_rh9uapd.tgz
This will install the file in its correct location. Now you can add your new toolbar using the web based User
Application Panel tool.
Go back to the top
Q. I’m having some connection problems that may be caused
by my network. What tests can I run to eliminate the various possibilities?
A. Here are some tests that you can use.
1. Check to see that only “eth0” is operational:
If both eth0 and eth1 are showing, then you may have a conflict again.
Running “
” will fix the problem
temporarily, but to force it to not come up at boot, it is necessary to edit the file “
“
and change “
” to “
ONBOOT=’no’“. Also, verify that the “
inet addr:” and “
Mask:” values for “eth0” are correct.
2. Verify that the firewall is off:
The output should be three lines as follows:
Chain input (policy ACCEPT):
Chain forward (policy ACCEPT):
Chain output (policy ACCEPT):
3. Check the routing tables with the command: “
“
The default route is listed under the line starting with “
” and should have the router IP address under
“
” and a Genmask of “
0.0.0.0“. The device (Iface) should be “
eth0“.
4. Verify that you can ping the following addresses:
ping {LAN Address of TAW server}
ping {default gateway}
ping {Your DNS}
5. Check to see that the TAW server software is operational
Run this as root. It should show that the number of user licenses are available.
6. Try to log into the TAW server locally
This is a Linux copy of the TAW client. Use “
localhost” as the IP address. The user should be “
taw” and the
password “
“. Select 8-bit pseudo color to be sure that local X-server supports the color depth.
7. Try to log into the TAW server from the LAN. Load the TAW client on another machine on the LAN and login using
the TAW server’s LAN address.
8. If #7 fails, try to contact port 27500 on the TAW server by using telnet.
TAW software does not respond to telnet requests, but you should get a socket connection and a message like
“Connected to…”.
Use [Cntrl] – “]” [Enter] to break out of most Unix/Linux telnet sessions and type “quit” at the telnet prompt.
Go back to the top
A. Please contact support@thinanywhere.com to update your server software to the latest release.
later?
A. Yes, ThinAnywhere server supports the ability to disconnect and reconnect sessions.
Disconnecting a session is a powerful feature that allows you to leave your jobs and processes running on
the server and at a later time, reconnect from another location. This is accomplished by simply clicking on the
“Disconnect” button when you exit your ThinAnywhere connection. When you select “Disconnect”, your complete session
will be saved on the ThinAnywhere server along with all processes, telnet and rlogin sessions, and programs that were
started in that session that are currently running. The session is not frozen or suspended, but still
active and you have simply disconnected from an active session. This also implies that disconnecting will not free
up a license that is used by a 3rd party program. A user can have multiple disconnected sessions on the ThinAnywhere
server.
A disconnected session still requires a ThinAnywhere license.
To reconnect to a session, simply login to the server and a dialog list box will appear displaying a list of
disconnected sessions that are owned by you. The sessions will appear in ordered by session I.D. and start time.
Highlight the session that matches your old session I.D. and click the “Select” button. If a selection is not made
within 10 seconds, the oldest disconnected session will be automatically selected.
errors from t-connect. What could be the problem?
A. This sounds like you are connecting to a machine that uses RDP5 (t-connect is only RDP4). You just need “rdesktop” 1.3.x.
Please download and install the following on the ThinAnywhere server:
http://www.thinanywhere.com/updates/misc/rd.tgz
Then run “
tar zxvPf rd.tgz“
This will overwrite the t-connect and tconnect3b modules with a new version.
It may have a color issue when using 8-bit color.
A. Make sure you have turned on the remote connectivity on your Windows XPpro machine:
Click the “
Start” menu and choose “
Control Panels” then “
System”. In the System panel, choose the “
Remote” tab and put a
check mark to enable“
Remote Desktop”. Then save your changes.
We also have a newer version of t-connect available than the one you may be using on your ThinAnywhere server. You can access the new t-connect by going to:
http://www.thinanywhere.com/updates/
Download the file “
rd.tgz” to the ThinAnywhere server.
To install “
”.
This will put everything in its place automatically for you.
can I do that?
A. You can kill any session using the “tawadmin” program. To access the “tawadmin” program on the ThinAnywhere server,
login as “root“. If you are on a desktop on the server, open a terminal and do the following,
This will open the “tawadmin program.
The ThinAnywhere Login Statistics window will look similar to this
—— ThinAnywhere Login Statistics —— Sys8 Release 6.10
Commands: h = Help Screen, t = Toggle Screen, s = Seconds to update,
. . . . . . . . . . . .d = Disconnect, k = Kill Session, q = Quit
User . . . Login – Time . . . .. S. Disp. S-ID Type ShmID …. . Peer-Address:Port
dan3 . . 10/22/04 11:03:28 C. :30. . 1885 . O .. 52920331 192.178.1.156:3719
dan3 . . 10/22/04 14:29:09 C. :31. . 1885 . C .. 94351084 192.178.1.156:3952
bob2 . . 10/24/04 10:25:13 D. :32. . 1425 . O .. 26375237 192.178.1.148:4273
Available licenses: 12
Mon Oct 24 13:42:28 2004
The table heading “S” indicates whether a session is Connected “C” or Disconnected “D”.
The table heading “S-ID” indicates the Session ID Number.
The table heading “Type” indicates whether the user is the session Originator “O” or is a Collaborator “C”.
To kill a session, enter “
” and hit “
Enter“.
To kill the disconnected session of user bob2,
and hit “
Enter“.
To exit the “tawadmin” program, enter “
“.
If the session is still hung, do the following.
As “root” user, run the “tawadmin” executable and find the “ShmID” value for
the session that is hung.
Run (also as root) the command “ipcs -a | grep {shmid}” where {shmid} is the
shared memory segment ID for that hung session.
If it exists, check the number on the far right. It should be zero. If so,
remove the hung session with the following command:
ipcrm -m {shmid}
A. For Windows, GNOME and KDE:
1. Turn off show contents of a window while being moved across the screen.
2. Make the desktop background a solid color.
1. Turn off all animated applets on the desktop including the flashing icon for up2date.
2. Turn off the mini view of the desktop in the tool bar at the bottom right of the screen.
A. On the Windows server, edit the “taw3d.ini” file (ThinAnywhere 3D configuration File). You can lower the “QualityAdjustment” value. This will change the compression and will only lower the quality of the image during animation, zoom, etc. but will also lower the bandwidth usage. That will help performance.
The value for the lowest quality is -17 and the for the highest quality 17 is the value. You can play with the value until you get the results you like best.