Can't log into remote desktop XDMCP

[caveman]

I've got a home network with a few machine running various releases of
Solaris 10.

Blade 2000: fixed IP 192.168.0.9 (Solaris 10, update 4)
Laptop: dynamic IP 192.168.0.x (Solaris x86, Developer Edition)
Ultra 60: on a different subnet 192.168.1.15 (Solaris 10, update 2)

If a machine is rebooted and one sits at the console, the default is to
log into the local host. But one can can select a remote host from:

Options -> Remote Host -> Enter host name

I have used this years ago, but for reasons I can't work out, it is not
working.

The laptop cant get a remote desktop of the Blade 2000 and the Blade
can't see the laptop. These are networked OK - either machine can SSH to
another. The error message generated is something like this

"Remote host could not be accessed. The remote host name is valid, but
the remote host may not be running dtlogin (or other X display manager)."

But dtlogin is running - see ps output below.

kestrel / % ps -elf | grep dtlogin
0 S root 567 536 0 40 20 ? 1311 ? Dec 16
? 0:01 /usr/dt/bin/dtlogin -daemon -udpPor
0 S root 536 1 0 40 20 ? 772 ? Dec 16
? 0:00 /usr/dt/bin/dtlogin -daemon -udpPor
0 S drkirkby 3915 3880 0 50 20 ? 161 ? 04:45:53
pts/4 0:00 grep dtlogin

I'm entering the IP address, not asking the machine to resolve the
hostname, so I'm puzzled why it is not working.

There is only a simple switch between these machines. One has a
firewall, but I've disabled that and still it does not work.

Any suggestions?

[Marc]

caveman wrote:

> I've got a home network with a few machine running various releases of
> Solaris 10.

[...]

> The laptop cant get a remote desktop of the Blade 2000 and the Blade
> can't see the laptop. These are networked OK - either machine can SSH to
> another. The error message generated is something like this
>
> "Remote host could not be accessed. The remote host name is valid, but
> the remote host may not be running dtlogin (or other X display manager)."

Did you enable tcp listen on the X server? Did you enable xdmcp? I think
both are disabled by default now, since the secure-by-default change.

[Dave]

I've not, but how do I do this?

There appears to be nothing I can enable with svcadm

kestrel /tmp/foo % svcs -a | grep -i xdmcp
kestrel /tmp/foo %

and the only obvious tcp one is this:

kestrel /tmp/foo % svcs -a | grep -i tcp
disabled Dec_16 svc:/network/rpc/cde-ttdbserver:tcp

Is that what I need to enable?

It would be good if the error message generated about dtlogin not
running was a bit more explicit if there are other services that need to
be running.

Dave (aka caveman)

[Richard B. Gilbert]

Don't hold your breath waiting for it. Explicit error messages that
tell you what's wrong and suggest how to fix it are not the "Unix way"!
"A competent sysadmin" is supposed to be able to figure it out.

If you want better than that, and I wouldn't blame you, you'll need to
use an O/S like OpenVMS. OpenVMS doesn't tell you "file not found" and
leave you to figure it out; the message tells you the full path and
filename that could not be found. You can then supply the required
file or fix the program to look in the right place.

[Marc]

Dave wrote:

>>> I've got a home network with a few machine running various releases of
>>> Solaris 10.
>> [...]
>>> The laptop cant get a remote desktop of the Blade 2000 and the Blade
>>> can't see the laptop. These are networked OK - either machine can SSH to
>>> another. The error message generated is something like this
>>>
>>> "Remote host could not be accessed. The remote host name is valid, but
>>> the remote host may not be running dtlogin (or other X display manager)."
>>
>> Did you enable tcp listen on the X server? Did you enable xdmcp? I think
>> both are disabled by default now, since the secure-by-default change.
>
> I've not, but how do I do this?
>
> There appears to be nothing I can enable with svcadm

Google gives:

Show properties
svcprop svc:/application/x11/x11-server
Turn on tcp listen
svccfg -s svc:/application/x11/x11-server setprop options/tcp_listen = true
Then restart the X server
svcadm refresh svc:/application/x11/x11-server

[Dave]

Richard B. Gilbert wrote:

>> It would be good if the error message generated about dtlogin not
>> running was a bit more explicit if there are other services that need
>> to be running.
>
> Don't hold your breath waiting for it. Explicit error messages that
> tell you what's wrong and suggest how to fix it are not the "Unix way"!
> "A competent sysadmin" is supposed to be able to figure it out.

I see. I guess I'm not a competent system admin then! (Not that the
label worries me too much, as I don't do it for a living).

