- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Setting up XDMCP for ReflectionX
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2004 10:30 AM
06-29-2004 10:30 AM
I'm trying to setup XDMCP to connect from my windows box using ReflectionX to my RedHat9 box. I've followed the directions at http://www.ibiblio.org/pub/linux/docs/HOWTO/XDMCP-HOWTO and still cannot get it working. When I try to connect I get either "XDM session declined by host (Maximum number of open sessions from you host reached)" or something to the effect of, "please make sure you have an xdm client running."
I've installed my redhat machine to init5 and I can login directly through a x windows login prompt. Also, from Reflection I can choose from a Broadcast list of who to xdmcp into and my machine shows up. Initially it lists the name, ip, and operating system. After I try to connect to it once, nothing happens. When i pop up the list again, it now says "Server is busy." and that's when I get the too many connections message. Does anyone know what the solution is?
Thanks,
Tina
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2004 05:49 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2004 01:55 AM
06-30-2004 01:55 AM
Re: Setting up XDMCP for ReflectionX
I suppose to understand the problem more, why can't my linux box resolve other computer names. Does that mean my dns setup is incorrect?
Thanks again,
Tina
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2004 02:16 AM
06-30-2004 02:16 AM
Re: Setting up XDMCP for ReflectionX
probably.
if you windows box hostname is windows and IP=1.2.3.4, run these commands from linux:
1) nslookup windows - you should get 1.2.3.4 as answer
2) nslookup 1.2.3.4 - you should see "windows"
instead of nslookup you can use host or dig utilities.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2004 07:04 AM
06-30-2004 07:04 AM
Re: Setting up XDMCP for ReflectionX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2004 12:58 AM
07-01-2004 12:58 AM
Re: Setting up XDMCP for ReflectionX
If you are using xdm or some other xdm-inspired variant, you'll need to edit /etc/X11/xdm/xdm-config or equivalent and make sure it is listening on port 177.
lsof -c gdm or xdm should show the display manager listening on port 177 and you should see it with netstat -an | grep 177. If not, you are not configured correctly OR you have a firewall blocking incoming UDP to that port. iptables or ipchains default setup can block this. Take appropriate measures to modify those settings.