home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.protocols.nfs:2313 comp.protocols.tcp-ip.ibmpc:5197
- Newsgroups: comp.protocols.nfs,comp.protocols.tcp-ip.ibmpc
- Path: sparky!uunet!cs.utexas.edu!torn!cunews!dgbt!netfs!ncs.dnd.ca!boucher
- From: boucher@ncs.dnd.ca (R. Boucher)
- Subject: PC-NFS 3.5 to 4.0 Upgrade Problems
- Message-ID: <1992Sep12.030127.25715@netfs.dnd.ca>
- Followup-To: comp.protocols.tcp-ip.ibmpc
- Summary: TCP/IP apps work, RPC based apps don't
- Keywords: PC-NFS RPC
- Sender: news@netfs.dnd.ca (NEWS)
- Nntp-Posting-Host: ncs.dnd.ca
- Organization: DND, Ottawa, CANADA
- Distribution: usa
- Date: Sat, 12 Sep 1992 03:01:27 GMT
- Lines: 91
-
- I have just gotten around to upgrade my 286PC from PC-NFS 3.5 to
- PC-NFS 4.0 and things have been going downhill since...
-
- Whereas 3.5 worked flawlessly before (printer redirection file
- system mounting and all the TCP/IP applications), 4.0 can only manage
- to mount filesystems and run the TCP/IP applications.
-
- The applications which use RPC (nfsping, rpcinfo, showmnt) dont work,
- which indicates that some RPC calls don't seem to be doing the right
- thing. Everything works fine to the TCP/UDP layer (telnet, ftp, rsh).
- I re-installed 4.0, but the behavior didn't change.
-
- If anyone can give me a pointer to what I should check out next, it
- would be *greatly* appreciated. The whole point of the upgrade is
- to be able to print raw-binary file to a server-printer.
-
- I have RTFM and checked-out the README.TXT prior to the upgrade. If
- this is a FAQ, please direct me to its location.
-
- (output and behavior analysis follows)
-
- Thanks,
- --
- Robert Boucher
-
- (HOME/WORK) boucher@ncs.dnd.ca
- (WORK) ...!uunet!revcan!dcsem!252
- (HOME) ...!uunet!revcan!flatout!asimov!rob
-
-
- Here is my output when I start PC-NFS 4.0:
-
- C:\> prt *
- Sun Microsystems PC-NFS(R) Print Redirector Version 4.0
- Copyright (c) 1986-1992 Sun Microsystems, Inc.
- The hotkey is <Ctrl>+<LShift>+<RShift>
- C:\> net init
- [PC-NFS is Installed]
- PC name: chenette
- NFS216f : asimov is not a PC-NFS authentication server.
- NFS217I : Searching for a PC-NFS authentication server...
- [not sure why its not a pcnfsd server on the first try...]
- Authentication Server: asimov
- Username: rob
- Mounting drives ....
- Drive f: on asimov:/tmp
- Device LPT2: on asimov:panasonic
- NFS039F : The NET USE failed (code 1003):
- [could this be a mountd problem on the server?]
- Drive Q: on asimov:/var/spool/mail
- C:\>
-
- where my config.sys contains just the bare-bones:
- SHELL=C:\command.com /p /e:256
- DEVICE=C:\DOS\ANSI.SYS
- FILES=20
- BUFFERS=10
- DEVICE=c:\NFS\PCNFS.SYS
- DEVICE=c:\NFS\SOCKDRV.SYS
- DEVICE=c:\NFS\WD8003E.SYS /p300
- LASTDRIVE=V
-
- The network.bat contains:
- NET START RDR CHENETTE *
- NET PCNFSD asimov
- NET NAME rob password
-
- and drives.bat contains:
- NET USE F: asimov:/tmp
- NET USE LPT2: asimov:panasonic
- NET USE Q: asimov:/var/spool/mail
-
- When I type "ping asimov", I get "asimov (xx.xx.xx.xx) is alive".
- However, when using "nfsping", I get "No answer from asimov".
- Something similar happens when using rpcinfo: if using rpcinfo with
- the -p option, I get the full listing of RPC services available from
- asimov, however if I specify "rpcinfo -u asimov 150001 1", I get "proc
- 150001 vers 1 is not available", although it was listed in the
- "rpcinfo -p".
-
- The filesystems mounted on F: and Q: are properly handled and work
- fine. When I use "showmnt -e asimov", I get "NFS107W : Server asimov
- is not responding".
-
- My PC-NFS server is a 486PC running DELL SVR4 i2.1 with PCNFSD v2 (dated
- 92/09/18). PCNFSD was tested successfully with the enclosed
- clnt.pcnfsd tester. PC-NFS v3.5 worked flawlessly with this pcnfs
- server. The PC is a 286 (640K,EGA) with the following BIOS: 286
- Modular BIOS Version 3.03 Copyright Award Software Inc. It's using
- a WD8003E ethernet card. If it matters, it's running MS-DOS 3.3
- (and its not running MS-Windows).
-