Displaying X app's on PC from Tru64 Unix V5.1 failing (used to work!)

From: cknorr <cknorr_at_hops.com>
Date: Tue, 22 May 2001 17:49:15 -0400

We use a PC X-windows package called eXodus. The package lets you create a
full-blown xdm session to an X-windows client or just run an individual
command - /usr/bin/X11/dxterm being a personal favorite of mine.

All was well with world until a few of our machines upgraded from Tru64
Unix V4 to V5.1. I can still create xdm sessions to these V5.1 machines,
but attempting to run an individual command consistently fails with the message

eXodus was unable to open a connection to the host {ip number}
Permission denied.

The problem is 100% consistent: commands to V4 machines work; commands to
V5.1 machines don't work.

Strangely enough, if I create a dxterm to a V4 box, telnet over to a V5.1
box, and manually run the command to display it on my PC (something like
/usr/bin/X11/dxterm -display {my pc's ip number:0.0}) it works!

Anyone know of differences between V4 and V5 that might cause this? I've
noticed a few differences, like under V5 it's no longer possible to "telnet
0". Is there a pointer to documentation that might describe differences in
network behavior, including how X-windows might behave?

thanks and regards,

Chris
Received on Tue May 22 2001 - 21:51:15 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:42 NZDT