Search


About StarNet

StarNet Communications has been a leading developer of X Windows solutions since 1989. After establishing X-Win32 as the de facto standard in the higher education market during the early to mid-1990s -- 150 unlimited Campus Site Licenses worldwide -- X-Win32 has become of one the top three PC X servers in the government and commercial sectors as well.

Unlike its major rivals, Exceed (Hummingbird) and Reflection-X (WRQ/Attachmate), X-Win32 offers a highly focused PC X server that offers superior performance and productivity features, stability, ease of use and low cost (40% or better in most cases).

StarNet also delivers unequaled customer support. Our state-of-the-art engineering infrastructure allows us to fix problems and make a new release available quickly (overnight in many cases). As our testimonials page shows, StarNet customers consistently rate their X-Win32 experience as the best in the industry.




Automatically configuring the DISPLAY environment variable

With X-Win32 you do not have to set the $DISPLAY environment variable in your login scripts (e.g. .bashrc, .cshrc, or .profile) on your remote UNIX, Linux, or BSD hosts (e.g. Red Hat, SuSE, Debian, Ubuntu, HP-UX, AIX, or Solaris) in order for the program in the command field of your X-Win32 sessions to work. In fact, setting this environment variable in your login scripts will most likely cause your X-Win32 sessions to work only when you connect from one of your Windows machines.

There are two different tactics for avoiding setting the $DISPLAY environment variable, depending on the type of session that you are using.

Avoiding setting $DIPSLAY for rexec and rsh sessions

  1. If your remote host is on the same network (i.e. there are no firewall or network address translation (NAT) devices between your two hosts) as your X-Win32 machine, then simply add the -display $DISPLAY command-line parameter to your X-Win32 sessions using X-Config, then remove all traces of setting $DISPLAY from your login scripts.
  2. If there is a firewall or NAT device between the two computers and the remote computer is on the public Internet, then you can use X-Win32’s IPSmart facility to find the address of your NAT device; to do this, simply add the -display $IPSMART:$DNUM command-line paramter to your X-Win32 sessions using X-Config, then remote all traces of setting $DISPLAY from your login scripts. If all of your sessions function this way, then you can instead change the address in X-Config’s Display tab to IPSmart, which will cause -display $DISPLAY to return the IPSmart address.
  1. For newly created sessions, be sure to use the Wizard button in X-Config’s Sessions tab to create each session. The Session Wizard automatically adds the -display $DISPLAY command-line parameter to new rsh and rexec sessions that start xterm or dtterm.

    Avoiding setting $DISPLAY for StarNetSSH sessions

  2. If you are not using X11 Forwarding with your StarNetSSH sessions (e.g. because it is disabled in sshd_config on the remote host), then you should first and foremost turn this feature on as it will automatically set the $DISPLAY environment variable on the remote host for you, without the need to pass -display [...] on the command-line to your sessions.
  1. If you are using X11 Forwarding with your StarNetSSH sessions but the $DISPLAY environment variable seems to be incorrect (noted by a cannot open display error when starting your StarNetSSH sessions) then you need to double-check your login scripts to be sure that they are not setting the $DISPLAY environment variable and thus overriding the value that sshd is setting it to.

    Category:Sessions -> rexec
    Category:Sessions -> rsh
    Cateogry:Sessions -> StarNetSSH




How Can We Improve This KB Article?

Please rate the quality of this article: Excellent Good Fair Poor

Did this article answer your question? If not, we'd like to hear more about it:

Do you need additional assistance? If so, enter your email address:

Articles are periodically updated based on your feedback. If you enter an email address, then you will be given the opportunity to open a case, for which you will receive a response within 2 business days.