[TriOx]

Do you have the Windows IP address and fully qualified hostname in the hosts file on the Irix box?

[William D]

I added it to /etc/hosts and to /etc/hosts.equiv still getting the errors when I try to bring up the X Window desktop through SSH, and XDMCP still just closes after a second.

[TriOx]

Maybe you need to enable xdmcp in your xdm-config? I made the changes here in step 1:
https://wiki.preterhuman.net/Headless_desktop

[William D]

I really have no idea what I'm doing wrong, but I tried that and still get the exact same results. I'm about ready to give up on it working.
I'm getting this on mobaxterm

[TriOx]

Don't give up, this hobby is all about perseverance and climbing to the top of the mountain or bottom of the rabbit hole, pick your favorite metaphor. I think you are close.

Try without ssh? I didn't start X through ssh. Just create a new session and choose xdmcp instead of ssh in the network sessions manager and see what happens.

https://mobaxterm.mobatek.net/documentation.html#1_2
https://mobaxterm.mobatek.net/doc/networ...anager.png

[callahan]

Okay, I think I understand now. You ssh in and then actually use the command "X"? Remote desktop doesn't work like that, because there is already an X-server running on the SGI that started at boot. What you want to do is just use that already-running X server to send stuff to your PC.

What happens if you type "nedit" at that prompt? If you want the SGI desktop experience, you can also type "toolchest" and use that to launch whatever other programs you might want to use.

Note there are likely to be a few bugs (that are most likely on the SGI side). I always get the error that the color "SGIdarkgrey" or whatever is not defined. Also, for some reason I can't figure out some programs on my Octane only work using the FVWM windowing mode (in settings, X11, middle of the screen), while they work fine on my Indigo2 and Indy.

[William D]

Ok, it tried toolchest and jot from the SSH connection and they open up. Interesting, not what I was expecting, I thought I would get the whole desktop of the Irix machine like you do when using Remote Desktop between two Windows computers. XDMP still is no joy, but if it's the same as what I'm getting through SSH...no big deal then.

[TriOx]

1) Is Windows 10 allowing the xdmcp out of the local firewall?
2) I would double check the hosts file and make sure that Irix can find the Windows box with the Windows FQDN. Also, I always leave IRIS as the hostname to start, this is a gotcha sometimes.

Yes to full desktop. It is a bit slow and 3D can nuke the session but I'll take it:

[William D]

Ok, trying to get XDMCP to work from MobaXterm to my O2 again and it still doesn't work. So I did some traffic captures.
Thoughts?

[TriOx]

Nice. The last packet, I see xdm declines the connection with "no valid address".

From the link I posted earlier:

"XDMCP does a reverse DNS lookup on the box attempting to establish the remote connection. Adding the client IP and hostname to the /etc/hosts file on your SGI X host should fix this problem. If this issue persists, you may also need to fix any incorrect entries in your reverse lookup zones on your DNS server."

On the O2, can you run 'dig -x windows_ip_here' in a terminal and see if you have anything listed after PTR? If there is nothing found then try removing the FQDN from the O2 hosts file and leave just the hostnames.

I originally had my kit on a network with DNS and good reverse zones so I needed the FQDN. Yesterday I tried a direct ethernet link from the Windows box with ICS to Fuel and in that scenario I had to remove the FQDN from the hosts file to get the XDMCP connection to work. So the two lines in my Fuel hosts file are just:

192.168.137.1 DESKTOP-ABC123 DESKTOP-ABC123
192.168.137.8 IRIS IRIS