diff options
| -rw-r--r-- | docs/faq/sambafaq.sgml | 176 |
1 files changed, 84 insertions, 92 deletions
diff --git a/docs/faq/sambafaq.sgml b/docs/faq/sambafaq.sgml index b8bcf92741..618fecbcc3 100644 --- a/docs/faq/sambafaq.sgml +++ b/docs/faq/sambafaq.sgml @@ -4,7 +4,8 @@ First linuxdoc-sgml version, outline only v 0.6 25 Oct 1996 Dan Filled in from current text faq - + v 0.7 1 June 1997 Paul + Replicated changes in txt faq to sgml faq --> <article> @@ -13,12 +14,12 @@ <author>Paul Blackman, <tt>ictinus@lake.canberra.edu.au</tt> -<date>, v 0.5 +<date>, v 0.7 <abstract> This is the Frequently Asked Questions (FAQ) document for Samba, the free and very popular SMB server product. An SMB server allows file and printer connections from clients such as Windows, -OS/2, Linux and others. Current to version 1.9.16. Please send any +OS/2, Linux and others. Current to version 1.9.17. Please send any corrections to the author. </abstract> @@ -165,40 +166,41 @@ Many different platforms have run Samba successfully. The platforms most widely used and thus best tested are Linux and SunOS. At time of writing, the Makefile claimed support for: - - * SunOS - * Linux with shadow passwords - * Linux without shadow passwords - * SOLARIS - * SOLARIS 2.2 and above (aka SunOS 5) - * SVR4 - * ULTRIX - * OSF1 (alpha only) - * OSF1 with NIS and Fast Crypt (alpha only) - * OSF1 V2.0 Enhanced Security (alpha only) - * AIX - * BSDI - * NetBSD - * NetBSD 1.0 - * SEQUENT - * HP-UX - * SGI - * SGI IRIX 4.x.x - * SGI IRIX 5.x.x - * FreeBSD - * NeXT 3.2 and above - * NeXT OS 2.x - * NeXT OS 3.0 - * ISC SVR3V4 (POSIX mode) - * ISC SVR3V4 (iBCS2 mode) - * A/UX 3.0 - * SCO with shadow passwords. - * SCO with shadow passwords, without YP. - * SCO with TCB passwords - * SCO 3.2v2 (ODT 1.1) with TCP passwords - * intergraph - * DGUX - * Apollo Domain/OS sr10.3 (BSD4.3) +<itemize> +<item> SunOS +<item> Linux with shadow passwords +<item> Linux without shadow passwords +<item> SOLARIS +<item> SOLARIS 2.2 and above (aka SunOS 5) +<item> SVR4 +<item> ULTRIX +<item> OSF1 (alpha only) +<item> OSF1 with NIS and Fast Crypt (alpha only) +<item> OSF1 V2.0 Enhanced Security (alpha only) +<item> AIX +<item> BSDI +<item> NetBSD +<item> NetBSD 1.0 +<item> SEQUENT +<item> HP-UX +<item> SGI +<item> SGI IRIX 4.x.x +<item> SGI IRIX 5.x.x +<item> FreeBSD +<item> NeXT 3.2 and above +<item> NeXT OS 2.x +<item> NeXT OS 3.0 +<item> ISC SVR3V4 (POSIX mode) +<item> ISC SVR3V4 (iBCS2 mode) +<item> A/UX 3.0 +<item> SCO with shadow passwords. +<item> SCO with shadow passwords, without YP. +<item> SCO with TCB passwords +<item> SCO 3.2v2 (ODT 1.1) with TCP passwords +<item> intergraph +<item> DGUX +<item> Apollo Domain/OS sr10.3 (BSD4.3) +</itemize> <sect1> How can I find out more about Samba? <p> <label id="more"> @@ -304,9 +306,9 @@ hungry sniffer dogs but it will have been a noble gesture. <sect1>I can't see the Samba server in any browse lists!<p> <label id="no_browse"> -*** Until the FAQ can be updated, please check the file: -*** ftp://samba.anu.edu.au/pub/samba/BROWSING.txt -*** for more information on browsing. + See ftp://samba.anu.edu.au/pub/samba/BROWSING.txt + for more information on browsing. Browsing.txt can also be found + in the docs directory of the Samba source. If your GUI client does not permit you to select non-browsable servers, you may need to do so on the command line. For example, under @@ -319,12 +321,10 @@ The details of how to do this and the specific syntax varies from client to client - check your client's documentation. <sect1>Some files that I KNOW are on the server doesn't show up when I -view the files from my client!<p> -<label id="missing_files"> +view the files from my client! <p> <label id="missing_files"> <sect1>Some files on the server show up with really wierd filenames when -I view the files from my client!<p> -<label id="strange_filenames"> +I view the files from my client! <p> <label id="strange_filenames"> If you check what files are not showing up, you will note that they are files which contain upper case letters or which are otherwise not @@ -379,18 +379,15 @@ trying to connect to (consult your system administrator). Assuming it exists and you specified it correctly (read your client's doco on how to specify a service name correctly), read on: - * Many clients cannot accept or use service names longer than -eight - characters. - * Many clients cannot accept or use service names containing -spaces. - * Some servers (not Samba though) are case sensitive with service -names. - * Some clients force service names into upper case. +<itemize> +<item> Many clients cannot accept or use service names longer than eight characters. +<item> Many clients cannot accept or use service names containing spaces. +<item> Some servers (not Samba though) are case sensitive with service names. +<item> Some clients force service names into upper case. +</itemize> <sect1>My client reports "cannot find domain controller", "cannot log -on to the network" or similar <p> -<label id="cant_see_net"> +on to the network" or similar <p> <label id="cant_see_net"> Nothing is wrong - Samba does not implement the primary domain name controller stuff for several reasons, including the fact that the @@ -449,7 +446,7 @@ as a strictly temporary solution. In earlier Samba versions there were some difficulties with the very latest Microsoft products, particularly Excel 5 and Word for Windows 6. These should have all been solved. If not then please let Andrew -Tridgell know. +Tridgell know via email at 'samba-bugs@anu.edu.au'. <sect1>My "server string" doesn't seem to be recognised<p> <label id="bad_server_string"> @@ -458,9 +455,9 @@ my client reports the default setting, eg. "Samba 1.9.15p4", instead of what I have changed it to in the smb.conf file. You need to use the -C option in nmbd. The "server string" affects -what smbd puts out and -C affects what nmbd puts out. In a future -version these will probably be combined and -C will be removed, but -for now use -C +what smbd puts out and -C affects what nmbd puts out. +Current versions of Samba (1.9.16p11 +) have combined these options into +the "server string" field of smb.conf, -C for nmbd is now obsolete. <sect1>My client reports "This server is not configured to list shared resources" <p> <label id="cant_list_shares"> @@ -510,30 +507,23 @@ as uid 65535 will actually run as root. This is not good! <sect1>Are any Macintosh clients for Samba<p> <label id="mac_clients"> -In Rob Newberry's words (rob@eats.com, Sun, 4 Dec 1994): - -The answer is "No." Samba speaks SMB, the protocol used for Microsoft -networks. The Macintosh has ALWAYS spoken Appletalk. Even with -Microsoft "services for Macintosh", it has been a matter of making the -server speak Appletalk. It is the same for Novell Netware and the -Macintosh, although I believe Novell has (VERY LATE) released an -extension for the Mac to let it speak IPX. - -In future Apple System Software, you may see support for other -protocols, such as SMB -- Applet is working on a new networking -architecture that will --> -- make it easier to support additional -protocols. But it's not here yet. - -Now, the nice part is that if you want your Unix machine to speak -Appletalk, there are several options. "Netatalk" and "CAP" are free, -and available on the net. There are also several commercial options, -such as "PacerShare" and "Helios" (I think). In any case, you'll have -to look around for a server, not anything for the Mac. - -Depending on you OS, some of these may not help you. I am currently -coordinating the effort to get CAP working with Native Ethertalk under -Linux, but we're not done yet. - +lkcl - update 09mar97 - the answer is "Yes!". Thursby now have a +CIFS Client / Server - see www.thursby.com. They test it against +Windows 95, Windows NT and samba for compatibility issues. At +present, DAVE is at version 1.0.0. DAVE version 1.0.1 is in beta, +and will be released in April 97 (the speed of finder copies has +been greatly enhanced, and there are bug-fixes included). + +Alternatives - There are two free implementations of AppleTalk for +several kinds of UNIX machnes, and several more commercial ones. +These products allow you to run file services and print services +natively to Macintosh users, with no additional support required on +the Macintosh. The two free omplementations are Netatalk, +http://www.umich.edu/~rsug/netatalk/, and CAP, +http://www.cs.mu.oz.au/appletalk/atalk.html. What Samba offers +MS Windows users, these packages offer to Macs. For more info on +these packages, Samba, and Linux (and other UNIX-based systems) +see http://www.eats.com/linux_mac_win.html <sect1>"Session request failed (131,130)" error<p> <label id="sess_req_fail"> @@ -569,21 +559,23 @@ it. To syncronize your PC's clock with your Samba server: -* Copy timesync.pif to your windows directory - * timesync.pif can be found at: +<itemize> +<item> Copy timesync.pif to your windows directory + <item> timesync.pif can be found at: http://samba.canberra.edu.au/pub/samba/binaries/miscellaneous/timesync.pif -* Add timesync.pif to your 'Start Up' group/folder -* Open the properties dialog box for the program/icon - * Make sure the 'Run Minimized' option is set in program -'Properties' - * Change the command line section that reads \\sambahost to reflect -the name - of your server. -* Close the properties dialog box by choosing 'OK' +<item> Add timesync.pif to your 'Start Up' group/folder +<item> Open the properties dialog box for the program/icon +<item> Make sure the 'Run Minimized' option is set in program 'Properties' +<iteM> Change the command line section that reads \\sambahost to reflect the name of your server. +<item> Close the properties dialog box by choosing 'OK' Each time you start your computer (or login for Win95) your PC will synchronize it's clock with your Samba server. +Alternativley, if you clients support Domain Logons, you can setup Domain Logons with Samba + - see: ftp://samba.anu.edu.au/pub/samba/BROWSING.txt *** for more information. +Then add NET TIME \\%L /SET /YES as one of the lines in the logon script. + <sect1>Problems with WinDD, NTrigue, WinCenterPro etc<p> <label id="multiple_session_clients"> |