[Samba] Automounter issues on Samba Server
I am having a problem with automounter failures on my Solaris Samba server. There is an automount path on the server that looks something like this: /dir1/dir2/dir3/dir4 Each dirN is an automount point with its own map. Dir4 contains some data, and some links to other automount points in /net Frequently (more than once per day, on a bad day), the automounter gets confused, or something, and will no longer mount *some* mount points in /net. More factoids follow: - This only happens on the Samba server. - The failed mount points are not always the same, but are always symlinked from .../dir4. - During these failures, the automounter is still working for other directories in /net, .../dir4, and elsewhere - The mount points in /net that are hung are still visible, but are not mounted, which is even more odd since -nobrowse is set for /net - they should not be visible at all if they are not mounted. - Stopping and restarted the automounter, using /etc/init.d/autofs *usually* resolves the problem temporarily. After about 5 or 6 times, however, this no longer works, and the entire system needs to be rebooted. - The system is an Ultra II, running Solaris 2.6 and Samba 2.2.8a Has anybody else experienced anything like this? Any ideas why it happens, or how to solve it? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] What's the solution? Multiple users accessing Samba from terminal server
I've seen a lot of mention of this problem on this list, and via google, but no solutions that I can follow. Can somebody please clue me in? I have a terminal server, with multiple users, who need to access shares from a Samba server. The first user has no problem, but subsequent users fail, unless I first kill the smbd process. Important trivia (maybe): 1 - We did not have this problem until we migrated our authentication from NT4 domain controllers to Active Directory. 2 - We only have this problem on Win2k terminal servers. XP systems, single user Win2k systems, and Win2003 terminal servers are OK. 3 - If one user has a drive mapped, and we kill smbd to allow a second user to map a drive, the first user CAN STILL MAP A DRIVE. This can be repeated over and over, to get many people mapped, but it is obviously a pain, and appears to have a temporary effect (apparently something cached somewhere) 4 - If we change the netbios name in smb.conf between each user, then we can also get multiple users to map drives. 5 - Our Samba servers are running Solaris 2.6, Samba v 2.2.8a TIA - A -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba CANNOT work with DNS round-robin (?)
This is posed as a question more that a statement, so if you can show that I'm wrong, please feel free to correct / flame me. A couple of years ago, I identified a file corruption issue caused by two people attempting to edit the same file via two different Samba servers. The file was in a shared file space, mounted on both Samba servers via NFS. The problem, I believe, lies in the fact that the oplock being held on Server A is not visible to Server B, and therefore the users were colliding with each other. Once I forced the users to use one or the other server, based on the files they were accessing, the problem vanished. I would like to set up a system of three Samba servers in a DNS round robin configuration, but I am concerned that this problem will resurface, because there is no way to tell which server the user will get, or to force a group of users onto a specific system. Any thoughts on this? Anthony Ciarochi -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Problem compiling 3.0.0
I am having trouble getting Samba 3.0.0 to compile. It is actually failing when it tries to link smbd. System: RedHat Linux: 2.4.9 i686 AFS client installed and running Openssl 0.9.7c installed at /ssl My configuration arguments: # ./configure --with-afs --with-fake-kaserver --with-ads --with-smbmount --enable-debug The Error: # make Using FLAGS = -g -I/usr/kerberos/include -Iinclude -I/dp/computing/proj/samba/samba-3.0.0/source/include -I/dp/computing/proj/samba/samba-3.0.0/source/ubiqx -I/dp/computing/proj/samba/samba-3.0.0/source/smbwrapper -I. -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -I/usr/kerberos/include -I/dp/computing/proj/samba/samba-3.0.0/source LIBS = -lcrypt -lresolv -lnsl -ldl -L/ssl -L/ssl/lib LDSHFLAGS = -shared -L/usr/kerberos/lib LDFLAGS = -L/usr/kerberos/lib Linking bin/smbd auth/pass_check.o: In function `afs_auth': /dp/computing/proj/samba/samba-3.0.0/source/auth/pass_check.c:51: undefined reference to `setpag' /dp/computing/proj/samba/samba-3.0.0/source/auth/pass_check.c:52: undefined reference to `ka_UserAuthenticateGeneral' collect2: ld returned 1 exit status make: *** [bin/smbd] Error 1 Has anybody run across this? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
