MCSR

Xwin-32 is X Windows terminal software that you can run on your Windows 95/98/NT/2000/XP/Vista platforms. Doing so will allow you to use your PC desktop to display (serve) the user interface of any X Windows applications you may run or write on any Unix or Linux server. A common use is X terminal emulation--you can use Xwin-32 instead of telnet to connect to a server.

Licensing

Ole Miss has a 50-seat site license for the 130.74 network (that is, the olemiss.edu domain). This means that no more that 50 Xwin-32 instances maybe be up and running at any one time. Users from outside the olemiss.edu domain will probably need to obtain Xwin-32 from their own institutions, although a free evaluation copy may be downloaded from here. For more information about Xwin-32 features, please visit MCSR Parallel-O-Gram online newsletter.

Installation

To install Xwin-32 directly to your Windows system, perform the following steps:

Download and run Xwin-32 Ver. 9.5
When prompted for the serial number/license key, enter the license key information. You can get the campus license key file via the myOleMiss web portal.

For support in installing or running Xwin-32, see the FAQ below, try the online help, and check the Web site at Starnet. You may also email assist at mcsr.olemiss.edu for assistance.

MCSR/Ole Miss Frequently Asked Questions about Xwin-32

What terminal type should I use?
xterm
What connection type should I use? (ssh, rsh, rexec, LIVE or XDMCP)?
You should choose either ssh or XDMCP since rexec has been disabled on most IT/MCSR servers. If you choose XDMCP, then you should choose Query from the drop-down menu. However, if you choose ssh, the secure shell has to be installed in your computer. You may download and install the free version of SSH Secure Shell via IT Helpdesk .
What if I get the error: xterm: not found?
In your session command, include the full path name of the xterm command. For example: /usr/bin/X11/xterm If unsure of where the xterm is located, you can look for it using the whereis command. For example: $ whereis xterm
Location of xterm on MCSR machines:
- sweetgum /usr/bin/X11/xterm
- willow /usr/openwin/bin/xterm
- cypress /usr/bin/X11/xterm
What if I get the error: can't open display?
In your session command, include the -display option, followed by the IP address of your PC. Example: -display 137.74.132.42:0.0
or
-display $DISPLAY
where the DISPLAY system variable is defined (to your PC's IP Address) in your login script on the Unix/Linux server
What if I get the error: Client is not authorized to connect to server?
Under Options, XHosts, add an entry with the domain name (e.g., sweetgum.mcsr.olemiss.edu) of all remote Unix/Linux servers that might need to display X windows on your PC.
How can I change my password on sweetgum with Win32?
You can NOT change your password on sweetgum by yourself with Win32. If you want to change your password, you have to contact the IT Helpdesk.
When I try to connect to an MCSR server using this software, I get a message saying that "connection timed out" or "invalid request". Why?
If your site is behind a firewall, you may need to ask your network administrator to add an exemption entry for MCSR server of interest, so that you can connect to it across your firewall. If you cannot even ping the MCSR server, but can ping (and connect to) other servers on your campus, this is a likely cause.
When I try to launch an X Windows client session, I get the message: connection refused. I am using rexec, and everything else seems to be set up correctly. What do I do?
Connect using XDMCP (instead of rexec), and choose Query from the XDMCP drop-down menu.
When I try to launch an X Windows client session, nothing happens, and no error messages appear. Why not?
Right-Click the XWin32 icon (the blue X) at the bottom right of your display, and select Show Messages from the pop-up menu. A new window should appear, wherein will be displayed all of the messages generated from each connection attempt.
When I try to run SAS interactively on willow, connecting from my desktop PC, SAS never comes up. Why not?
You must have XWin32 running on your PC; however, that in itself is not sufficient. You must also use XWin32 to connect to willow. This will result in Solaris CDE windows materializing (slowly) on your display. You may then launch sas through a secu re shell session (after first setting the DISPLAY variable to your PC's IP address), or through an X terminal launched from the CDE File Manager Window (File->Open Terminal) (without having to explicity set the DISPLAY variable).