RE: [Samba] Remote Share Access Problems
Turns out it was a PATH MTU issue when packets were crossing the router from one VLAN to the next. Fixed the MTU issue and everything worked fine. Should have never doubted Samba ;) _ From: Peter Olivia [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 22, 2004 1:44 PM To: 'samba@lists.samba.org' Subject: [Samba] Remote Share Access Problems I have been trying to access home dir shares on my Samba PDC from a windows 2003 server that is on a remote subnet with no success. I am running SAMBA 3.0.9 as an LDAP PDC (and as of today 3.0.10 to try fix this issue). On the server in question, these dirs are local to the server, but I also NFS export them to other servers. I can access other shares with identical uid/gids and permissions on the same server. But if I try to connect to my home dirs, it sits forever until it comes back with \\server\share is not accessible ... the specified network name is no longer available. If I create a new file in the accessible shares, it saves it as the correct uid/gid. If I move the server to the same subnet as the PDC, all works just fine. My first guess was that something was cached on the server that was causing my grief. I tried removing any somewhat recent tdb and dat files that were in /var/cache/samba to no avail. I finally rebooted to see if I could make the shares work. Nothing seems to allow access to the existing dirs. If I recreate the dirs with identical names, they work. I just hate to recreate all the homedirs and migrate data just to have it return again later on. Could it be a locking issue? Any ideas where to turn? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Remote Share Access Problems
I have been trying to access home dir shares on my Samba PDC from a windows 2003 server that is on a remote subnet with no success. I am running SAMBA 3.0.9 as an LDAP PDC (and as of today 3.0.10 to try fix this issue). On the server in question, these dirs are local to the server, but I also NFS export them to other servers. I can access other shares with identical uid/gids and permissions on the same server. But if I try to connect to my home dirs, it sits forever until it comes back with \\server\share is not accessible ... the specified network name is no longer available. If I create a new file in the accessible shares, it saves it as the correct uid/gid. If I move the server to the same subnet as the PDC, all works just fine. My first guess was that something was cached on the server that was causing my grief. I tried removing any somewhat recent tdb and dat files that were in /var/cache/samba to no avail. I finally rebooted to see if I could make the shares work. Nothing seems to allow access to the existing dirs. If I recreate the dirs with identical names, they work. I just hate to recreate all the homedirs and migrate data just to have it return again later on. Could it be a locking issue? Any ideas where to turn? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba + OpenLDAP + Automount question
Here is what I did on my setup: 1) Mounted a base share for all samba data (i.e. home dirs and profiles) in /home/samba so that I ended up with /home/samba/home/$USER and /home/samba/profiles/$USER (where $USER is the login name of the user) 2) Pointed all LDAP users home dirs to /home/samba/home/$USER and their profiles to /home/samba/profiles/$USER 3) All I needed to do then is setup shares (and the logon path and logon home entries) a. [homes] path=/home/samba/home/%u b. [Profiles] path=/home/samba/profiles The home dirs get automounted at user logon as the logon home drive. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
