sam@ccsn2.uucp (Sam Moore) (02/14/90)
Did anyone have any luck implementing the gatewayd.c program that comes with Ultrix DECnet? Has anyone modified VMS DEC WIndows to use CMU TCP/IP for its transport? I am trying to get a VMS X11 application to work for our none DECnet workstations. I would rather get VMS X to transport across TCP/IP, but if the gatewayd.c program will work, then I will use it until the VMS side is fixed. Thank you Sam Moore sam@cave.ncsu.edu
herald.usask.ca (Ian MacPhedran,2B13 Eng.,4832) (02/21/90)
From article <1990Feb13.214240.1309@ncsuvx.ncsu.edu>, by sam@ccsn2.uucp (Sam Moore): > > > Did anyone have any luck implementing the gatewayd.c program that > comes with Ultrix DECnet? Has anyone modified VMS DEC WIndows to > use CMU TCP/IP for its transport? > I am trying to get a VMS X11 application to work for our non DECnet > workstations. > > Sam Moore > sam@cave.ncsu.edu It works pretty much as advertised in the README file in the same directory. The only problem is that the DECnet object name for X connections is WRONG. (And this is probably your problem also.) The DECnet object for display number # on the machine your X server is running on is actually X$X# and not X#, as said in the documentation. The line about defining the object would be: ncp set obj X$X2 file /usr/etc/xgate2 type stream default user guest (Remember to use \ to escape the $ from the shell.) While I'm writing this, I'd like to pose a query of my own. I used the reverse of this to send TCP/IP based X11 stuff to my VAXmate, which is running Version 2.2 of the DWDOS server. This works from Ultrix machines (from which I could use DECnet anyway, so this is no great win) but when I try this from other UNIX machines running X11, Release 3, the VAXmate sends back the string: ``Protocol version mismatch'' What version is it looking for? Thanks. Ian. Ian MacPhedran, Engineering Computer Centre, University of Saskatchewan. 2B13 Engineering Building, U. of S. Campus, Saskatoon, Sask., CANADA S7N 0W0 macphed@dvinci.USask.CA macphedran@sask.USask.CA macphedran@sask.BITNET
michaud@decvax.dec.com (Jeff Michaud) (02/23/90)
> The DECnet object for display number # on the machine your X server is > running on is actually X$X# and not X#, as said in the documentation. Ah, yup. At the time I wrote the program it was correct, but MIT changed to X$Xn afterwards. It's correct for an X10 DECnet<=>TCP gateway however :-))))). /--------------------------------------------------------------\ |Jeff Michaud michaud@decwrl.dec.com michaud@decvax.dec.com| |DECnet-ULTRIX #include <standard/disclaimer.h> | \--------------------------------------------------------------/
michaud@decvax.dec.com (Jeff Michaud) (02/23/90)
> > The DECnet object for display number # on the machine your X server is > > running on is actually X$X# and not X#, as said in the documentation. > Ah, yup. At the time I wrote the program it was correct, but > MIT changed to X$Xn afterwards. It's correct for an X10 > DECnet<=>TCP gateway however :-))))). To correct myself (before someone else does :-), only Xn is correct for the DECnet object name for a X10 DECnet<=>TCP gateway. The tcp port numbers for X10 would then be 5000+n (vs. 6000+n for X11). Then again, does it matter? Who's running X10 with DECnet only transport on one system and needs to gateway to an X10 with tcp transport only? Who's even running X10 at all? :-))) /--------------------------------------------------------------\ |Jeff Michaud michaud@decwrl.dec.com michaud@decvax.dec.com| |DECnet-ULTRIX #include <standard/disclaimer.h> | \--------------------------------------------------------------/