jdd@wucs.UUCP (John DeHart) (10/29/84)
We are having difficulties installing IP/TCP 1.28 on VMS V3.6 ( with
the 3.5 XGDRIVER) with Eunice 3.2. We have the shared Deuna version of
IP/TCP and our DECNET works fine.
Everything works going out of VMS/EUNICE (ftp,rlogin,rsh, rcp,telnet,mail)
but rcp and rsh get some error messages when coming into VMS/EUNICE.
Mail has problems getting to VMS. Rlogin and ftp do not work at all.
The error messages from rsh and rcp look like this
[EUNICE: AST ^Y setup failed, Status = %Xf4 - %SYSTEM-F-ILLIOFUNC illegal I/O]
[EUNICE: AST ^C setup failed, Status = %Xf4 - %SYSTEM-F-ILLIOFUNC illegal I/O]
[EUNICE: AST ^T setup failed, Status = %Xf4 - %SYSTEM-F-ILLIOFUNC illegal I/O]
These messages occur when rsh or rcp is used for the first couple of hours
after the network is restarted, after that the two commands work silently.
The commands (rcp, rsh) work even when these messages are received.
The last four lines of the mail messages look like this when trying to
mail to someone on the VMS machine.
% mail -v jdd@wucecv
... (normal messages)
451 (No such file or directory) Mail troubles (sndmsg balks), try later
>> QUIT
221 Bye received, Goodbye
jdd@wucecv ... Deferred: Bad file number
%
rlogin and ftp on the other hand do not work at all. Ftp does the following
% ftp wucecv
connected to wucecv
%
Rlogin does similar things and sometimes gives messages like, "Broken pipe",
"rlogin: status 0".
I know that the daemons for rlogin and ftp get started, because they
show up on a SHOW/SYS (VMS) and on a ps -clax (EUNICE)
I have spent numerous hours on the phone with technical support from TWG
going over the installation procedure and everything looks fine.
They seem to have objections to the way we organized our VMS users.
We are supporting 1500-1600 students, so we set them up one level
deeper than normal (e.g DRB0:[USER.AAA9999]). We also use logical names
in defining our VMS users in AUTHORIZE (e.g. DEFINE U1 __DRB0:[USER.])
TWG has suggested that we use the physical name in AUTHORIZE and move
the users up a level, even though they admit it probably won't make
any difference.
Well there's our story. Anyone had similar problems? Any suggestions?
---
John DeHart ..!ihnp4!wucs!jdd
Box 1045 Washington Univ.
St. Louis Mo. 63130 USA (314) 889-6160kvc@scgvaxd.UUCP (Kevin Carosso) (11/03/84)
Don't listen to TWG regarding rooted logical names... Unless there is something drastically wrong with Eunice, you shouldn't have any trouble with putting your users one directory down and giving them a root, I do it all the time. Unless TWG says that Eunice can't hack rooted directories, then I wouldn't bother to take their suggestion. In any case, if they suggested using physical device names in authorize they are definitely confused. Even if you move your users out of the one-level root, do NOT use the device names in the SYSUAF. Create a (concealed) logical name for the disk (all our users are on a disk (actually several disks) called USER:). If you put a physical name in there, then you will have to manually change every entry in your UAF should you ever want to move disks around. Using the logical name means you change only the logical name if you move disks around. /Kevin Carosso scgvaxd!kvc Hughes Aircraft Co.