> If you want better than that, and I wouldn't blame you, you'll need to
> use an O/S like OpenVMS. OpenVMS doesn't tell you "file not found" and
> leave you to figure it out; the message tells you the full path and
> filename that could not be found. You can then supply the required
> file or fix the program to look in the right place.

It's a long time since I used VMS. I do have a Dec Alpha here, which
would run OpenVMS although it has Tru64 on it. (Not that it has actually
been powered up in the last few years, but I still have it).

Last time I looked there was some silly scheme one had to join to get an
OpenVMS license, which was free in the US, but cost a nominal figure in
the UK. Can't recall the details, but I gave up the idea.

I've actually done assmebly language programming on a VAZ in the dim and
distant past. It was such a pleasure compared to the x86 chips at the time.

[Darren Dunham]

Marc <marc....@gmail.com> wrote:
> Google gives:
>
> Show properties
> svcprop svc:/application/x11/x11-server
> Turn on tcp listen
> svccfg -s svc:/application/x11/x11-server setprop options/tcp_listen = true
> Then restart the X server
> svcadm refresh svc:/application/x11/x11-server

See also:
<http://groups.google.com/group/comp.unix.solaris/browse_thread/thread/2b0152f259b09861/>

--
Darren Dunham ddu...@taos.com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >

[Dave]

Marc wrote:

> Show properties
> svcprop svc:/application/x11/x11-server
> Turn on tcp listen

> svccfg -s svc:/application/x11/x11-server setprop options/tcp_listen = true

cheers, that seems to work.

> Then restart the X server
> svcadm refresh svc:/application/x11/x11-server

I dont have that, or a remotely similar name.

# svcadm refresh svc:/application/x11/x11-server
svcadm: Pattern 'svc:/application/x11/x11-server' doesn't match any
instances

It's clear dtlogin is using port 0, which effectivley means its disabled

# ps -ef | grep dtlo
root 532 1 0 20:32:16 ? 0:00 /usr/dt/bin/dtlogin
-daemon -udpPort 0
root 1315 532 0 21:08:58 ? 0:00 /usr/dt/bin/dtlogin
-daemon -udpPort 0

But I dont know where to set the port for it.

I copied /usr/dt/config/Xconfig to /etc/dt/config/Xconfig where I see it
says:

############################################################################
# To disable listening for XDMCP requests from X-terminals.
#
# Dtlogin.requestPort: 0

It implies one needs to uncomment that to disable it - i.e. it is
enabled. But uncommenting and putting to 177 does not help. i.e.

Dtlogin.requestPort: 177

does not help. Even after a reboot, the port is still 0.

I'm not sure if I'm supposed to edit /etc/dt/config/Xaccess, but it has:

# Entries...

* # grant service to all remote displays

so I can't see what is wrong. Anyone any ideas?

[Thomas Tornblom]

I think:

svccfg -s svc:/application/graphical-login/cde-login setprop dtlogin/args=\"\"

will do it.

It removes the "-udpPort 0", which makes it use the default port of 177.

[Dave]

Thank you, that works!

dave

[Casper H.S. Dik]

Dave <f...@coo.com> writes:

># To disable listening for XDMCP requests from X-terminals.
>#
># Dtlogin.requestPort: 0

>It implies one needs to uncomment that to disable it - i.e. it is
>enabled. But uncommenting and putting to 177 does not help. i.e.

>Dtlogin.requestPort: 177

>does not help. Even after a reboot, the port is still 0.

Have you looked at the svcprop dtlogin/args value?

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.

[Dave]

Casper H.S. Dik wrote:
> Dave <f...@coo.com> writes:
>
>> # To disable listening for XDMCP requests from X-terminals.
>> #
>> # Dtlogin.requestPort: 0
>
>> It implies one needs to uncomment that to disable it - i.e. it is
>> enabled. But uncommenting and putting to 177 does not help. i.e.
>
>
>
>> Dtlogin.requestPort: 177
>
>> does not help. Even after a reboot, the port is still 0.
>
>
> Have you looked at the svcprop dtlogin/args value?
>
> Casper

Thank you. I had got it working by the time you replied, but that was
the problem - one of the arguments set the port to 0.

Dave

[Trouble@Mill]

I'm having similar problems. I tried the command above, which then
made port 177 show up in a netstat, where it didn't before. So I'm
getting somewhere.

But, the status is "Idle", not "Listening"

I also set "tcp_listen = true", as suggested by another poster, but
still no joy. Any attempt to connect just hangs.

There are no override files in /etc/dt, and the "defaults" in
/usr/dt/config are as follows: Xaccess is set to allow any user to
connect, and Xconfig has the requestPort line commented out.

Any ideas what else I need to set to get dtlogin to start listening
for xdmcp requests.

Cheers,
Eddie

[joes...@gmail.com]

Is this Eddie from the cd3o forums??