× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.