Our LAN has a mix of Linux and OSX computers connected to it. The Linux computers work as expected but the OSX computers will not connect, complains:
"Could not connect to the server because the name or password is not correct."
The servers contain:
-bash-4.1$ cat /etc/exports # # /etc/exports
/nfs4exports 192.168.1.0/24(ro,sync,insecure,no_root_squash,no_subtree_check,fsid=0)
/nfs4exports/data 192.168.1.0/24(rw,sync,insecure,no_root_squash,no_subtree_check)
/nfs4exports/home 192.168.1.0/24(rw,sync,insecure,no_root_squash,no_subtree_check)
Does anyone see anything here that would prevent them from connecting?
Bob
On 05.06.2013 18:07, Bob Goodwin - Zuni, Virginia, USA wrote:
Our LAN has a mix of Linux and OSX computers connected to it. The Linux computers work as expected but the OSX computers will not connect, complains:
"Could not connect to the server because the name or password is not correct."
The servers contain:
-bash-4.1$ cat /etc/exports # # /etc/exports
/nfs4exports 192.168.1.0/24(ro,sync,insecure,no_root_squash,no_subtree_check,fsid=0)
/nfs4exports/data 192.168.1.0/24(rw,sync,insecure,no_root_squash,no_subtree_check)
/nfs4exports/home 192.168.1.0/24(rw,sync,insecure,no_root_squash,no_subtree_check)
Does anyone see anything here that would prevent them from connecting?
What's up Bob?
/etc/sysconfig/nfs RPCNFSDARGS="-d -s"
systemctl restart nfs-server journalctl -f --full
poma
On 06/06/13 03:02, poma wrote:
Does anyone see anything here that would prevent them from connecting?
What's up Bob?
/etc/sysconfig/nfs RPCNFSDARGS="-d -s"
systemctl restart nfs-server journalctl -f --full
poma
I haven't found any definition for "-d -s" What does it tell it to do?
I tried man /etc/sysconfig/nfs but see no list of options ... I have no keyboard/display on the server so it's ssh and vi and my skills with vi are minimal. Need to know what I'm doing.
Bob
On 06/06/13 22:25, Bob Goodwin - Zuni, Virginia, USA wrote:
On 06/06/13 03:02, poma wrote:
Does anyone see anything here that would prevent them from connecting?
What's up Bob?
/etc/sysconfig/nfs RPCNFSDARGS="-d -s"
systemctl restart nfs-server journalctl -f --full
poma
I haven't found any definition for "-d -s" What does it tell it to do?
man 8 rpc.nfsd
I tried man /etc/sysconfig/nfs but see no list of options ... I have no keyboard/display on the server so it's ssh and vi and my skills with vi are minimal. Need to know what I'm doing.
Bob
On 06/06/13 10:27, Ed Greshko wrote:
/etc/sysconfig/nfs
RPCNFSDARGS="-d -s"
systemctl restart nfs-server journalctl -f --full
poma
I haven't found any definition for "-d -s" What does it tell it to do?
man 8 rpc.nfsd
Ok, I've muddled through most of this but the server runs SL-6 and does not recognize the command
journalctl -f --full
What is the equivalent command, assuming there is one?
Am 06.06.2013 17:48, schrieb Bob Goodwin - Zuni:
Ok, I've muddled through most of this but the server runs SL-6 and does not recognize the command
journalctl -f --full
What is the equivalent command, assuming there is one?
the is no systemd nor journald before F15 and RHEL6 is based on F12/F13 look in /var/log/messages and othe files in /var/log as well as dmesg like all the decades before systemd
On 06/06/13 11:51, Reindl Harald wrote:
Am 06.06.2013 17:48, schrieb Bob Goodwin - Zuni:
Ok, I've muddled through most of this but the server runs SL-6 and does not recognize the command
journalctl -f --full
What is the equivalent command, assuming there is one?
the is no systemd nor journald before F15 and RHEL6 is based on F12/F13 look in /var/log/messages and othe files in /var/log as well as dmesg like all the decades before systemd
Ok, will do that.
Thanks
On 06/06/13 12:02, Bob Goodwin - Zuni, Virginia, USA wrote:
the is no systemd nor journald before F15 and RHEL6 is based on F12/F13 look in /var/log/messages and othe files in /var/log as well as dmesg like all the decades before systemd
In /var/log/Messages I see:
Jun 6 12:17:06 localhost rpc.mountd[29893]: refused mount request from 192.168.1.29 for /home/nfs4exports/ (/): not exported
192.168.1.29 is the old Mac portable I am using to test with.
"not exported" so why not? Dunno what to look for there?
On 06.06.2013 18:25, Bob Goodwin - Zuni, Virginia, USA wrote:
In /var/log/Messages I see:
Jun 6 12:17:06 localhost rpc.mountd[29893]: refused mount request from 192.168.1.29 for /home/nfs4exports/ (/): not exported
192.168.1.29 is the old Mac portable I am using to test with.
"not exported" so why not? Dunno what to look for there?
Exactly as written. :) For testing purposes mount locally on the server, point by point. Afterwards in the same manner at the client.
poma
On 06/06/13 16:20, poma wrote:
On 06.06.2013 18:25, Bob Goodwin - Zuni, Virginia, USA wrote:
In /var/log/Messages I see:
Jun 6 12:17:06 localhost rpc.mountd[29893]: refused mount request from 192.168.1.29 for /home/nfs4exports/ (/): not exported
192.168.1.29 is the old Mac portable I am using to test with.
"not exported" so why not? Dunno what to look for there?
Exactly as written. :) For testing purposes mount locally on the server, point by point. Afterwards in the same manner at the client.
poma
I don't understand what you are suggesting.
Both servers work as expected with any Linux client computer I've tried, they are essential to my system. The Apple Mac computers do not connect, immediately give me the error message: "Could not connect to the server because the name or password is not correct."
What name? What password? No password is required, "name" ? It's just 192.168.1.xx, another misleading error message most likely.
On 06.06.2013 23:11, Bob Goodwin - Zuni, Virginia, USA wrote:
I don't understand what you are suggesting.
Both servers work as expected with any Linux client computer I've tried, they are essential to my system. The Apple Mac computers do not connect, immediately give me the error message: "Could not connect to the server because the name or password is not correct."
What name? What password? No password is required, "name" ? It's just 192.168.1.xx, another misleading error message most likely.
I can only comment logs on the server side. ;) Mentioned log on the server says that the client is trying to mount non exported point. If this doesn't occur during communication with the Linux based clients, obviously the problem is in the System 6/7 implementation or misconfiguration - the client side. So we went back to the very beginning. :) Or maybe back to the future, regarding the hardware you are trying to drive. :)
poma
On 06/06/13 18:09, poma wrote:
I can only comment logs on the server side. ;) Mentioned log on the server says that the client is trying to mount non exported point. If this doesn't occur during communication with the Linux based clients, obviously the problem is in the System 6/7 implementation or misconfiguration - the client side. So we went back to the very beginning. :) Or maybe back to the future, regarding the hardware you are trying to drive. :)
poma
Yes, I am sure you understand my problem and I appreciate your help.
Sometimes your brevity makes it hard for me to follow, requires some thought, not a bad thing I guess.
What I was looking for was someone who understood the problems involved in getting Mac OSX working with our Linux NFS. I know there were things that had to be done to get it working with NFSv3 a couple of years ago, I eventually got it to work and it was convenient to have. I'll work on it some more tomorrow, end of day here now.
Thanks,
Bob
On 07.06.2013 01:51, Bob Goodwin - Zuni, Virginia, USA wrote:
Yes, I am sure you understand my problem and I appreciate your help.
Sometimes your brevity makes it hard for me to follow, requires some thought, not a bad thing I guess.
What I was looking for was someone who understood the problems involved in getting Mac OSX working with our Linux NFS. I know there were things that had to be done to get it working with NFSv3 a couple of years ago, I eventually got it to work and it was convenient to have. I'll work on it some more tomorrow, end of day here now.
Haha cats everywhere, Panthera pardus, Schrödinger's cat, Spherical Cow, … Bob you can literally try all options, http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPa...
poma
On 07/06/13 00:02, poma wrote:
Haha cats everywhere, Panthera pardus, Schrödinger's cat, Spherical Cow, … Bob you can literally try all options, http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPa...
poma
I didn't know there were OSX man pages!
It looks like I may need to specify nfsv4 somewhere? If this is applicable to my OSX 10.5 client ...
nfsvers=<num> Set the NFS protocol version number - 2 for NFSv2, 3 for NFSv3 and 4 for NFSv4. The default is to try version 3 first, and fall back to version 2 if the mount fails.
nfsv2 nfsv3 nfsv4 Deprecated. Use -o vers=<num> to specify NFS protocol version.
I'll try this later.
Bob
Allegedly, on or about 07 June 2013, Bob Goodwin - Zuni, Virginia, USA sent:
I didn't know there were OSX man pages!
If we dropped the hint that OSX is a based on BSD (a real UNIX), would that help you?
Of course what works on one doesn't necessarily mean that it'll work on the other in the same way, but it's a starting point. Particularly as BSD has some differences to Linux.
On 07/06/13 08:40, Tim wrote:
If we dropped the hint that OSX is a based on BSD (a real UNIX), would that help you?
No I am well aware of that but it never occurred to me to look for man pages since Apple seems to do their best to conceal everything [my impression]. I do know enough to root around in their "Terminal" with Unix/Linux commands, just never tried "man" anything ...
Bob
On 06/06/2013 07:25 AM, Bob Goodwin - Zuni, Virginia, USA wrote:
I tried man /etc/sysconfig/nfs but see no list of options ... I have no keyboard/display on the server so it's ssh and vi and my skills with vi are minimal. Need to know what I'm doing.
You don't have to use vi if you don't want to. I certainly don't! Use nano instead. Much easier to use.
On 06/06/13 11:22, Joe Zeff wrote:
I tried man /etc/sysconfig/nfs but see no list of options ... I have no keyboard/display on the server so it's ssh and vi and my skills with vi are minimal. Need to know what I'm doing.
You don't have to use vi if you don't want to. I certainly don't! Use nano instead. Much easier to use.
I usually use "gedit" when I don't have "E3" available but in this case gedit wants a display that I couldn't get to work. I have a vi cheat sheet and was able to get by using that it just takes longer. E3em is my preferred text editor, have used it "forever" but never see any mention of it.
On 06/06/2013 08:56 AM, Bob Goodwin - Zuni, Virginia, USA wrote:
I usually use "gedit" when I don't have "E3" available but in this case gedit wants a display that I couldn't get to work. I have a vi cheat sheet and was able to get by using that it just takes longer. E3em is my preferred text editor, have used it "forever" but never see any mention of it.
One thing I like about nano (or, "Mork's editor" as I like to call it) is that most of the important commands are listed at the bottom of the screen, including ^G, which lists the rest of them. Nice, user friendly and with enough features to make it fairly easy to do whatever emergency edits you need from a CLI.
Hello there,
What version of OSX are you running?
Macs are very bad with NFS - and under different versions you configure it drastically differently.
Boris. On Jun 5, 2013 12:07 PM, "Bob Goodwin - Zuni, Virginia, USA" < bobgoodwin@wildblue.net> wrote:
Our LAN has a mix of Linux and OSX computers connected to it. The Linux computers work as expected but the OSX computers will not connect, complains:
"Could not connect to the server because the name or password is not correct."
The servers contain:
-bash-4.1$ cat /etc/exports # # /etc/exports
/nfs4exports 192.168.1.0/24(ro,sync,**insecure,no_root_squash,no_** subtree_check,fsid=0)http://192.168.1.0/24(ro,sync,insecure,no_root_squash,no_subtree_check,fsid=0)
/nfs4exports/data 192.168.1.0/24(rw,sync,**insecure,no_root_squash,no_** subtree_check)http://192.168.1.0/24(rw,sync,insecure,no_root_squash,no_subtree_check)
/nfs4exports/home 192.168.1.0/24(rw,sync,**insecure,no_root_squash,no_** subtree_check)http://192.168.1.0/24(rw,sync,insecure,no_root_squash,no_subtree_check)
Does anyone see anything here that would prevent them from connecting?
Bob
--
box10 Fedora-18 XFCE Linux
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.**org/mailman/listinfo/usershttps://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/**Mailing_list_guidelineshttp://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 06/06/13 18:25, Boris Epstein wrote:
Hello there,
What version of OSX are you running?
Macs are very bad with NFS - and under different versions you configure it drastically differently.
Boris.
I'm using an old Mac portable with OSX 10.5 installed. The desktop computer downstairs has the latest OSX installed, whatever it is called? I observed the problem there and elected to resurrect this old portable as a matter of convenience for testing, I have it right next to me.
Both Mac's have the same problem, GO > Connect to Server and I give it the address nfs://192.168.1.8:/home and it immediately returns the error message "Could not connect to the server because the name or password is not correct."
If as you say it varies with versions then it may be hopeless but I wont give up quite yet.
Thanks,
Bob
-
Bob Goodwin -
Boris Epstein -
Ed Greshko -
Joe Zeff -
poma -
Reindl Harald -
Tim