From my client, also Suse 9.3, running NFS Client, I see the shared
I have a Suse 9.3 server running NFS server with two users, afore and lilo directories afore & lilo. File ownership is as it should be, afore for afore directory and lilo for lilo directory. I Lilo's machine is running Suse 9.2. First of all, when I setup the NFS client in Yast and try to select for the file system, it cannot find anything. I enter the /home directory same as on my Suse 9.3 machine. When I finish, it takes a long time for Yast to start the services again. I check the mount point, and the two directories are there, but afore as ownership of lilo and lilo folder has ownership of 2002! So, why does the select remote filesystem not work in 9.2 and work in 9.3 and why to the ownerships show up different on the two client machines. Server is set to allow all hosts and the firewalls turned off on all machines for test purposes. Art
Did you create the users on the different machines explicitly to have the same UIDs? Or are you using NIS or some similar distributed name service thingy? Log in as lilo on each machine and type "id" you want to see the same numbers for UID and GID on each system. Cheers, Simon --- Art Fore <art.fore@comcast.net> wrote:
I have a Suse 9.3 server running NFS server with two users, afore and lilo
From my client, also Suse 9.3, running NFS Client, I see the shared directories afore & lilo. File ownership is as it should be, afore for afore directory and lilo for lilo directory.
I Lilo's machine is running Suse 9.2. First of all, when I setup the NFS client in Yast and try to select for the file system, it cannot find anything. I enter the /home directory same as on my Suse 9.3 machine. When I finish, it takes a long time for Yast to start the services again.
I check the mount point, and the two directories are there, but afore as ownership of lilo and lilo folder has ownership of 2002!
So, why does the select remote filesystem not work in 9.2 and work in 9.3 and why to the ownerships show up different on the two client machines.
Server is set to allow all hosts and the firewalls turned off on all machines for test purposes.
Art
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
"You can tell whether a man is clever by his answers. You can tell whether a man is wise by his questions." Naguib Mahfouz __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
On Sun, 2005-08-07 at 16:02 -0700, Simon Roberts wrote:
Did you create the users on the different machines explicitly to have the same UIDs? Or are you using NIS or some similar distributed name service thingy?
Log in as lilo on each machine and type "id" you want to see the same numbers for UID and GID on each system.
Cheers, Simon
--- Art Fore <art.fore@comcast.net> wrote:
I have a Suse 9.3 server running NFS server with two users, afore and lilo
From my client, also Suse 9.3, running NFS Client, I see the shared directories afore & lilo. File ownership is as it should be, afore for afore directory and lilo for lilo directory.
I Lilo's machine is running Suse 9.2. First of all, when I setup the NFS client in Yast and try to select for the file system, it cannot find anything. I enter the /home directory same as on my Suse 9.3 machine. When I finish, it takes a long time for Yast to start the services again.
I check the mount point, and the two directories are there, but afore as ownership of lilo and lilo folder has ownership of 2002!
So, why does the select remote filesystem not work in 9.2 and work in 9.3 and why to the ownerships show up different on the two client machines.
Server is set to allow all hosts and the firewalls turned off on all machines for test purposes.
Art
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
"You can tell whether a man is clever by his answers. You can tell whether a man is wise by his questions." — Naguib Mahfouz
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
The server logins were made the same as the two other machines, but the UIDs are the default on all machines. On my machine and the server, afore is UID 1000, lilo is 1002 on the server, and her machine has lilo as 1000. If you go by UID, I can see where her machine would come up with what it does, but I would have though that NFS would take care of that. I have not had the problem in earlier version of Suse. Art
On Sun, 2005-08-07 at 16:02 -0700, Simon Roberts wrote:
Did you create the users on the different machines explicitly to have the same UIDs? Or are you using NIS or some similar distributed name service thingy?
Log in as lilo on each machine and type "id" you want to see the same numbers for UID and GID on each system.
Cheers, Simon
--- Art Fore <art.fore@comcast.net> wrote:
I have a Suse 9.3 server running NFS server with two users, afore and lilo
From my client, also Suse 9.3, running NFS Client, I see the shared directories afore & lilo. File ownership is as it should be, afore for afore directory and lilo for lilo directory.
I Lilo's machine is running Suse 9.2. First of all, when I setup the NFS client in Yast and try to select for the file system, it cannot find anything. I enter the /home directory same as on my Suse 9.3 machine. When I finish, it takes a long time for Yast to start the services again.
I check the mount point, and the two directories are there, but afore as ownership of lilo and lilo folder has ownership of 2002!
So, why does the select remote filesystem not work in 9.2 and work in 9.3 and why to the ownerships show up different on the two client machines.
Server is set to allow all hosts and the firewalls turned off on all machines for test purposes.
Art
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
"You can tell whether a man is clever by his answers. You can tell whether a man is wise by his questions." — Naguib Mahfouz
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Well I have liloo machine upgraded to 9.3, same problem as before. What I don't understand is how when I go into yast, network services, nfs client and add a new server, put in the server ip address, then try the select remote file system, it comes up empty and that machine, but on my machine, it comes up correctly. Same network, server NFS server has * that can access the /home directory. Art
Well, you're probably right. If the browsing can't see it, there's something else wrong. Though just as an aside, if you upgrade a machine it seems very unlikely that the upgrade would alter your UIDs, so if they were mismatched before, they still are. The command id will tell you unequivocally and with trivial ease if that's the case. The only other problem I've come across with NFS that seems a bit like this is that some NFSes would refuse to talk with any machine for which they could not find a proper name. So, if you didn't have the machine's hostname in /etc/hosts (for example) then NFS wouldn't talk with it. But I don't think that's a requirement any more. Good luck, Simon --- Art Fore <art.fore@comcast.net> wrote:
Did you create the users on the different machines explicitly to have the same UIDs? Or are you using NIS or some similar distributed name service thingy?
Log in as lilo on each machine and type "id" you want to see the same numbers for UID and GID on each system.
Cheers, Simon
--- Art Fore <art.fore@comcast.net> wrote:
I have a Suse 9.3 server running NFS server with two users, afore and lilo
From my client, also Suse 9.3, running NFS Client, I see the shared directories afore & lilo. File ownership is as it should be, afore for afore directory and lilo for lilo directory.
I Lilo's machine is running Suse 9.2. First of all, when I setup
On Sun, 2005-08-07 at 16:02 -0700, Simon Roberts wrote: the
NFS client in Yast and try to select for the file system, it cannot find anything. I enter the /home directory same as on my Suse 9.3 machine. When I finish, it takes a long time for Yast to start the services again.
I check the mount point, and the two directories are there, but afore as ownership of lilo and lilo folder has ownership of 2002!
So, why does the select remote filesystem not work in 9.2 and work in 9.3 and why to the ownerships show up different on the two client machines.
Server is set to allow all hosts and the firewalls turned off on all machines for test purposes.
Art
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
"You can tell whether a man is clever by his answers. You can tell whether a man is wise by his questions." â Naguib Mahfouz
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Well I have liloo machine upgraded to 9.3, same problem as before. What I don't understand is how when I go into yast, network services, nfs client and add a new server, put in the server ip address, then try the select remote file system, it comes up empty and that machine, but on my machine, it comes up correctly. Same network, server NFS server has * that can access the /home directory.
Art
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
"You can tell whether a man is clever by his answers. You can tell whether a man is wise by his questions." Naguib Mahfouz __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
On Sun, 2005-08-07 at 22:55 -0700, Simon Roberts wrote:
Well, you're probably right. If the browsing can't see it, there's something else wrong. Though just as an aside, if you upgrade a machine it seems very unlikely that the upgrade would alter your UIDs, so if they were mismatched before, they still are. The command id will tell you unequivocally and with trivial ease if that's the case.
The only other problem I've come across with NFS that seems a bit like this is that some NFSes would refuse to talk with any machine for which they could not find a proper name. So, if you didn't have the machine's hostname in /etc/hosts (for example) then NFS wouldn't talk with it. But I don't think that's a requirement any more.
Good luck, Simon
--- Art Fore <art.fore@comcast.net> wrote:
Did you create the users on the different machines explicitly to have the same UIDs? Or are you using NIS or some similar distributed name service thingy?
Log in as lilo on each machine and type "id" you want to see the same numbers for UID and GID on each system.
Cheers, Simon
--- Art Fore <art.fore@comcast.net> wrote:
I have a Suse 9.3 server running NFS server with two users, afore and lilo
From my client, also Suse 9.3, running NFS Client, I see the shared directories afore & lilo. File ownership is as it should be, afore for afore directory and lilo for lilo directory.
I Lilo's machine is running Suse 9.2. First of all, when I setup
On Sun, 2005-08-07 at 16:02 -0700, Simon Roberts wrote: the
NFS client in Yast and try to select for the file system, it cannot find anything. I enter the /home directory same as on my Suse 9.3 machine. When I finish, it takes a long time for Yast to start the services again.
I check the mount point, and the two directories are there, but afore as ownership of lilo and lilo folder has ownership of 2002!
So, why does the select remote filesystem not work in 9.2 and work in 9.3 and why to the ownerships show up different on the two client machines.
Server is set to allow all hosts and the firewalls turned off on all machines for test purposes.
Art
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
"You can tell whether a man is clever by his answers. You can tell whether a man is wise by his questions." — Naguib Mahfouz
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Well I have liloo machine upgraded to 9.3, same problem as before. What I don't understand is how when I go into yast, network services, nfs client and add a new server, put in the server ip address, then try the select remote file system, it comes up empty and that machine, but on my machine, it comes up correctly. Same network, server NFS server has * that can access the /home directory.
Art
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
"You can tell whether a man is clever by his answers. You can tell whether a man is wise by his questions." — Naguib Mahfouz
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
The upgrade was a new install, not just an upgrade from 9.2 to 9.3, although the UID is the same on the new install. I used the ip address of the server, although I did try the name of the server after adding it to the hosts file. No change. Art
On Sun, 2005-08-07 at 18:18 -0700, Art Fore wrote:
On Sun, 2005-08-07 at 16:02 -0700, Simon Roberts wrote:
Did you create the users on the different machines explicitly to have the same UIDs? Or are you using NIS or some similar distributed name service thingy?
Log in as lilo on each machine and type "id" you want to see the same numbers for UID and GID on each system.
Cheers, Simon
--- Art Fore <art.fore@comcast.net> wrote:
I have a Suse 9.3 server running NFS server with two users, afore and lilo
From my client, also Suse 9.3, running NFS Client, I see the shared directories afore & lilo. File ownership is as it should be, afore for afore directory and lilo for lilo directory.
I Lilo's machine is running Suse 9.2. First of all, when I setup the NFS client in Yast and try to select for the file system, it cannot find anything. I enter the /home directory same as on my Suse 9.3 machine. When I finish, it takes a long time for Yast to start the services again.
I check the mount point, and the two directories are there, but afore as ownership of lilo and lilo folder has ownership of 2002!
So, why does the select remote filesystem not work in 9.2 and work in 9.3 and why to the ownerships show up different on the two client machines.
Server is set to allow all hosts and the firewalls turned off on all machines for test purposes.
Art
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
"You can tell whether a man is clever by his answers. You can tell whether a man is wise by his questions." — Naguib Mahfouz
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Well I have liloo machine upgraded to 9.3, same problem as before. What I don't understand is how when I go into yast, network services, nfs client and add a new server, put in the server ip address, then try the select remote file system, it comes up empty and that machine, but on my machine, it comes up correctly. Same network, server NFS server has * that can access the /home directory.
Art
I have run route -n on lilo machine and it comes up the same as afore machine. Turned off firewall and ran iptables -F. Can ping 192.168.0.4 and get reply I can access the internet I can ssh to 192.168.0.4 from lilo machine. Tring to connect with Krds says it cannot find host. This worked in 9.2 before the new 9.3 installation NFS clinet setup in YAST still does not find either host or remote files system. Entering the info manually, it that it cannot mount fstab entry. Fstab entry is same for both client machines. I added the host name via the Yast network hosts setup and tried using host name, which I can ping, still same thing. So, what else to try? Art
participants (2)
-
Art Fore -
Simon Roberts