[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | Multia |
|
| Moderator: | ONTIME::SYSTEM |
|
| Created: | Tue Oct 04 1994 |
| Last Modified: | Tue Jun 03 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 782 |
| Total number of notes: | 3413 |
Was there ever a resolution or workaround to this problem - one
of my customers has recently raised this with me i.e. he cannot
connect to a service, only to a node name via LAT on a Multia.
He was sold the Multias as a replacement for VXT2000s, and is very
annoyed that he doesn't get the same functionality. CSC (UK) have
told him it's a bug that won'r be fixed, but note 349 suggests there
may be a way round it. Can anyone help?
Dialogue between customer and CSC below.....
From: NWSRT1::DSN%SRQ$102570074S1UVO "DSNlink Notification (20-MAY-1997
20:10)" 20-MAY-1997 19:11:55.90
To: NWSRT1::COLIN
CC:
Subj: RE: X-windows access to LAT hosts
Additional Service Request information is available from the Digital
Customer Support Center. It has been automatically submitted to you.
The message from the Digital Customer Support Center contains either
a solution description, a request closure confirmation, or a call for
more information about the problem you submitted.
When letting us know whether the solution resolved your problem, or
should you wish to send additional information, please REPLY to this
notification message or send to the address listed on the FROM line.
Attached to this message is any additional information regarding this
Service Request.
If you wish to telephone the Customer Support Center regarding this
Service Request, please refer to the sequence number shown below.
Thank you for using DSNlink.
Digital Sequence Number: 102570074S1UVO
Status: More information required
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Work Unit Entered: 7-MAY-1997 13:56
Work Unit originated from customer
From: (04UK0000800-AESDN) NWSRT1::COLIN "Colin Brewer, 7-277 3230 (
7-MAY-199
7 12:55)"
To: DSN%MULTIA_SW
Subj: X-windows access to LAT hosts
System NWSRT1 is a VAX 6000-430 running VMS V5.5-2.
(HW Ver=00A10000000000000B000006, SID=0B000006, XSID=02300101, DSN=V1.2)
I am trying to create an X-session on a LAT host from a Multia desktop. It
only works if I use the LAT service name that is the same as the host name.
It
does not work for other LAT service names offered by the host. KEAterm on the
same Multia desktop connects successfully to any LAT service name.
Colin Brewer
******************************************************************************
*
Name : MR COLIN BREWER
Phone : 01734 774204 EXT 3230
******************************************************************************
*
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Work Unit Entered: 7-MAY-1997 20:33
Work Unit originated from customer
From: (04UK0000800-AESDN) NWSRT1::COLIN "Colin Brewer, 7-277 3230 (
7-MAY-199
7 19:32)"
To: DSN%SRQ$102570074S1UVO
Subj: RE: X-windows access to LAT hosts
System NWSRT1 is a VAX 6000-430 running VMS V5.5-2.
(HW Ver=00A10000000000000B000006, SID=0B000006, XSID=02300101, DSN=V1.2)
Further info, following your phone call.
When trying to start up a LAT X-session on the lat service STANDBY, I get the
following error message in an "X Session Startup" window:
The following error occurred while attempting to start an X session on STANDBY
over LAT
Network routine connect() failed, error=EINVAL
If you have enabled logging (via the Control Panel), please check the log for
any additional information.
The log gives:
07/05/97 13:29:02 X Server Information Multia X Server V2.2.451
(Intel
) logging enabled.
07/05/97 13:29:02 Network Warning socket(12) failed,
error=ENOBUF
S
07/05/97 13:29:02 Network Warning socket(12) failed,
error=ENOBUF
S
07/05/97 13:29:02 Network Warning socket(12) failed,
error=ENOBUF
S
07/05/97 13:29:03 Network Warning getnodeadd() failed,
error=EAFN
OSUPPORT
07/05/97 13:29:03 Network Warning getnodeadd() failed,
error=EAFN
OSUPPORT
07/05/97 13:29:03 Network Warning getnodeadd() failed,
error=EAFN
OSUPPORT
07/05/97 13:29:03 Network Warning socket(12) failed,
error=ENOBUF
S
07/05/97 13:29:03 X Application Startup Information Local startup of
'mwm'
initially succeeded. If it ultimately failed, the display may not have been
set
properly, or the application's path may have been wrong.
07/05/97 13:29:05 Network Warning connect(76) failed,
error=EINVA
L
07/05/97 13:29:05 X Session Startup Error Network routine connect()
f
ailed, error = EINVAL.
07/05/97 13:29:06 X Protocol Error Reply sent to Client #1,
Reques
t=ChangeProperty, Error=BadAtom
07/05/97 13:29:06 X Protocol Error Reply sent to Client #1,
Reques
t=ChangeProperty, Error=BadAtom
07/05/97 13:29:06 X Protocol Error Reply sent to Client #1,
Reques
t=ChangeProperty, Error=BadAtom
07/05/97 13:29:06 X Protocol Error Reply sent to Client #1,
Reques
t=QueryFont, Error=BadFont
07/05/97 13:29:06 X Protocol Error Reply sent to Client #1,
Reques
t=QueryFont, Error=BadFont
07/05/97 13:29:07 X Protocol Error Reply sent to Client #1,
Reques
t=ChangeProperty, Error=BadAtom
07/05/97 13:29:07 X Protocol Error Reply sent to Client #1,
Reques
t=ChangeProperty, Error=BadAtom
This is the same whether STANDBY exists or not.
The log for a successful connection (to the node NWSRT1) is:
07/05/97 13:27:38 X Server Information Multia X Server V2.2.451
(Intel
) logging enabled.
07/05/97 13:27:38 Network Warning socket(12) failed,
error=ENOBUF
S
07/05/97 13:27:38 Network Warning socket(12) failed,
error=ENOBUF
S
07/05/97 13:27:38 Network Warning getnodeadd() failed,
error=EAFN
OSUPPORT
07/05/97 13:27:38 Network Warning getnodeadd() failed,
error=EAFN
OSUPPORT
07/05/97 13:27:38 Network Warning getnodeadd() failed,
error=EAFN
OSUPPORT
07/05/97 13:27:39 Network Warning socket(12) failed,
error=ENOBUF
S
07/05/97 13:27:39 X Application Startup Information Local startup of
'mwm'
initially succeeded. If it ultimately failed, the display may not have been
set
properly, or the application's path may have been wrong.
07/05/97 13:27:41 X Protocol Error Reply sent to Client #1,
Reques
t=ChangeProperty, Error=BadAtom
07/05/97 13:27:41 X Protocol Error Reply sent to Client #1,
Reques
t=ChangeProperty, Error=BadAtom
07/05/97 13:27:41 X Protocol Error Reply sent to Client #1,
Reques
t=ChangeProperty, Error=BadAtom
07/05/97 13:27:42 X Protocol Error Reply sent to Client #1,
Reques
t=QueryFont, Error=BadFont
07/05/97 13:27:42 X Protocol Error Reply sent to Client #1,
Reques
t=QueryFont, Error=BadFont
07/05/97 13:27:42 X Protocol Error Reply sent to Client #1,
Reques
t=ChangeProperty, Error=BadAtom
07/05/97 13:27:42 X Protocol Error Reply sent to Client #1,
Reques
t=ChangeProperty, Error=BadAtom
07/05/97 13:27:44 X Protocol Error Reply sent to Client #3,
Reques
t=QueryFont, Error=BadFont
07/05/97 13:27:44 X Protocol Error Reply sent to Client #3,
Reques
t=QueryFont, Error=BadFont
The service STANDBY does exist:
Node Name: NWSRT1 LAT Protocol Version: 5.2
Node State: On
Node Ident: SYS$ANNOUNCE
Incoming Connections: Enabled Incoming Session Limit: None
Outgoing Connections: Disabled Outgoing Session Limit: None
Service Responder: Disabled
Circuit Timer (msec): 80 Keepalive Timer (sec): 20
Retransmit Limit (msg): 8 Node Limit (nodes): None
Multicast Timer (sec): 60 CPU Rating: 0
Maximum Unit Number: 9999
User Groups: 0
Service Groups: 0
Service Name Status Rating Identification
NWSRT1 Available 69 D
STANDBY Available 69 D
Colin Brewer
******************************************************************************
*
Name : MR COLIN BREWER
Phone : 01734 774204 EXT 3230
******************************************************************************
*
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Work Unit Entered: 8-MAY-1997 12:30
Work Unit created by Service Specialist
Colin,
I have been able to reproduce the problem. I will investigate further and
I will get back to you.
Regards,
Geoff Judd.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Work Unit Entered: 15-MAY-1997 09:19
Work Unit created by Service Specialist
Colin,
I have escalated this problem to our engineering group. I will contact
you
again when I have further information.
Regards,
Geoff Judd.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Work Unit Entered: 20-MAY-1997 20:10
Work Unit created by Service Specialist
Colin,
This restriction is documented in section 4.3.1. of the Multia Enterprise
Client Version 3.2 Release Notes. I have raised this with the engineering
group
and there are no plans to remove this restriction in the future.
Regards,
Geoff Judd.
Andy Cartwright
[Posted by WWW Notes gateway]
| T.R | Title | User | Personal
Name | Date | Lines
|
|---|