X-Win32 Knowledge Base   >   Session declined: Maximum number of sessions reached

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.




Session declined: Maximum number of sessions reached

Increase max number of sessions on Linux, no more sessions allowed

Sometimes a host will say no more connections are allowed.

XDMCP fatal error: Session declined Maximum number of open sessions from your host reached

This is usually caused by a router using NAT. The problem is the host thinks the router is a Xserver trying to connect and because several users might be connecting to the host through the router, the host stops allowing the router to open new sessions. The fix for this is to increase the Displays per host on your Linux or UNIX host.

Under Linux, this setting is in the /etc/X11/gdm/gdm.conf file and the /etc/kde/kdm/kdmrc file. Here’s the part of the file(s) you need to look at:

[xdmcp]
# Distributions: Ship with this off. It is never a safe thing to leave
# out on the net. Alternatively you can set up /etc/hosts.allow and
# /etc/hosts.deny to only allow say local access.
Enable=true
HonorIndirect=true
MaxPending=4
MaxPendingIndirect=4
MaxSessions=16
MaxWait=15
MaxWaitIndirect=15
DisplaysPerHost=2
Port=177
# Willing script, none is shipped and by default we'll send
# hostname system id
Willing=/etc/X11/gdm/Xwilling

Increasing DisplaysPerHost will allow more users to connect before this error happens.

/etc/X11/gdm/gdm.conf configures more host connections for Gnome.

/etc/kde/kdm/kdmrc file configures more host connections for KDE.

If there are too many sessions, rebooting the host will fix this problem as well. However, the problem will return once the Displays per host is exceeded again.

Category:Sessions -> XDMCP
Category:Errors



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.