X-Win32 Knowledge Base   >   StarNetSSH: Bad packet length connecting to Solaris 9 server

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.




StarNetSSH: Bad packet length connecting to Solaris 9 server

Solaris 9 has a bug, introduced in a patch, that breaks X11 Forwarding for all ssh clients attempting to connect to Solaris 9 using X11 Forwarding (including all versions of X-Win32). The symptom of this bug is that a connection attempt with X11 Forwarding enabled is disconnected with a bad packet length error.

Solutions

  1. Install a replacement patch from Sun: Solaris 9 SSH X11 Forwarding Patch
  2. Disable IPv6 listening for the ssh server. The IPv6 functionality contains the bug that breaks X11 Forwarding, so limiting support to IPv4 only works-around the problem for servers that do not need IPv6 support.
    1. Edit /etc/ssh/sshd_config and change
      # IPv4 only
      #ListenAddress 0.0.0.0
      # IPv4 & IPv6
      ListenAddress ::
      to
      # IPv4 only
      ListenAddress 0.0.0.0
      # IPv4 & IPv6
      #ListenAddress ::
    2. Edit /etc/init.d/sshd and change
      [ -x /usr/lib/ssh/sshd ] && /usr/lib/ssh/sshd &
      to

      3. [ -x /usr/lib/ssh/sshd ] && /usr/lib/ssh/sshd -4 &
    3. Restart the daemon using the init.d script.

      Category:FAQ
      Category:Sessions -> SSH



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.