diff options
author | Andrew Tridgell <tridge@samba.org> | 1996-05-30 03:16:17 +0000 |
---|---|---|
committer | Andrew Tridgell <tridge@samba.org> | 1996-05-30 03:16:17 +0000 |
commit | 48c6b86d4c580d62ef46132dc04ce2b1d14e21e8 (patch) | |
tree | 6cf73c85e274ed4fd68e08e5dcdb22741c6a11a0 /docs | |
parent | 64c6a19923e43c8b0e3a3da4e56b0eb136f830d5 (diff) | |
download | samba-48c6b86d4c580d62ef46132dc04ce2b1d14e21e8.tar.gz samba-48c6b86d4c580d62ef46132dc04ce2b1d14e21e8.tar.xz samba-48c6b86d4c580d62ef46132dc04ce2b1d14e21e8.zip |
- added an entry on WinDD to samba.faq
- added a sample smb.conf from Thoralf.Freitag@remserv.rz.fhtw-berlin.de
- print the errno when you get a can't change directory error
- added installscripts.sh from James_K._Foote.PARC@xerox.com
Diffstat (limited to 'docs')
-rw-r--r-- | docs/samba.faq | 37 |
1 files changed, 37 insertions, 0 deletions
diff --git a/docs/samba.faq b/docs/samba.faq index e58c88bc18f..6e3cf2943aa 100644 --- a/docs/samba.faq +++ b/docs/samba.faq @@ -511,6 +511,43 @@ To syncronize your PC's clock with your Samba server: Each time you start your computer (or login for Win95) your PC will synchronize it's clock with your Samba server. + +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +* 4: Problems with WinDD, NTrigue, WinCenterPro etc + +All of the above programs are applications that sit on an NT box and +allow multiple users to access the NT GUI applications from remote +workstations (often over X). + +What has this got to do with Samba? The problem comes when these users +use filemanager to mount shares from a Samba server. The most common +symptom is that the first user to connect get correct file permissions +and has a nice day, but subsequent connections get logged in as the +same user as the first person to login. They find that they cannot +access files in their own home directory, but that they can access +files in the first users home directory (maybe not such a nice day +after all?) + +Why does this happen? The above products all share a common heritage +(and code base I believe). They all open just a single TCP based SMB +connection to the Samba server, and requests from all users are piped +over this connection. This is unfortunate, but not fatal. + +It means that if you run your Samba server in share level security +(the default) then things will definately break as described above. The +share level SMB security model has no provision for multiple user IDs +on the one SMB connection. See security_level.txt in the docs for more +info on share/user/server level security. + +If you run in user or server level security then you have a chance, +but only if you have a recent version of Samba (at least 1.9.15p6). In +older versions bugs in Samba meant you still would have had problems. + +If you have a trapdoor uid system in your OS then it will never work +properly. Samba needs to be able to switch uids on the connection and +it can't if your OS has a trapdoor uid system. You'll know this +because Samba will note it in your logs. + =============================================================================== SECTION FIVE: Specific client application problems ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |