home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky vmsnet.networks.tcp-ip.multinet:2613 comp.os.vms:20408
- Path: sparky!uunet!sunquest!spades.aces.com!gavron
- From: gavron@spades.aces.com (Ehud Gavron 602-570-2000 x. 2546)
- Newsgroups: vmsnet.networks.tcp-ip.multinet,comp.os.vms
- Subject: Re: Remote X Clients over TCP/IP onto VS
- Message-ID: <5JAN199321175448@spades.aces.com>
- Date: 6 Jan 93 04:17:00 GMT
- References: <1icdgtINNs8j@fnnews.fnal.gov>
- Sender: news@sunquest.UUCP
- Reply-To: gavron@ACES.COM
- Followup-To: vmsnet.networks.tcp-ip.multinet
- Organization: ACES Consulting Inc.
- Lines: 33
- News-Software: VAX/VMS VNEWS 1.4-b1
-
- In article <1icdgtINNs8j@fnnews.fnal.gov>, jeffk@cdibm.fnal.gov (Jeff Kallenbach) writes...
- #We have a user who is having difficulty running remote X clients onto his
- #VAX Station via TCP/IP.
-
- "having difficulty" is not an error description.
-
- #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?
-
- 1. Include a problem description.
- 2. Include an error example
- 3. Include the output from
- $ MULTINET X11DEBUG
- which is usually enough to indicate the problem. I'll bet one of
- you people is so incredibly brilliant that the security authorization
- is limited to DECNET transport, but that's just a guess since zero
- information is included.
-
- #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.
-
-
- Ehud
-
- --
- Ehud Gavron (EG76)
- gavron@vesta.sunquest.com
- 1993 Count of COMP.OS.VMS people who can't describe a problem: #1
-