Since I've seen SuSE folks posting here lately, I'm repeating this problem in the hopes that someone there will see it and offer some help:
We've been using SuSE in our office since 5.x, and have always been able to mount the AS/400 to our Linux boxen. However, with 7.0, we get this message:
shadow:~ # mount weyco400:/ /mnt/weyco400 pmap_getmaps rpc problem: RPC: Procedure unavailable mount: RPC: Unable to receive; errno = Connection refused
What changed in 7.0 that might cause this behavior? How do we fix it?
Other NFS mounts in both directions work fine, and in fact, I can mount machine "shadow" from the AS/400. -- ____________________________________________________________ Glenn Holmer gholmer@weycogroup.com Programmer/Analyst phone: 414.908.1809 Weyco Group, Inc. fax: 414.908.1601 -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Have you blocked off ports 2049 and port 111 - both are needed. Does /etc/exports contain / *.yourdomainname(rw) in it Regards, Bruce.
Since I've seen SuSE folks posting here lately, I'm repeating this problem in the hopes that someone there will see it and offer some help:
We've been using SuSE in our office since 5.x, and have always been able to mount the AS/400 to our Linux boxen. However, with 7.0, we get this message:
shadow:~ # mount weyco400:/ /mnt/weyco400 pmap_getmaps rpc problem: RPC: Procedure unavailable mount: RPC: Unable to receive; errno = Connection refused
What changed in 7.0 that might cause this behavior? How do we fix it?
Other NFS mounts in both directions work fine, and in fact, I can mount machine "shadow" from the AS/400.
-- ____________________________________________________________ Glenn Holmer gholmer@weycogroup.com Programmer/Analyst phone: 414.908.1809 Weyco Group, Inc. fax: 414.908.1601
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Bruce wrote:
Have you blocked off ports 2049 and port 111 - both are needed.
Does /etc/exports contain / *.yourdomainname(rw) in it
Regards, Bruce.
Interestingly, a portscanner does *not* show anything on 2049 on the AS/400 (nor in the services listing), although 111 is there. But older SuSE's (e.g. 6.3) can connect properly!
Since I've seen SuSE folks posting here lately, I'm repeating this problem in the hopes that someone there will see it and offer some help:
We've been using SuSE in our office since 5.x, and have always been able to mount the AS/400 to our Linux boxen. However, with 7.0, we get this message:
shadow:~ # mount weyco400:/ /mnt/weyco400 pmap_getmaps rpc problem: RPC: Procedure unavailable mount: RPC: Unable to receive; errno = Connection refused
What changed in 7.0 that might cause this behavior? How do we fix it?
Other NFS mounts in both directions work fine, and in fact, I can mount machine "shadow" from the AS/400.
-- ____________________________________________________________ Glenn Holmer gholmer@weycogroup.com Programmer/Analyst phone: 414.908.1809 Weyco Group, Inc. fax: 414.908.1601 -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
We're still struggling with this, and I've called upon IBM support. They had me take a comm trace, and they report that the SuSE 6.4 box that works is using UDP to port 111, while the 7.0 box that doesn't work is using TCP. Is this significant? Is there a way to specify which protocol 'mount' uses to test this out? Glenn Holmer wrote:
Since I've seen SuSE folks posting here lately, I'm repeating this problem in the hopes that someone there will see it and offer some help:
We've been using SuSE in our office since 5.x, and have always been able to mount the AS/400 to our Linux boxen. However, with 7.0, we get this message:
shadow:~ # mount weyco400:/ /mnt/weyco400 pmap_getmaps rpc problem: RPC: Procedure unavailable mount: RPC: Unable to receive; errno = Connection refused
What changed in 7.0 that might cause this behavior? How do we fix it?
Other NFS mounts in both directions work fine, and in fact, I can mount machine "shadow" from the AS/400.
-- ____________________________________________________________ Glenn Holmer gholmer@weycogroup.com Programmer/Analyst phone: 414.908.1809 Weyco Group, Inc. fax: 414.908.1601 -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Yes this is VERY significant. I asked you whether or not your system was open for action on PORTS 111 and 2049. You may have to get the nfs daemon to listen on port 111. Or use port option for mount. Try (and I haven't tested it) mount -t nfs node:/ /directory port=111 Pop verbose or -v in there somewhere,. The other way will be to install the mount from SuSE 6.4. Bruce.
We're still struggling with this, and I've called upon IBM support. They had me take a comm trace, and they report that the SuSE 6.4 box that works is using UDP to port 111, while the 7.0 box that doesn't work is using TCP. Is this significant? Is there a way to specify which protocol 'mount' uses to test this out?
Glenn Holmer wrote:
Since I've seen SuSE folks posting here lately, I'm repeating this problem in the hopes that someone there will see it and offer some help:
We've been using SuSE in our office since 5.x, and have always been able to mount the AS/400 to our Linux boxen. However, with 7.0, we get this message:
shadow:~ # mount weyco400:/ /mnt/weyco400 pmap_getmaps rpc problem: RPC: Procedure unavailable mount: RPC: Unable to receive; errno = Connection refused
What changed in 7.0 that might cause this behavior? How do we fix it?
Other NFS mounts in both directions work fine, and in fact, I can mount machine "shadow" from the AS/400.
-- ____________________________________________________________ Glenn Holmer gholmer@weycogroup.com Programmer/Analyst phone: 414.908.1809 Weyco Group, Inc. fax: 414.908.1601
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Bruce wrote:
Yes this is VERY significant. I asked you whether or not your system was open for action on PORTS 111 and 2049.
And I answered:
Interestingly, a portscanner does *not* show anything on 2049 on the AS/400 (nor in the services listing), although 111 is there. But older SuSE's (e.g. 6.3) can connect properly!
You may have to get the nfs daemon to listen on port 111. Or use port option for mount. Try (and I haven't tested it) mount -t nfs node:/ /directory port=111
The AS/400 *is* listening on 111. The issue is TCP vs. UDP, not port number. The comm trace I took on the AS/400 shows both failing and succeeding attempts coming in on 111. IBM later called back and said that they do not support NFS mounts over TCP on the AS/400, only UDP. I tried "mount -o udp weyco400:/ /mnt/weyco400" and still get the same error: pmap_getmaps rpc problem: RPC: Procedure unavailable mount: RPC: Unable to receive; errno = Connection refused A comm trace of this attempt shows that the connection is being attempted with TCP despite the "-o udp" option. This is important enough to the company that at this point I am leaning toward banning 7.0 on production machines in our shop. -- ____________________________________________________________ Glenn Holmer gholmer@weycogroup.com Programmer/Analyst phone: 414.908.1809 Weyco Group, Inc. fax: 414.908.1601 -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Ah well, at we tried. At this stage I suspect a bug in the form of perhaps a security update that has disabled an earlier function or something similar. The best suggestion now is to rename mount to say mount-7.0 and copy a version of mount from SuSE6.4 or anywhere else into /bin The version I have is mount-2.10f This, for me, seems to be very stable. Looking in http://www.suse.de/en/support/download/updates/64_update.html and http://www.suse.de/en/support/download/updates/70_update.html I can't see any reference to mount directly The rpm package is util-2.10f-32. Check your version and make a decision. You could rpm -U -f oldversion.rpm and try that out or just copy the old version of mount across and try it. It seems a bit odd that the seeking of a server would be changed from udp to tcp, but there may be a reason. Thats a fundamental. Bruce.
Bruce wrote:
Yes this is VERY significant. I asked you whether or not your system was open for action on PORTS 111 and 2049.
And I answered:
Interestingly, a portscanner does *not* show anything on 2049 on the AS/400 (nor in the services listing), although 111 is there. But older SuSE's (e.g. 6.3) can connect properly!
You may have to get the nfs daemon to listen on port 111. Or use port option for mount. Try (and I haven't tested it) mount -t nfs node:/ /directory port=111
The AS/400 *is* listening on 111. The issue is TCP vs. UDP, not port number. The comm trace I took on the AS/400 shows both failing and succeeding attempts coming in on 111.
IBM later called back and said that they do not support NFS mounts over TCP on the AS/400, only UDP.
I tried "mount -o udp weyco400:/ /mnt/weyco400" and still get the same error:
pmap_getmaps rpc problem: RPC: Procedure unavailable mount: RPC: Unable to receive; errno = Connection refused
A comm trace of this attempt shows that the connection is being attempted with TCP despite the "-o udp" option.
This is important enough to the company that at this point I am leaning toward banning 7.0 on production machines in our shop.
-- ____________________________________________________________ Glenn Holmer gholmer@weycogroup.com Programmer/Analyst phone: 414.908.1809 Weyco Group, Inc. fax: 414.908.1601
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
participants (2)
-
bruce@toorak.com
-
gholmer@weycogroup.com