X-Win32 Knowledge Base   >   Xlib: connection to localhost:10.0 refused by 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.




Xlib: connection to localhost:10.0 refused by server

When you attempt to start a program via your SSH session:


Xlib: connection to “localhost:10.0” refused by server

This error indicates that X-Win32 has rejected the X Client application’s attempt to connect. There are several possible solutions to this problem:

  1. Your license may be restricting your connection and giving a Cannot Connect to a Host on a Restricted Network error. Click here for more information.
  2. Check the Use XAuth checkbox on X-Config’s Security tab, then restart X-Win32 and attempt to start your X-Win32 session and your applications again. If this does not fix the problem, proceed to the next solution.
  1. You may enable SSH applications to be authenticated by the machine that they are coming from (your local machine in this case). If X-Config’s Security tab has any entries in the X-Host list field, then you must explicitly add the host 127.0.0.1 (localhost) in order to allow SSH applications to be automatically authenticated; an empty X-Host list indicates that all hosts will be allowed (including localhost), but adding even a single entry to the list requires that you re-add the localhost entry manually. After making this change, restart X-Win32 and attempt to start your session and your applications again.

    See Also:
    Cannot Connect to a Host on a Restricted Network
    Category:Errors
    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.