RE: Mounting NFS file share -- MIDRANGE-L

I was able to PING the server successfully. We don't have NFS installed
on the windows server so I can't use that at this time. 
I did verify that the share already exists. I can MKDIR to
('/QNTC/nwssql01'). When I displayed the directory I wasn't seeing
anything so I assumed it wasn't working. I guess I misunderstood how
QNTC works by trying to create the directory with the share included. 
I looked at the properties of NetServer and noticed that the domain was
set to a work group that wasn't in the same domain that the remote
server is on. I changed the domain and was able to see the subfolders in
('QNTC/nwssql01/*'). After I did that I broke the communication link to
our fax server. I looked at the work group and it consists of our fax
server and the UPS shipping meter in our warehouse. I changed the domain
back to the work group to fix what I broke. 
I'm going to use FTP until I can get the Fax Server and UPS meter onto
the same domain as our other servers. Once I do that I'll change the
domain in NetServer and see if that was what the problem is. 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Tuesday, December 12, 2006 2:36 PM
To: Midrange Systems Technical Discussion
Subject: Re: Mounting 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')


What happens if you try to do the following:

      PING RMYSYS('nwssql01')

It should respond with:

      Verifying connection to host system nwssql01 at address x.x.x.x

Make sure that the address (x.x.x.x in the above example) is correct for

the server you're connecting to.  Also, remember that you're using NFS
not 
Windows networking.  SO make sure you're using the TCP/IP host name
(from 
DNS or hosts table) not the Windows NetBIOS name.

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.


NFS requires two-way communication.  Not only does the data need to be 
sent from your System i to the NFS server, but the NFS server has to be 
able to send data back.  Make sure that SXXXXXXX.DOMAINNAME.COM can be 
looked up from both your local system and the NFS server.

This is all basic TCP/IP setup, and has very little to do with NFS other

than the fact that NFS runs over TCP/IP!

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?


In order to create a share on a Windows computer, you have to do it from

the server itself.  You can't use MKDIR to tell a computer to share 
something that it isn't already sharing!!

To tell the /QNTC filesystem to create an entry for the nwssql01 server,

type the following command.  Do not add any additional share or
directory 
names after the server name -- all you want to do is establish a link to

the server:

     MKDIR ('/QNTC/nwssql01')

Now, you should be able to see any shares available on that server by 
typing:

     WRKLNK '/QNTC/nwssql01/*')

Assuming the 'AttachmentsReady' share is already there, you're good.  If

not, you have to go to the nwssql01 server and add the share. Once the 
share has been added, you can create directories within the share if you

like.

     MKDIR ('/QNTC/nwssql01/AttachmentsReady/MyDir')

But, for security reasons, the share itself ("AttachmentsReady" in this 
example) has to be created on the server side.  The share is referenced
in 
a path name the same way a directory would be, but it's not quite the
same 
thing as a normal directory.


Note that your message discusses two completely different network 
protocols (NFS and SMB) and I replied to both of them.  I hope that's
not 
confusing!  The first part of the message (the part discussing the MOUNT

command and DNS) is about NFS.  The remaining part (the part discussing 
QNTC and the MKDIR command) is about SMB.  The SMB part should work with

NetBIOS names, but the NFS part will only work with TCP/IP names.