[Info-vax] DEC Windows TCPIP forwarding

[fboucher1965 at gmail.com]

On Wednesday, May 15, 2013 at 12:54:13 AM UTC-4, Andrew Armstrong wrote:
> I am having difficulties forwarding X11 on my Vaxstation 4000-90 running OPENVMS 7.3. I have the display correctly configured, and I have allowed the
>  VAX's host name using xhost on the remote machine. create/terminal results in 
> the following:
> 
> %DECW-E-CANT_OPEN_DISPL, Can't open display. 
> 
> Multinet /X11debug reports:
> 
> %X11DEBUG-I-STARTING, MultiNet X11 transport diagnostics starting...
> %X11DEBUG-S-PASSEDALL, passed all X11 tests
> 
> However, the SYS$MANAGER:DECW$SERVER_0_ERROR.LOG notes that 
> 
> DECW$TRANSPORT_COMMON image base address: 00001200
> DECW$TRANSPORT_DECNET image base address: 00887600
> %DECW-I-ATTACHED, transport DECNET attached to its network
> DECW$TRANSPORT_LOCAL image base address: 00892800
> DECW$TRANSPORT_TCPIP image base address: 00894A00
> %DECW-W-ATT_FAIL, failed to attach transport TCPIP
> -SYSTEM-F-NOLOGNAM, no logical name match
> 
> Wireshark also reports no activity from the VAX using any X11 based protocol 
> with the exception of XDM, which establishes a session, but does nothing.
> (Which makes sense, considering that multinet probably contains the 
> connection side, and gets everything else from DECWINDOWS)
> 
> Now, this machine previously had UCX installed on it, which I uninstalled 
> because I can never manage to get it to work correctly with regards to DNS 
> resolution. My best guess is that there is some esoteric configuration file 
> that still has the UCX values that is screwing up X11. Is there a way to get
> a more verbose output, and actually find the logical that's causing it to 
> choke? Other then that, where would the most likely trouble spots be?

I got the same problem.  The solution I found was to enable and start XDM (X Display Manager) from the config of TCPIP.  
@TCPIP$CONFIG
select server config
select XDM
select ENABLE and Start on this node.
exit
It then worked for me.

Francois Boucher