| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3264.1 | | PEACHS::GHEFF | Got a head with wings | Thu Apr 10 1997 10:07 | 6 |
| ECONNREFUSED usually means that the rexec (or rsh) "service" is not
available. Check the TCPWare side to be sure that rexec is functional.
Lanworkplace should work.
#Gary
|
| 3264.2 | still no joy | MIPSBX::"[email protected]" | Stephen | Mon Apr 14 1997 06:25 | 8 |
| I checked that REXEC is configured and running corectly but it is still
not working - the same errors are appearing. Any further suggestions as
to where I might look ??
Cheers
Steve
[Posted by WWW Notes gateway]
|
| 3264.3 | | PEACHS::GHEFF | Do you feel like swimming? | Mon Apr 14 1997 10:07 | 4 |
| How did you determine that rexecd is responding? Did you use an rexec
client? (NT and Unix have rexec commands.) Did you telnet into port 512?
#Gary
|
| 3264.4 | | NNTPD::"[email protected]" | Stephen | Thu Apr 17 1997 13:47 | 7 |
| Hi there,
I got the cust to telnet into the rexec port 512 and this worked no
problem. Any more help will be appreciated.
#steve
[Posted by WWW Notes gateway]
|
| 3264.5 | | JAMIN::OSMAN | Eric Osman, dtn 226-7122 | Thu Apr 17 1997 15:18 | 13 |
| Try the usual diagnosis to narrow down where problem is occurring:
o Try app both as an excursion control panel app, and running app
from a terminal emulator. Do both fail ?
o If decnet available, try both decnet and tcp. Do both fail ?
o Try rsh and rexec. Do both fail ?
o Try with node numerical addresses instead of names. Does this work
?
/Eric
|
| 3264.6 | | PEACHS::GHEFF | Do you feel like swimming? | Thu Apr 17 1997 18:31 | 28 |
| I took a quick look at the 2.1 source and it looked to me like the
launcher was looping on a read, waiting for either real information or
something like an econnrefused message to come back from the rexec
daemon on the remote system. In the event of an error it cleans up
some memory and closes its socket. (Really there's little else it can
do in the event of a disconnect on the remote end.)
I also took a quick look at www.process.com and www.novell.com for any
rexec connection issues and didn't find anything interesting.
I really don't believe that this is a problem with the eXcursion
software, I've got to think it's either something at the TCPware end
or (less likely) a problem with the Lanworkplace configuration.
I have not seen such a message come back when PCX$SERVER.COM was out of
date before, but I suppose it's worth checking on the age of the file.
Edit sys$system:pcx$server.com and look at the very first line of the
file. If it contains something like
$ SET NOVERIFY !V502
then you're probably okay. If the first line is not a SET NOVERIFY
followed by a version number, please replace the existing file
with a newer version off the eXcursion kit.
#Gary
|
| 3264.7 | | NNTPD::"[email protected]" | Stephen | Tue Apr 22 1997 10:21 | 6 |
| I shall post the results of these once I have managed to get hold of the cust.
Cheers
Steve
[Posted by WWW Notes gateway]
|