Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

XDMCP problem: One server blocks the other

2 views
Skip to first unread message

Vicente Zamora

unread,
Dec 12, 2006, 1:26:00 PM12/12/06
to

I have a Solaris 2.6 server that I am trying to replace with a newer
box which already has Solaris 9. However, when I put the newer one on
the network, I can only see that one on the XDMCP broadcast chooser.

In other words, Server6 has always been on the XDMCP chooser menu, no
problem, but when Server9 is on the network, I can only see Server9 and
not Server6 AND Server9 (as it should). When I take Server9 off the
network, Server6 comes back. I have another Sun server (Solaris 8) on
the network and it doesn't seem to be affected by this.

My question is : Is there any other configuration file (XDM related or
not) that I should be looking at?

What I have done so far:
- Checked the IP addresses: They have different IP addresses.
- Compared the Xconfig files on all Sun servers: they appear to be
identical.
- I really haven't done any changes on the XDMCP configuration on any
of the servers, so basically they are as they came out of the box.

Other info (which may or may not be relevant):
- Server9 has Gnome and CDE, but I am using GNOME. Server6 has CDE
- I am not using firewalls or any other such things within my LAN.

I am considering using another Xwindows client, right now I am using
Kea! X, but technically this should not make a difference.

I appreciate your advice,

Vince

Casper H.S. Dik

unread,
Dec 12, 2006, 1:51:10 PM12/12/06
to
"Vicente Zamora" <VEZa...@gmail.com> writes:


>I have a Solaris 2.6 server that I am trying to replace with a newer
>box which already has Solaris 9. However, when I put the newer one on
>the network, I can only see that one on the XDMCP broadcast chooser.

>In other words, Server6 has always been on the XDMCP chooser menu, no
>problem, but when Server9 is on the network, I can only see Server9 and
>not Server6 AND Server9 (as it should). When I take Server9 off the
>network, Server6 comes back. I have another Sun server (Solaris 8) on
>the network and it doesn't seem to be affected by this.

>My question is : Is there any other configuration file (XDM related or
>not) that I should be looking at?

I assuming both run dtlogin? Check the /etc/dt/config/ or
/usr/dt/config. Specifically Xaccess.

>Other info (which may or may not be relevant):
>- Server9 has Gnome and CDE, but I am using GNOME. Server6 has CDE

Are you using dtlogin to login or gdm?

Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

Vicente Zamora

unread,
Dec 12, 2006, 3:07:01 PM12/12/06
to
Thanks Casper for your prompt reply.

Both systems are using dtlogin, not gdm.

I am pasting the Xaccess file for both of them, which is the way it
came out of the box, I haven't modified it.

I really don't know what else to do, except change IP addresses, and
maybe put the new server on another port of the LAN switch, but again,
this should have nothing to do with it.

/usr/dt/config/Xaccess:
# Entries...

* # grant service to all remote displays

#
# The nicest way to run the chooser is to just ask it to broadcast
# requests to the network - that way new hosts show up automatically.
# Sometimes, however, the chooser can't figure out how to broadcast,
# so this may not work in all environments.
#

* CHOOSER BROADCAST #any indirect host can get a
chooser

#
# If you'd prefer to configure the set of hosts each terminal sees,
# then just uncomment these lines (and comment the CHOOSER line above)
# and edit the %hostlist line as appropriate
#
#%hostlist host-a host-b
#* CHOOSER %hostlist #

Casper H.S. Dik

unread,
Dec 13, 2006, 3:49:28 AM12/13/06
to
"Vicente Zamora" <VEZa...@gmail.com> writes:

>Thanks Casper for your prompt reply.

>Both systems are using dtlogin, not gdm.

>I am pasting the Xaccess file for both of them, which is the way it
>came out of the box, I haven't modified it.

>I really don't know what else to do, except change IP addresses, and
>maybe put the new server on another port of the LAN switch, but again,
>this should have nothing to do with it.


Check the netmasks on both systems; check with netstat to see if the
system is indeed listening on the appropriate ports.

0 new messages