HDTenEightyP/NetNews huggingface dataset:
Newsgroups: vmsnet.networks.tcp-ip.multinet,vmsnet.mail.pmdf
Subject: New Multinet with Old PMDF - Can it be?
From: gordon@chmeds.ac.nz
Date: 7 Jan 93 18:16:25 +1200

Problem: old version of PMDF, new version of Multinet don't get on.

Situation: VMS 5.5, I just installed Multinet 3.1. We are still using
PMDF version 3. I'd like to upgrade, just now that isn't an option as we
haven't the money.  We might be able to later, but the problem is now.

Mail in fails. An opcom message from multinet server indicates that the server
failed, "service SMTP: abort" (that's all, apart from the PID).

The installation process requires that the file multinet:smtp_server.exe
be replaced with the PMDF-supplied version.  I did that; but its an old
.exe file, and may be built with an inappropriate version of the Multinet 
libraries.  Rebuilding from the PMDF distribution screws up - it wants a
file [multinet-plus.lib]lib.olb, which of course no longer exists (its an 
*OLD* version of PMDF).

The PMDF configuration file is exactly as we had for CMUTEK TCP/IP, with
the obvious change of CTCP to MTCP.

Has anyone got PMDF version 3 running with a modern Multinet? Or any 
suggestions to tide things over until we can get PMDF version 4.1?

Cheers
Gordon, terribly perplexed
---
Gordon Findlay,  Computer Scientist, Christchurch School of Medicine


Mail temporarily to chchmeds@otago.ac.nz (their system works!)
From: cherry@OPAL.MGH.HARVARD.EDU
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Question on use of POP3
Date: 10 Jan 93 15:37:49 GMT
Reply-To: cherry@OPAL.MGH.HARVARD.EDU
Organization: Molecular Biology - Mass Gen Hospital

Ever since Multinet included POP3 support I've been setting up users
with a Macintosh in their office with Eudora. However there are two
types of users for which I cannot provide Eudora and wonder if anyone
has a suggestion.

The first type of user is one that reads their mail from more than one
Macintosh. With Eudora the mail is copied and saved on the Macintosh.
There is an option to Eudora that leaves the mail on the POP3 server
but the mail is not moved out of the NEWMAIL folder so it is
continually transferred as a new message until you login on the VAX
and move the message out of NEWMAIL. So Eudora is only useful if you
always read your mail via Eudora from the same Macintosh and have the
mail transferred to the Macintosh.

The second type of user is one that reads their mail on a machine that
is shared with other users. Eudora doesn't protect the mail messages
while on the Macintosh from prying eyes. I cannot provide more than
one user per Macintosh availability to Eudora because the mail
effectively becomes publicly accessible.

The minority of my users have their own Macintosh and read their mail
from only one Macintosh, increasing numbers are reading mail from
home.  This leaves the majority of our users having to log into the
VAX just to run VMSMAIL!  Can these problems be solved? Are there
suggestions for the Macintosh that do not require PathWorks? Have I
missed something in setting up POP3?

Thanks,

Mike Cherry
Massachusetts General Hospital
cherry@frodo.mgh.harvard.edu
From: SADVARY@DICKINSON.EDU (Sadvary, Bill)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Multinet and VMS
Date: Tue, 5 Jan 93 9:33:37 est
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List


We are running MultiNet v3.1B and we will soon be upgrading to VMS v5.5-2 (VAX 
6340).

Has anybody seen any problems with these two versions running in conjunction?

The DEBNA controller problem was fixed in VMS 5.5, right?

Any horror stories from upgrading to VMS v5.4-3 to v5.5-2?

Thanks for any answers.
-Bill Sadvary
 sadvary@dickinson.edu
From: MRL@NERUS.PFC.MIT.EDU (Mark London)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Info wanted on select routine.
Date: Sun, 10 Jan 93 14:37 EST
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

I'm trying to port software written for unix to vms.  It uses the "select"
routine to wait for either network or keyboard events.  While getting the 
channel number for stdin might be hard, I think I can do it, but my initial
tests show that the routine only works for Multinet network channels.  Is this 
true, or should it work for any channel assigned by the program?  Thanks.

Mark
Newsgroups: vmsnet.networks.tcp-ip.multinet
From: mark@cda.mrs.umn.edu (Mark Van Overbeke)
Subject: EWS and VAXstations
Organization: University of Minnesota - Morris
Date: Tue, 12 Jan 1993 15:08:27 GMT

Multinetters!

   I have just gotten the EWS server software to make a VAXstation 2000
with 6 Mb of memory a little more useful.  Has anyone out there gotten
the tcp part of EWS to work?  There is nothing in the installtion
instructions or the user manual that I have about getting the tcp part
set up.  I also do not have the Ultrix part so I don't have that to
reference.  Any pointers on this would be appreciated.  This all to be
on a VMS system. (at least for now)  Thanks.

-- 
Mark Van Overbeke                   Systems Software Programmer
Computing Services                  BITNET:    Mark@UMNMOR.BITNET   (VMS)
University of Minnesota, Morris     INTERNET:  Mark@caa.mrs.umn.edu (VMS) 
Morris, MN   56267           (612) 589-6378    mark@cda.mrs.umn.edu (Ultrix)
Success is the progressive realization of your worthwhile goal or dream!
From: adelman@TGV.COM (Kenneth Adelman)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Re: Upload directory for anonymous ftp?
Date: Fri, 8 Jan 93 08:21:28 PST
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

> Is it possible to create an upload directory for anonymous ftp?

    Yes. Take a look at the DCL in MULTINET:FTP_SERVER.COM, which,
when the username is given as ANONYMOUS adds a /ACCESS=NOWRITE
qualifier.

    What we do here is have an "unload" directory that requires a
special ANONYMOUS password to access. If you comment out the
$ MULTINET FTP/SERVER/GET_REMOTE_INFO command, the logical name
MULTINET_ANONYMOUS_PASSWORD will get defined as the password the
user gave. Then you can do something like:

$ MultiNet FTP/Server/Get_Remote_Info

$ If Username .Eqs. "ANONYMOUS"
$ Then
$   If F$Edit(F$TrnLNM("MULTINET_ANONYMOUS_PASSWORD","UPCASE,COLLAPSE") -
       .Eqs. "UPLOAD"
$   Then
$	  FTPOptions = "/Directory=Users:[Incoming]"
$	  RestrictOptions = ""
$   Endif

							    Ken
From: KNEZEVICH@NOAAPMEL.GOV (Mike Knezevich)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: bootp messages
Date: Tue, 5 Jan 1993 13:31 PDT
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

Hi,

I've turned on the Multinet bootp server, and set debug to -1, but we still see 
a fair number of messages generated by bootp, primarily on account of x 
terminals whose ethernet addresses are not in the Multinet bootp file, but 
rather are served by a Unix machine which has the x terminal boot files.  
Should these messages be generated when debug is set to -1?  Can I do anything
about it?

%%%%%%%%%%%  OPCOM   4-JAN-1993 07:51:32.47  %%%%%%%%%%%
Message from user SYSTEM on ALPHA
MultiNet Server: BootP: request from hardware address 0000A710B567

%%%%%%%%%%%  OPCOM   4-JAN-1993 07:51:34.13  %%%%%%%%%%%
Message from user SYSTEM on ALPHA
MultiNet Server: BootP: hardware address not found: 0000A710B567

thanks,

Mike
From: jeffk@cdibm.fnal.gov (Jeff Kallenbach)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Re: Remote X Clients over TCP/IP onto VS
Date: 6 Jan 1993 14:50:52 GMT
Organization: Fermi National Accelerator Laboratory, Batavia IL
Distribution: world
NNTP-Posting-Host: cdibm.fnal.gov

Problem has been located.  It had to do with the 

	$ define /system decw$install_tcpip "YES"

command and with Multinet being started after DECW.  Thanks to all who 
responded, esp madison and robinson.  

As for you, Ehud, I'm sure there was a purpose behind your bile discharge, but 
you can spare me the details.  That's a private matter between you and your 
doctor.  Maybe such catharsis saves your dog a good kicking when you get home.  
Anyway, your response was certainly *extremely* helpful (not).


-- 
============================================================================
Jeff Kallenbach                       |Opinions are not neccessarily shared
Fermi National Accelerator Laboratory |by my employer.  In fact, they agree 
708-840-2210                          |with very little of what I say.
============================================================================
From: adelman@TGV.COM (Kenneth Adelman)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Re: SLIP on a LAT line?
Date: Mon, 11 Jan 93 08:38:03 PST
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

> We have started testing SLIP via Multinet.  Since dedicating a high
> speed modem to the back  of a workstation is not possible, we would
> like to use LAT connections to allow a userto dial into our high
> speed modem banks, get connected to a DECserver, connect via the
> DECserver to the machine offering the SLIP service, log in normally,
> then use the MULTINET SET INTERFACE command to convert their terminal
> line into a SLIP line.  Is this possible?

    It is possible, but not supported. If the LAT device goes away,
you could get a system crash. I believe that some of our customers have
gotten it to work by setting the terminal /PASTHRU/NOTTSYNC/NOHOSTSYNC
prior to starting SLIP on the device.

> All of my tests end up with "device cannot be connected to Multinet
> kernel" or something close to that.  I'd love to hear anyone's success
> stories with something like this.

    Can you open a service call with SERVICE@TGV.COM and provide us
with the exact text of the error you get?

							    Ken
From: simon@internode.com.au (Simon Hackett)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Re: SLIP troubles
Date: Wed, 13 Jan 1993 12:53:06 +1030
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List


> Hello,
> 
>         We are running MultiNet over SLIP (we'd use ethernet if we had
> it, but...), and are having problems with data transfer:
> 
> With ftp, small files transfer okay, but anything larger than ~20K
> fails - it transfers the first few block, then freezes up and
> eventually times out:
> 

I've seen problems like this when talking between one system and
another which had bugs in some MTU-discovery code, which caused
problems with TCP packets over a certain size.

What is at the other end of your MultiNet SLIP link? Another Vax, or
something else? Once you get your MN 3.2 upgrade, you'll be able to
monitor the data flow through the slip link using TCPDUMP, which might
help to diagnose what is going wrong. [Ken: Please correct me if I'm
wrong on this one! :-) ]

What modems (or other comms gear) is connected between the MN Vax and
the other end?

Is there anything between the two systems which might inhibit the
flow of 8-bit clean data?



Cheers,
   Simon Hackett


Newsgroups: vmsnet.networks.tcp-ip.multinet
From: richard@raet-sh.UUCP (Richard van Denzel)
Subject: Printer problems on VMS V5.5-2
Organization: RAET Industrie & Handel, Utrecht
Date: Mon, 4 Jan 1993 09:31:17 GMT

Hello netlanders,

I have some printing problems on my VAXstation 3100 running VMS V5.5-2 and
using the Multinet LPD to print to some printers connected to a HP9000/832S
running HP-UX 8.0.
The problems seem to be occurring since I upgraded my machine to VMS V5.5-2.
On VMS V5.5 it all ran fine. I am using Multinet V3.1C.
The message I get on the console of the bootmember to which the VAXstation
is connected is:

Multinet Printer Symbiont: Negative acknowledgement waiting for ack of 
printer data,
	ABORTING PRINT JOB

Does anyone have a clue to what is going on, or should this be considered
a bug in either VMS V5.5-2 or MultinetV3.1C?

Please help, because I a baffled.

Thanx,

Richard.
-- 
--
Richard van Denzel	richard%raet-sh!relay.nluug.nl via internet backbone
RAET Industrie & Handel	uucp: ..!{uunet,sun4nl}!raet-sh!richard
Plotterweg 38
From: adelman@TGV.COM (Kenneth Adelman)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Re: help w/acc boards
Date: Mon, 11 Jan 93 14:30:11 PST
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

> Anybody out there got experience setting up acc boards for HDLC and x.25?

> I'm trying to set up IP over HDLC on a point-to-point circuit with some ACC
> 5100/6100 boards in a uVAX  and an 8600 respectively.  (Don't ask why, I just
> work here sometimes). The uVAX acc board comes up fine and will successfully
> loopback (internal and external).  I can ping, FTP, and  telnet to it. The 8600
> set up does not.  Same version of MultiNet on both systems, 3.1(X) I get the
> following error setting up either internal or external loopback on the 8600:

>   DSTL86> mu ping 195.200.200.2
>   PING 195.200.200.2 (195.200.200.2): 56 data bytes
>   sendto: %MULTINET-F-ENOBUFS, No buffer space available
>   MULTINET_PING: wrote 195.200.200.2 64 chars, ret=-1
>   sendto: %MULTINET-F-ENOBUFS, No buffer space available
>   MULTINET_PING: wrote 195.200.200.2 64 chars, ret=-1
>   sendto: %MULTINET-F-ENOBUFS, No buffer space available
>   .
>   .
>   etc
>   .

> ENOBUFS...what buffers where and what do I tweak?

    Check to be sure that $ MULTINET SHOW/BUFFER doesn't report a
problem with "requests for memory denied". If it does not, then the
problem is the ACC card not accepting packets for transmission. No idea
why it wouldn't do this.

							    Ken
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Re: MultiNet and VMS 5.5-*
From: LABELLES@ZENO.MSCD.EDU (Stephen LaBelle - MSCD)
Date: 06 Jan 1993 16:06:02 -0600 (MDT)
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

>> Bill Sadvary sadvary@dickinson.edu writes:
>> 
>> We are running MultiNet v3.1B and we will soon be upgrading to VMS v5.5-2
>> (VAX 6340).

   I will be upgrading a 6310 from VMS 5.5 to 5.5-2 tommorrow 1/7/93.

>> 
>> Has anybody seen any problems with these two versions running in conjunction?
>> 
>> The DEBNA controller problem was fixed in VMS 5.5, right?

   The DEBNA broadcast packets problem still exists with VMS 5.5-2, get the
   patch.
 

						Steve


##############################################################################
# Stephen LaBelle                        # Internet : labelles@zeno.mscd.edu #
# Systems Programmer                     #            labelles@clem.mscd.edu #
# Metropolitan State College of Denver   #####################################
# Denver, Colorado  USA                  # Bitnet   : LABELLES@MSCD.BITNET   #
##############################################################################
# DISCLAIMER: The opinions expressed are mine and in no way, shape or form   #
# neccessarily reflect those of Metropolitan State College of Denver.        #
##############################################################################
From: ewilts@galaxy.gov.bc.ca (Ed Wilts)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Re: NFS mount Sun CD-ROM
Date: 11 Jan 93 11:58:01 -0800
Organization: BC Systems Corporation

In article <1993Jan11.162621.20054@mksol.dseg.ti.com>, pyron@skndiv.dseg.ti.com (Dillon Pyron) writes:
> 
> Real simple.  I'd like to occasionally mount my VAX OLD CDs (wow) on my
> cube-mate's Sun.  And read them via Bookreader.  I suspect that I am persuing
> a dream, but maybe someone else has done this.  Or at least tried and can save
> me the effort.

I doubt that this is possible today.  The problem is that the Vax OLD CDs are
in Files-11 format which the Sun probably can't read.  I've got a similar
problem in that I can't mount the Ultrix OLDs and read them on the Vax.

Rumours are that Digital will be releasing the Ultrix OLDs in ISO format.  If
we're lucky and they do that with the VAX OLD, you'll be in business.

-- 
Ed Wilts, BC Systems, 4000 Seymour Place, Victoria, B.C., Canada, V8X 4S8
EWilts@Galaxy.Gov.BC.CA     Office:  (604) 389-3430   Fax: (604) 389-3412
Newsgroups: vmsnet.networks.tcp-ip.multinet
From: pyron@skndiv.dseg.ti.com (Dillon Pyron)
Subject: NFS mount Sun CD-ROM
Reply-To: pyron@skndiv.dseg.ti.com
Organization: TI/DSEG VAX Support
Date: Mon, 11 Jan 1993 16:26:21 GMT


Real simple.  I'd like to occasionally mount my VAX OLD CDs (wow) on my
cube-mate's Sun.  And read them via Bookreader.  I suspect that I am persuing
a dream, but maybe someone else has done this.  Or at least tried and can save
me the effort.

Thanks,
--
Dillon Pyron                      | The opinions expressed are those of the
TI/DSEG Lewisville VAX Support    | sender unless otherwise stated.
(214)462-3556 (when I'm here)     |
(214)492-4656 (when I'm home)     |"Pacts with the devil are not legally
pyron@skndiv.dseg.ti.com          |binding!"
PADI DM-54909                     |-Friar Tuck   _Robin Hood:The Hooded Man_
From: dsroberts@beckman.com
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Nice Calendar, Thanks TGV!
Date: 12 Jan 93 09:48:18 PDT
Organization: Beckman Instruments

Well, it was a pleasant surprise getting the calendar in the mail.  A nice
bonus for us customers.

Now, how about an key of names?  I've met maybe half the people depicted, but
I'd like to put faces and names to the rest.
-- 
   Don Roberts                   Internet:  dsroberts@beckman.com
   Beckman Instruments, Inc.     Phone:     714/961-3029
   2500 Harbor Bl. Mailstop X-12 FAX:       714/961-3351
   Fullerton, CA  92634          Disclaimer:  Blame me, not Beckman.
   "Abortion isn't a 'choice', it's the slaughter of the innocent"
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Re: EWS and VAXstations
From: rickm@darkwing.uoregon.edu (Rick Millhollin x6-1730)
Date: 12 Jan 1993 20:56:59 GMT
Distribution: world
Organization: University of Oregon Network Services
NNTP-Posting-Host: darkwing.uoregon.edu

For each VAXstation that is to be an X server you need a file EWS$LIBARY:nodename.DAT that looks like:

  *
  $INET_ADDRESS           128.223.33.68
  $INET_NETWORK_MASK      255.255.254.0
  $INET_BROADCAST_MASK    128.223.33.255
  $INET_ROUTER            128.223.32.1
  $LOGIN_HOST             DONALD,60.630,DECNET
  $LOGIN_HOST             OREGON,60.601,DECNET

On the VAXstation with DECwindows running, set up the Session Manager Security Options to allow access by:
  Node =node-name-of-client (if this doesn't work try IP-address)
  Username = *
  Transport=TCPIP .

On a client VAX do a $ SET DISPLAY/CREATE/NODE=node-name-of-VAXstation/TRANSPORT=TCPIP and  fire up the
application.

On  a client UNIX box do a setenv DISPLAY  node-name-of-VAXstation:0.0 and fire up the application.

 ------------------------------------------------------------------------------
|  Rick Millhollin               Bitnet:   rickm@oregon      U     U   OOOOO   |
|  Assistant Director for        Internet: rickm@oregon.     U     U  O     O  |
|    Technical Services                      uoregon.edu     U     U  O     O  |
|  Computing Center              Voice:    (503)346-1730     U     U  O     O  |
|  University of Oregon          FAX:      (503)346-4397     U     U  O     O  |
|  Eugene, Oregon 97403-1212                                  UUUUU    OOOOO   |
 ------------------------------------------------------------------------------
From: adelman@TGV.COM (Kenneth Adelman)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Re: Multinet and VMS
Date: Wed, 6 Jan 93 08:56:22 PST
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

> We are running MultiNet v3.1B and we will soon be upgrading to VMS v5.5-2 (VAX
> 6340).

> Has anybody seen any problems with these two versions running in conjunction?

> The DEBNA controller problem was fixed in VMS 5.5, right?

    No, it exists through at least VMS V5.5-1. I don't know if it
exists in V5.5-2.

							    Ken
Newsgroups: vmsnet.networks.tcp-ip.multinet
From: mcmahon@Tgv.Com (John 'Fast-Eddie/FuzzFace' McMahon)
Subject: Re: Nice Calendar, Thanks TGV!
Reply-To: mcmahon@Tgv.Com (John 'Fast-Eddie/FuzzFace' McMahon)
Organization: TGV, Incorporated in Santa Cruz, California, USA
Date: Tue, 12 Jan 1993 21:59:22 GMT


In article <1993Jan12.094818.1079@beckman.com>, dsroberts@beckman.com writes:
=>
=>Well, it was a pleasant surprise getting the calendar in the mail.  A nice
=>bonus for us customers.
=>
=>Now, how about an key of names?  I've met maybe half the people depicted, but
=>I'd like to put faces and names to the rest.

I'll post a key in a few days.  I haven't gotten my calendar yet :-) 

QUICK AND DIRTY CONTEST:  Can you name all the individuals in the 
calendar ?  Send your entries to McMahon@TGV.COM.  The winner
(first person with the most answers) will win something.

--
John 'Fast-Eddie' McMahon    ()
TGV, Incorporated            () "Any networking problem can be solved by
603 Mission Street           ()  the application of 33 miles of Unshielded 
Santa Cruz, California 95060 ()  Twisted Pair (UTP)"   
408-427-4366 or 800-TGV-3440 ()                      [InterOp Spring 1992]
E-Mail: MCMAHON@TGV.COM      ()

Xref: sparky vmsnet.networks.tcp-ip.multinet:2606 comp.os.vms:20362
From: jeffk@cdibm.fnal.gov (Jeff Kallenbach)
Newsgroups: vmsnet.networks.tcp-ip.multinet,comp.os.vms
Subject: Remote X Clients over TCP/IP onto VS
Date: 5 Jan 93 16:37:49 GMT
Organization: Fermi National Accelerator Laboratory, Batavia IL
NNTP-Posting-Host: cdibm.fnal.gov

We have a user who is having difficulty running remote X clients onto his
VAX Station via TCP/IP.  He's using VMS 5.3.something, multinet 3.1, DECWindows 
(not MOTIF), and the MULTI CONFIG LOAD-UCX-DRIVER flag is true.  DECNet 
transport works fine.  We have hundreds of VAXStations at FNAL and I thought we 
had this problem whipped.  My hunch is upgrading to VMS 5.4 or so will solve 
this, but I want to verify that before taking his system down.  Any suggestions?

JCK

-- 
============================================================================
Jeff Kallenbach                       |Opinions are not neccessarily shared
Fermi National Accelerator Laboratory |by my employer.  In fact, they agree 
708-840-2210                          |with very little of what I say.
============================================================================
From: mahan@TGV.COM (Patrick L. Mahan)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: RE: Remote X Clients over TCP/IP onto VS
Date: Tue, 5 Jan 93 10:04:51 PST
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

#
#We have a user who is having difficulty running remote X clients onto his
#VAX Station via TCP/IP.  He's using VMS 5.3.something, multinet 3.1, DECWindows 
#(not MOTIF), and the MULTI CONFIG LOAD-UCX-DRIVER flag is true.  DECNet 
#transport works fine.  We have hundreds of VAXStations at FNAL and I thought we 
#had this problem whipped.  My hunch is upgrading to VMS 5.4 or so will solve 
#this, but I want to verify that before taking his system down.  Any suggestions?
#

Make sure that the name specified by the logical UCX$INET_HOST is in the
file hosts.local.  Also, have him run MU X11/LOG both on his VAXstation as well
as from another VAX with the display set to point at his VAXstation.

Patrick L. Mahan

--- TGV Window Washer ------------------------------- Mahan@TGV.COM ---------

Waking a person unnecessarily should not be considered  - Lazarus Long
a capital crime.  For a first offense, that is            From the Notebooks of
							  Lazarus Long
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Quicky: What is the version of multinet needed for VMS v5.5-2?
From: macy@polar.bowdoin.edu (Tad Macy)
Date: Wed, 6 Jan 1993 19:45:20 -0500 (EST)
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List


Hope this is a quick one:

Just going to VMS 5.5-2 (from 5.4-3 and, yes, we know about most of
the gotcha's) and yes want to confirm the version of multinet needed.

Thanks,

Tad Macy
Bowdoin College