[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Can't get to file service?
Date: Thu, 18 Jul 91 12:02:13 CDT
From: firstname.lastname@example.org (Michael T. Swink)
We are operating Genera 8.0.1 on a SUN computer running SunOS 4.1 with
a symbolics board attached. While running in the genera environment if the
user tries to use the "login command" or the "show file" command among others,
Genera gives the error:
Show File (file) STEPHENS /usr2/quotes
Error: Request to STEPHENS for a 1124+59(:NFILE) connection was refused.
No reason was given.
***STEPHENS is the SUN that has the symbolics board installed on it***
however commands such as "show users @STEPHENS" work just fine.
The above error also occurs when trying to update the namespace.
The only related occurance that I can find when working with genera happens
when genera is first booted.
Error that occurs in cold load stream:
STEPHENS does no support FILE service through any locally supported protocol.
It supports only TCP-FTP via TCP, NFS via UDP, NFS via UDP.
The local host supports only NFS via UDP, TCP-FTP via TCP, TFTP via UDP, QFILE
via CHAOS, NFILE via BYTE-STREAM-WITH-MARK.
No path could be found for TCP-FTP via TCP, NFS via UDP, NFS via UDP.
Use protocol TFTP on medium UDP (Y or N) Yes.
STEPHENS does not support FILE service through any locally supported protocal.
Use protocol NFILE on medium TCP? (Y or N) Yes.
After typing 'yes' to the NFILE option, genera brings up the console window.
However, if 'no' is typed to the TFTP option, then a 'yes' answer to the NFILE
question causes genera to ask about protocol TFTP again, and when a 'yes'
answer is given this time the console window appears. This tells me that
neither protocol is being implemented.
It looks like STEPHENS or your local host do not both have network
addresses on the Internet connecting them. The "No path could be found"
line is a giveaway that neither UDP nor TCP have a connection. I am a
little surprised that you are not offered the choice of NFS, given that
that would probably work.
Your problem with updating the namespace is almost certainly that you
are storing your namespace files on Stephens as well as other files.
You might try updating the namespace locally first, and then forcibly
saving the same object on the server.
Try the following:
Show Namespace Object host local :Locally yes
Show Namespace Object host stephens :Locally yes
This should show:
the local host has an address on the Internet
Stephens has an address on the same Internet
Stephens has FILE service provided as follows:
FILE UDP NFS
FILE UDP TFTP
FILE TCP TCP-FTP
These last two are not required. It should NOT say
FILE TCP NFILE
although from the above I guess it probably doesn't.
- [no subject]
- From: email@example.com (Michael T. Swink)