HP3000-L Archives

October 2000, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Ian Ferguson <[log in to unmask]>
Reply To:
Ian Ferguson <[log in to unmask]>
Date:
Thu, 19 Oct 2000 11:51:42 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (88 lines)
Count me in on this one Error:42 on 6.5

Regards

Ian Ferguson

-----Original Message-----
From: Robert Mills [mailto:[log in to unmask]]
Sent: 19 October 2000 11:37
To: [log in to unmask]
Subject: Re: NetIPC ERROR IN VT


We are also getting the same Error: 42. Sometimes the message is for Job: 0.
We are on 6.0 (PP2 I think)

regards,
Robert W.Mills (Windsong Services)
-----Original Message-----
From: Paul Thompson [mailto:[log in to unmask]]
Sent: Thursday, October 19, 2000 11:39 AM
To: [log in to unmask]
Subject: Re: NetIPC ERROR IN VT


Gavin

I am also experiencing this problem also occasionally along with ** NS/3000
NetIPC ERROR IN VT; Job: #S3342; PIN: 148; Info: 1 - Error: 42;

I have so far been unable to pin down the problem. We are on 5.5.

Anyone got any clues on this one?

Cheers

Paul Thompson
Ecometry Analyst
Spark Response
Telephone: 0191 4959962
e-mail:[log in to unmask]
www.sparkresponse.co.uk


-----Original Message-----
From: Gavin Scott [mailto:[log in to unmask]]
Sent: 18 October 2000 18:56
To: [log in to unmask]
Subject: NetIPC ERROR IN VT


We're seeing VT sessions on one machine getting spontaneously dropped, with
the following associated message on the console:

** NS/3000 NetIPC ERROR IN VT; Job: #S1234; PIN: 123; Info: 1
- Error 39

I'm used to these errors usually indicating that a SOCKERR occurred on the
connection, but SOCKERR 39 is:

   INVALID NODE NAME SYNTAX.  (SOCKERR 39)

which doesn't sound like something you would get once the connection is
established.  The system is on 6.0, Powerpatch 2.

Telnet sessions are experiencing similar problems, though in the case of
telnet disconnects, the system sometimes thinks the session is still logged
on for a while.

I know that a lot of people have reported disconnect problems of one kind or
another over recent months.  Dos my problem sound familiar to anyone?

Thanks,

G.

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered
through the MessageLabs Virus Control Centre. For further information visit
http://www.star.net.uk/stats.asp

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered
through the MessageLabs Virus Control Centre. For further information visit
http://www.star.net.uk/stats.asp

ATOM RSS1 RSS2