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.




Xdmcp: Manager unwilling: Host unwilling

The error Xdmcp: Manager unwilling: Host unwilling that is displayed in X-Win32’s Messages window when you start an Xdmcp session means that the remote X Display Manager (e.g. xdm, kdm, gdm, etc.) is not allowed to manage an Xdmcp session for your machine. Typically you have to edit the Xaccess file in order to allow your host to connect.

Allowing all hosts to connect via Xdmcp

  1. Find Xaccess used by your display manager (typically this is located in /etc/X11/xdm)
  2. Edit the Xaccess file
  3. Find the line
    # * #any host can get a login window
  4. Uncomment the line, changing it to
    * #any host can get a login window
  5. Save the file
  1. Restart your X Display Manager by dropping to runlevel 3 then raising back to runlevel 5 (e.g. init 3 followed by init5), or run /etc/init.d/xdm restart on some Linux systems (SuSE, Debian, Ubuntu, etc.)

    Category:Errors
    Category:Sessions -> Xdmcp