RE: Mounting NFS file share

[vhamberg@xxxxxxxxxxx]

Just to be clear - NetServer - which uses /QNTC - is not related to NFS, except 
by accident of some similar names.

-------------- Original message -------------- 
From: "Grizzly Malchow" <grizzlym@xxxxxxxxxxxxxxxxxxxxx> 

> Never mind. I figured out what was wrong. Netserver wasn't configured 
> correctly. 
>
> -----Original Message----- 
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Grizzly Malchow 
> Sent: Tuesday, December 12, 2006 10:29 AM 
> To: Midrange Systems Technical Discussion 
> Subject: Mounting NFS file share 
>
> I'm trying to mount a *NFS file share to a file share on one of our 
> Windows servers. My first question is, and this probably isn't the 
> place to ask, how can I tell if the file share on the Windows server I'm 
> trying to use is a NFS file share? 
>
> When I run the following MOUNT command I am receiving the following 
> error: Cannot find address for specified system name. 
>
> MOUNT TYPE(*NFS) MFS('nwssql01:/AttachmentsReady') 
> MNTOVRDIR('/HOME/GRIZZLY/AttachmentsReady') 
>
>
>
> I have verified that the name of the remote server is correct. The Share 
> name is correct and the directory /HOME/GRIZZY/AttachmentsReady exists. 
> NFS is started as well. 
>
> The part that is puzzling to me is the additional message information 
> states that an error was detected while trying to retrieve communication 
> information about host SXXXXXXX.DOMAINNAME.COM (Where SXXXXXXX is the 
> serial number of our i5, System I, what have you and the DOMAINNAME is 
> our domain name) . It doesn't even appear to be trying to communicate 
> with the server I specified. 
>
>
>
> For what it's worth, I tried MKDIR ('/QNTC/nwssql01/AttachmentsReady') 
> and I receive a message stating I'm not authorized to the object. Can 
> anyone suggest where I can begin trouble shooting? 
>
>
>
> I need to establish this share because I eventually need to use the IFS 
> Api's to read/write files to the share. 
>
>
>
> Thanks in advance, 
>
> Griz 
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> list 
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/midrange-l. 
>
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/midrange-l.