Xref: utzoo comp.protocols.nfs:1072 comp.os.vms:27603 comp.sys.dec:3516 Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!lll-winken!rogue.llnl.gov!oberman From: oberman@rogue.llnl.gov Newsgroups: comp.protocols.nfs,comp.os.vms,comp.sys.dec Subject: Re: NFS Client for VMS? Message-ID: <1990Jul5.131413.1@rogue.llnl.gov> Date: 5 Jul 90 20:14:13 GMT References: Sender: usenet@lll-winken.LLNL.GOV Followup-To: comp.protocols.nfs Distribution: na Lines: 26 In article , hart@blackjack.dt.navy.mil (Michael Hart) writes: > Someone before me bought Wollongong TCP & NFS for VMS; unfortuneatly, > as I found out in a moment of need, the NFS product is server side > only for VMS. > > Does anyone know of or have a (preferable PD) NFS client side > software for VMS?? > > My need is to have a client that will talk to a VMS NFS server. Doing a client for VMS is a killer. At one time Wollongong reportedly said it couldn't be done. If they really said that, they were wrong. The only client now available is from TGV, Inc and is layered on top of their MultiNet product. While the client is pretty cheap, the base MultiNet is fairly expensive. But chaeper than Wollongong when I last compared. For information, contact TGV at 800 TGV-3440. R. Kevin Oberman Lawrence Livermore National Laboratory Internet: oberman@icdc.llnl.gov (415) 422-6955 Disclaimer: Don't take this too seriously. I just like to improve my typing and probably don't really know anything useful about anything.