topic DECwindows applications can't access server over TCPIP in Operating System - OpenVMS

DECwindows applications can't access server over TCPIP

Galen Tackett — Mon, 17 Jan 2005 08:31:09 GMT

I am running VMS V7.3 and DECwindows V1.2-6 with TCPware V5.6.

On the VMS side I have done
$ SET DISPLAY/CREATE/SERVER=ip_addr/TRANS=TCPIP

and on the Unix server box I've done

% xhost +.

I am able to use various TCP/IP applications between the two systems. But DECwindows applications all give me the familiar message that they can't access the server, as you'd see if the server's security were not set right.

HOWEVER, I can tell that the VMS side has not even tried to contact the server as TCPware's send and receive counters are not incrementing. Tcpdump also doesn't show any traffic between the client and server. This is true even if I direct the display to 127.0.0.1. (The VMS box has no graphics hardware but it ought to exchange a few X transport messages with itself, shouldn't it?)

I must be missing something but I have no idea what it might be.

Re: DECwindows applications can't access server over TCPIP

Martin Kirby_1 — Mon, 17 Jan 2005 08:44:35 GMT

Try:

SET DISPLAY/CREATE/NODE=ip_addr/TRANS=TCPIP

/NODE gives the host address
/SERVER gives the server at that address

Martin Kirby

Re: DECwindows applications can't access server over TCPIP

Ian Miller. — Mon, 17 Jan 2005 09:01:44 GMT

is the TCPIP transport available?

this global symbol sould include TCPIP
$ decw$server_transports

and can be defined in SYS$COMMON:[SYSMGR]DECW$PRIVATE_SERVER_SETUP

Re: DECwindows applications can't access server over TCPIP

Martin Vorlaender — Mon, 17 Jan 2005 09:11:39 GMT

Galen,

to clarify the other Martin's response:

>>>
/NODE gives the host address
/SERVER gives the server at that address
<<<

/SERVER and /SCREEN refer to the X server number and screen number, respectively (the "normal" syntax is node:server#.screen#).

cu,
Martin

Re: DECwindows applications can't access server over TCPIP

Galen Tackett — Mon, 17 Jan 2005 09:37:35 GMT

Sorry, I typed in the SET DISPLAY command above from memory and just typed it wrong. I did the right thing on my actual system as Martin and Martin have indicated.

I did edit DECW$PRIVATE_SERVER_SETUP.COM to enable TCPIP as a transport. I wasn't certain that this was necessary on the client side if it is not running as a server as well, but I made the edit anyway.

I will check DECW$SERVER_TRANSPORTS when I get home today to see if it includes TCPIP--assuming that it is defined on a system that has no graphics card and isn't running a DECwindows server process.

Re: DECwindows applications can't access server over TCPIP

Martin Kirby_1 — Mon, 17 Jan 2005 10:28:44 GMT

DECW$SERVER_TRANSPORTS and the server set-up shouldn't matter on a client system.

Any firewalls in the way?

Try connecting from the client system to the server system on port 6000 using something else (eg., traceroute, telnet), to separate DECwindows from network issues.

Check the correct SYS$LIBRARY:DECW$TRANSPORT_TCPIP or SYS$LIBRARY:DECW$TRANSPORT__TCPIP image is present, I don't know if TCPware might change it.

If you run DECW$EXAMPLES:ICO exactly what message do you get?