Sponsored Content
Full Discussion: How to enable XDMCP?
Operating Systems AIX How to enable XDMCP? Post 302181559 by prichard on Thursday 3rd of April 2008 10:28:23 AM
Old 04-03-2008
You would have to have an X session running on the AIX box for xhost + to work.
For example, when I ssh from my linux box to my AIX box and run xhost + I get the same error you get: 1356-200 xhost unable to open display ""

But when I login in to the AIX box via xdmcp, open a dtterm and enter "xhost +" I get the message "access control disabled, clients can connect from any host".

This means that xhost must be run from the machine with the display connection.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

XDMCP setup

How do you verify your XDMCP setup on Sun Solaris? I am trying to establish a connection, but no XDMCP servers were found. (1 Reply)
Discussion started by: heinb
1 Replies

2. IP Networking

xdmcp and netstat

On my linux box, i run netstat -l and i see xdmcp in the list but it doesn't have LISTEN as its state, see what it shows below, I'm wondering if this might explain why i can't see it in my exceed broadcast listing of servers broadcasting on our net? My unix boxes don't show this at all. Proto ... (1 Reply)
Discussion started by: kymberm
1 Replies

3. Solaris

xdmcp on Solaris 10 x86

I recently downloaded and installed Solaris 10 on an Intel PC. I want to connect to it via XDMCP from another client. I found you can enable xdmcp as follows: Launch -> Applications -> Utilities -> Administration -> Login Screen Setup Then selected the XDMCP tab and click the box that... (1 Reply)
Discussion started by: lyonsd
1 Replies

4. HP-UX

xdmcp on HP-UX

Anybody know how to set up xdmcp on HPUX (11.0 +)? Thanks. (1 Reply)
Discussion started by: lyonsd
1 Replies

5. HP-UX

xdmcp config

hi everybody, can anyone please tell me what are things for verify to have an xdmcp connexion ton HPUX 10.20 host best regards (0 Replies)
Discussion started by: hmaiida
0 Replies

6. UNIX for Dummies Questions & Answers

XDMCP no password

Hello all, Does anyone know or have configure their system to allow no password during an XDMCP session. I' m running Redhat whit gdm manager. Thanks! (0 Replies)
Discussion started by: larryase
0 Replies

7. Solaris

How to enable solaris 9 to accept remote XDMCP

Hi, I want to enable solaris 9 to accept remote XDMCP connections. Please let me know what places i should look into and what configurations to be made. Thanks (1 Reply)
Discussion started by: 0ktalmagik
1 Replies

8. Solaris

Help: for XDMCP

Hi, Boss i have a problem about open the Graphic remote. when i used the Xmanager2.0 connect to the Sun Fire880 with Sun solaris 2.8 software. prompt to following information: XDMCP connection failed: retry? so can some body told me how the check the XDMCP protocol was enable...and the port 177... (9 Replies)
Discussion started by: surainbow
9 Replies

9. Solaris

XDMCP Error

Hi Friends, I am not able to login through X browser from Windows Machine to Sun Fire V890 server. Solaris 10 is installed on this machine. Please suggest me what changes need to be done in Solaris Server. Thanks in Advance (2 Replies)
Discussion started by: durgaprasadr13
2 Replies
XHOST(1)                                                      General Commands Manual                                                     XHOST(1)

NAME
xhost - server access control program for X SYNOPSIS
xhost [[+-]name ...] DESCRIPTION
The xhost program is used to add and delete host names or user names to the list allowed to make connections to the X server. In the case of hosts, this provides a rudimentary form of privacy control and security. It is only sufficient for a workstation (single user) environ- ment, although it does limit the worst abuses. Environments which require more sophisticated measures should implement the user-based mechanism or use the hooks in the protocol for passing other authentication data to the server. OPTIONS
Xhost accepts the following command line options described below. For security, the options that affect access control may only be run from the "controlling host". For workstations, this is the same machine as the server. For X terminals, it is the login host. -help Prints a usage message. [+]name The given name (the plus sign is optional) is added to the list allowed to connect to the X server. The name can be a host name or a complete name (See NAMES for more details). -name The given name is removed from the list of allowed to connect to the server. The name can be a host name or a complete name (See NAMES for more details). Existing connections are not broken, but new connection attempts will be denied. Note that the current machine is allowed to be removed; however, further connections (including attempts to add it back) will not be permitted. Reset- ting the server (thereby breaking all connections) is the only way to allow local connections again. + Access is granted to everyone, even if they aren't on the list (i.e., access control is turned off). - Access is restricted to only those on the list (i.e., access control is turned on). nothing If no command line arguments are given, a message indicating whether or not access control is currently enabled is printed, fol- lowed by the list of those allowed to connect. This is the only option that may be used from machines other than the controlling host. NAMES
A complete name has the syntax ``family:name'' where the families are as follows: inet Internet host (IPv4) inet6 Internet host (IPv6) dnet DECnet host nis Secure RPC network name krb Kerberos V5 principal local contains only one name, the empty string si Server Interpreted The family is case insensitive. The format of the name varies with the family. When Secure RPC is being used, the network independent netname (e.g., "nis:unix.uid@domainname") can be specified, or a local user can be specified with just the username and a trailing at-sign (e.g., "nis:pat@"). For backward compatibility with pre-R6 xhost, names that contain an at-sign (@) are assumed to be in the nis family. Otherwise they are assumed to be Internet addresses. If compiled to support IPv6, then all IPv4 and IPv6 addresses returned by getaddrinfo(3) are added to the access list in the appropriate inet or inet6 family. The local family specifies all the local connections at once. However, the server interpreted address "si:localuser:username" can be used to specify a single local user. (See the Xsecurity(7) manual page for more details.) Server interpreted addresses consist of a case-sensitive type tag and a string representing a given value, separated by a colon. For exam- ple, "si:hostname:almas" is a server interpreted address of type hostname, with a value of almas. For more information on the available forms of server interpreted addresses, see the Xsecurity(7) manual page. The initial access control list for display number n may be set by the file /etc/Xn.hosts, where n is the display number of the server. See Xserver(1) for details. DIAGNOSTICS
For each name added to the access control list, a line of the form "name being added to access control list" is printed. For each name removed from the access control list, a line of the form "name being removed from access control list" is printed. SEE ALSO
X(7), Xsecurity(7), Xserver(1), xdm(1), xauth(1), getaddrinfo(3) ENVIRONMENT
DISPLAY to get the default host and display to use. BUGS
You can't specify a display on the command line because -display is a valid command line argument (indicating that you want to remove the machine named ``display'' from the access list). The X server stores network addresses, not host names, unless you use the server-interpreted hostname type address. If somehow you change a host's network address while the server is still running, and you are using a network-address based form of authentication, xhost must be used to add the new address and/or remove the old address. AUTHORS
Bob Scheifler, MIT Laboratory for Computer Science, Jim Gettys, MIT Project Athena (DEC). X Version 11 xhost 1.0.5 XHOST(1)
All times are GMT -4. The time now is 05:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy