The "insecure port" message says that the NFS client (z/OS) is using a TCP port number >1023. Historically, only "authorized" programs could use IP ports in the range 0..1023. So some servers required that the client (remote) site use a port <= 1023 because that was assurance that the client was indeed "authorized". To allow an "insecure" port to be use, that is one >1023, you need the "insecure" option in the /etc/exports entry. As an example from my home LAN:
/nfs 192.168.152.0/24(nohide,rw,insecure,sync,fsid=0) 192.168.151.0/24(rw,insecure,sync,nohide,fsid=0) /nfs2 192.168.152.0/24(nohide,rw,insecure,sync,fsid=0) 192.168.151.0/24(rw,insecure,sync,nohide,fsid=0) The above shows that clients can connect to both /nfs and /nfs2 on the server. The clients are in one of two IP ranges. Either 192.168.152.0 or 192.168.151.0. "nohide" means that NFS can traverse into filesystems mounted "beneath" the subdirectories mentioned. "rw" means they can be mount in "read write" mode. "insecure" means that the nfs client (remote) can use IP ports >1023. "sync" forces writing to disk more quickly (as best as I can tell). You might want to update your /etc/exports file to include the "insecure" option. If you can't read up on the z/OS NFS client's use of ports here: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/cpn1co60/2.1.5.6 -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * [email protected] * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -----Original Message----- > From: Linux on 390 Port [mailto:[email protected]] On > Behalf Of Dazzo, Matt > Sent: Monday, September 26, 2011 2:04 PM > To: [email protected] > Subject: Re: RH NFS Server > > I finally got some messages to the /var/log/messages file. > What might these means? Thanks Matt > > Sep 26 14:54:35 lntest1 mountd[1264]: authenticated mount > request from 27.1.39.74:1023 for /home/matt (/home/matt) > Sep 26 14:54:35 lntest1 kernel: nfsd: request from insecure > port (27.1.39.74:1062)! > [root@lntest1 log]# > > -----Original Message----- > From: Linux on 390 Port [mailto:[email protected]] On > Behalf Of McKown, John > Sent: Monday, September 26, 2011 9:49 AM > To: [email protected] > Subject: Re: RH NFS Server > > The actual subdirectory name on my Linux box is /LIH1. The > "/nfs" prefix is a requirement of the NFS client on z/OS. > > -- > John McKown > Systems Engineer IV > IT > > Administrative Services Group > > HealthMarkets(r) > > 9151 Boulevard 26 * N. Richland Hills * TX 76010 > (817) 255-3225 phone * > [email protected] * www.HealthMarkets.com > > Confidentiality Notice: This e-mail message may contain > confidential or proprietary information. If you are not the > intended recipient, please contact the sender by reply e-mail > and destroy all copies of the original message. > HealthMarkets(r) is the brand name for products underwritten > and issued by the insurance subsidiaries of HealthMarkets, > Inc. -The Chesapeake Life Insurance Company(r), Mid-West > National Life Insurance Company of TennesseeSM and The MEGA > Life and Health Insurance Company.SM > > > > > -----Original Message----- > > From: Linux on 390 Port [mailto:[email protected]] On > > Behalf Of Dazzo, Matt > > Sent: Monday, September 26, 2011 8:18 AM > > To: [email protected] > > Subject: Re: RH NFS Server > > > > John, in your parm statement (:/nfs/LIH1) is nfs an real dir > > or a specification? > > > > -----Original Message----- > > From: Linux on 390 Port [mailto:[email protected]] On > > Behalf Of McKown, John > > Sent: Friday, September 23, 2011 11:57 AM > > To: [email protected] > > Subject: Re: RH NFS Server > > > > For z/OS NFS, the FILESYSTEM is syntactically required and > > the name must be unique, but it is a logical name and not an > > actual data set name. An example which works on my z/OS 1.10 > > system is: > > > > MOUNT FILESYSTEM('SERVER1.ASCII') + > > MOUNTPOINT('/nfs-ascii/server1') + > > PARM('10.168.254.172:/nfs/LIH1,xlat(Y),proto(udp),vers(3)') + > > TYPE(NFS) + > > MODE(RDWR) > > > > SERVER1.ASCII is not a DSN. > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO > LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO > LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
