1<!doctype linuxdoc system> <!-- -*- SGML -*- --> 2<!-- 3 v 0.5 18 Oct 1996 Dan Shearer Dan.Shearer@unisa.edu.au 4 First linuxdoc-sgml version, outline only 5 v 0.6 25 Oct 1996 Dan 6 Filled in from current text faq 7 v 0.7 1 June 1997 Paul 8 Replicated changes in txt faq to sgml faq 9 9 June 1997 Paul 10 Lots of changes, added doco list, updated compatible systems list 11 added NT SP3 entry, added Year 2000 entry, Getting ready for 1.9.17 12 v 0.8 7th Oct 97 Paul 13 changed samba.canberra entries to samba.anu.../samba/ 14--> 15 16<article> 17 18<title> Samba FAQ 19 20<author>Paul Blackman, <tt>ictinus@samba.org</tt> 21 22<date>v 0.8, June '97 23 24<abstract> This is the Frequently Asked Questions (FAQ) document for 25Samba, the free and very popular SMB server product. An SMB server 26allows file and printer connections from clients such as Windows, 27OS/2, Linux and others. Current to version 1.9.17. Please send any 28corrections to the author. 29</abstract> 30 31<toc> 32 33<sect> General Information<p> <label id="general_info"> 34 35All about Samba - what it is, how to get it, related sources of 36information, how to understand the version numbering scheme, pizza 37details 38 39<sect1> What is Samba? <p> <label id="introduction"> 40Samba is a suite of programs which work together to allow clients to 41access to a server's filespace and printers via the SMB (Server 42Message Block) protocol. Initially written for Unix, Samba now also 43runs on Netware, OS/2 and VMS. 44 45In practice, this means that you can redirect disks and printers to 46Unix disks and printers from Lan Manager clients, Windows for 47Workgroups 3.11 clients, Windows NT clients, Linux clients and OS/2 48clients. There is also a generic Unix client program supplied as part 49of the suite which allows Unix users to use an ftp-like interface to 50access filespace and printers on any other SMB servers. This gives the 51capability for these operating systems to behave much like a LAN 52Server or Windows NT Server machine, only with added functionality and 53flexibility designed to make life easier for administrators. 54 55The components of the suite are (in summary): 56 57<itemize> 58<item><bf>smbd</bf>, the SMB server. This handles actual connections from clients, doing all the file, permission and username work 59<item><bf>nmbd</bf>, the Netbios name server, which helps clients locate servers, doing the browsing work and managing domains as this capability is being built into Samba 60<item><bf>smbclient</bf>, the Unix-hosted client program 61<item><bf>smbrun</bf>, a little 'glue' program to help the server run external programs 62<item><bf>testprns</bf>, a program to test server access to printers 63<item><bf>testparms</bf>, a program to test the Samba configuration file for correctness 64<item><bf>smb.conf</bf>, the Samba configuration file 65<item><bf>smbprint</bf>, a sample script to allow a Unix host to use smbclient to print to an SMB server 66<item><bf>Documentation!</bf> DON'T neglect to read it - you will save a great deal of time! 67</itemize> 68 69The suite is supplied with full source (of course!) and is GPLed. 70 71The primary creator of the Samba suite is Andrew Tridgell. Later 72versions incorporate much effort by many net.helpers. The man pages 73and this FAQ were originally written by Karl Auer. 74 75<sect1> What is the current version of Samba? <p><label id="current_version"> 76At time of writing, the current version was 1.9.17. If you want to be 77sure check the bottom of the change-log file. <url url="ftp://samba.org/pub/samba/alpha/change-log"> 78 79For more information see <ref id="version_nums" name="What do the 80version numbers mean?"> 81 82<sect1> Where can I get it? <p> <label id="where"> 83The Samba suite is available via anonymous ftp from 84samba.org. The latest and greatest versions of the suite are in 85the directory: 86 87/pub/samba/ 88 89Development (read "alpha") versions, which are NOT necessarily stable 90and which do NOT necessarily have accurate documentation, are 91available in the directory: 92 93/pub/samba/alpha 94 95Note that binaries are NOT included in any of the above. Samba is 96distributed ONLY in source form, though binaries may be available from 97other sites. Recent versions of some Linux distributions, for example, 98do contain Samba binaries for that platform. 99 100<sect1> What do the version numbers mean? <p> <label id="version_nums"> 101It is not recommended that you run a version of Samba with the word 102"alpha" in its name unless you know what you are doing and are willing 103to do some debugging. Many, many people just get the latest 104recommended stable release version and are happy. If you are brave, by 105all means take the plunge and help with the testing and development - 106but don't install it on your departmental server. Samba is typically 107very stable and safe, and this is mostly due to the policy of many 108public releases. 109 110How the scheme works: 111<enum> 112<item>When major changes are made the version number is increased. For 113example, the transition from 1.9.15 to 1.9.16. However, this version 114number will not appear immediately and people should continue to use 1151.9.15 for production systems (see next point.) 116 117<item>Just after major changes are made the software is considered 118unstable, and a series of alpha releases are distributed, for example 1191.9.16alpha1. These are for testing by those who know what they are 120doing. The "alpha" in the filename will hopefully scare off those who 121are just looking for the latest version to install. 122 123<item>When Andrew thinks that the alphas have stabilised to the point 124where he would recommend new users install it, he renames it to the 125same version number without the alpha, for example 1.9.16. 126 127<item>Inevitably bugs are found in the "stable" releases and minor patch 128levels are released which give us the pXX series, for example 1.9.16p2. 129</enum> 130So the progression goes: 131<verb> 132 1.9.15p7 (production) 133 1.9.15p8 (production) 134 1.9.16alpha1 (test sites only) 135 : 136 1.9.16alpha20 (test sites only) 137 1.9.16 (production) 138 1.9.16p1 (production) 139</verb> 140The above system means that whenever someone looks at the samba ftp 141site they will be able to grab the highest numbered release without an 142alpha in the name and be sure of getting the current recommended 143version. 144 145<sect1> What platforms are supported? <p> <label id="platforms"> 146Many different platforms have run Samba successfully. The platforms 147most widely used and thus best tested are Linux and SunOS. 148 149At time of writing, the Makefile claimed support for: 150<itemize> 151<item> A/UX 3.0 152<item> AIX 153<item> Altos Series 386/1000 154<item> Amiga 155<item> Apollo Domain/OS sr10.3 156<item> BSDI 157<item> B.O.S. (Bull Operating System) 158<item> Cray, Unicos 8.0 159<item> Convex 160<item> DGUX. 161<item> DNIX. 162<item> FreeBSD 163<item> HP-UX 164<item> Intergraph. 165<item> Linux with/without shadow passwords and quota 166<item> LYNX 2.3.0 167<item> MachTen (a unix like system for Macintoshes) 168<item> Motorola 88xxx/9xx range of machines 169<item> NetBSD 170<item> NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach). 171<item> OS/2 using EMX 0.9b 172<item> OSF1 173<item> QNX 4.22 174<item> RiscIX. 175<item> RISCOs 5.0B 176<item> SEQUENT. 177<item> SCO (including: 3.2v2, European dist., OpenServer 5) 178<item> SGI. 179<item> SMP_DC.OSx v1.1-94c079 on Pyramid S series 180<item> SONY NEWS, NEWS-OS (4.2.x and 6.1.x) 181<item> SUNOS 4 182<item> SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later') 183<item> Sunsoft ISC SVR3V4 184<item> SVR4 185<item> System V with some berkely extensions (Motorola 88k R32V3.2). 186<item> ULTRIX. 187<item> UNIXWARE 188<item> UXP/DS 189</itemize> 190 191<sect1> How can I find out more about Samba? <p> <label id="more"> 192There are a number of places to look for more information on Samba, including: 193<itemize> 194<item>Two mailing lists devoted to discussion of Samba-related matters. 195<item>The newsgroup, comp.protocols.smb, which has a great deal of discussion on Samba. 196<item>The WWW site 'SAMBA Web Pages' at <url url="http://samba.edu.au/samba/"> includes: 197 <itemize> 198 <item>Links to man pages and documentation, including this FAQ 199 <item>A comprehensive survey of Samba users. 200 <item>A searchable hypertext archive of the Samba mailing list. 201 <item>Links to Samba source code, binaries, and mirrors of both. 202 </itemize> 203<item>The long list of topic documentation. These files can be found in the 'docs' directory of the Samba source, or at <url url="ftp://samba.org/pub/samba/docs/"> 204 <itemize> 205 <item><url url="ftp://samba.org/pub/samba/docs/Application_Serving.txt" name="Application_Serving.txt"> 206 <item><url url="ftp://samba.org/pub/samba/docs/BROWSING.txt" name="BROWSING.txt"> 207 <item><url url="ftp://samba.org/pub/samba/docs/BUGS.txt" name="BUGS.txt"> 208 <item><url url="ftp://samba.org/pub/samba/docs/DIAGNOSIS.txt" name="DIAGNOSIS.txt"> 209 <item><url url="ftp://samba.org/pub/samba/docs/DNIX.txt" name="DNIX.txt"> 210 <item><url url="ftp://samba.org/pub/samba/docs/DOMAIN.txt" name="DOMAIN.txt"> 211 <item><url url="ftp://samba.org/pub/samba/docs/DOMAIN_CONTROL.txt" name="CONTROL.txt"> 212 <item><url url="ftp://samba.org/pub/samba/docs/ENCRYPTION.txt" name="ENCRYPTION.txt"> 213 <item><url url="ftp://samba.org/pub/samba/docs/Faxing.txt" name="Faxing.txt"> 214 <item><url url="ftp://samba.org/pub/samba/docs/GOTCHAS.txt" name="GOTCHAS.txt"> 215 <item><url url="ftp://samba.org/pub/samba/docs/HINTS.txt" name="HINTS.txt"> 216 <item><url url="ftp://samba.org/pub/samba/docs/INSTALL.sambatar" name="INSTALL.sambatar"> 217 <item><url url="ftp://samba.org/pub/samba/docs/INSTALL.txt" name="INSTALL.txt"> 218 <item><url url="ftp://samba.org/pub/samba/docs/MIRRORS" name="MIRRORS"> 219 <item><url url="ftp://samba.org/pub/samba/docs/NetBIOS.txt" name="NetBIOS.txt"> 220 <item><url url="ftp://samba.org/pub/samba/docs/OS2.txt" name="OS2.txt"> 221 <item><url url="ftp://samba.org/pub/samba/docs/PROJECTS" name="PROJECTS"> 222 <item><url url="ftp://samba.org/pub/samba/docs/Passwords.txt" name="Passwords.txt"> 223 <item><url url="ftp://samba.org/pub/samba/docs/Printing.txt" name="Printing.txt"> 224 <item><url url="ftp://samba.org/pub/samba/docs/README.DCEDFS" name="README.DCEDFS"> 225 <item><url url="ftp://samba.org/pub/samba/docs/README.OS2" name="README.OS2"> 226 <item><url url="ftp://samba.org/pub/samba/docs/README.jis" name="README.jis"> 227 <item><url url="ftp://samba.org/pub/samba/docs/README.sambatar" name="README.sambatar"> 228 <item><url url="ftp://samba.org/pub/samba/docs/SCO.txt" name="SCO.txt"> 229 <item><url url="ftp://samba.org/pub/samba/docs/SMBTAR.notes" name="SMBTAR.notes"> 230 <item><url url="ftp://samba.org/pub/samba/docs/Speed.txt" name="Speed.txt"> 231 <item><url url="ftp://samba.org/pub/samba/docs/Support.txt" name="Support.txt"> 232 <item><url url="ftp://samba.org/pub/samba/docs/THANKS" name="THANKS"> 233 <item><url url="ftp://samba.org/pub/samba/docs/Tracing.txt" name="Tracing.txt"> 234 <item><url url="ftp://samba.org/pub/samba/docs/UNIX-SMB.txt" name="SMB.txt"> 235 <item><url url="ftp://samba.org/pub/samba/docs/Warp.txt" name="Warp.txt"> 236 <item><url url="ftp://samba.org/pub/samba/docs/WinNT.txt" name="WinNT.txt"> 237 <item><url url="ftp://samba.org/pub/samba/docs/history" name="history"> 238 <item><url url="ftp://samba.org/pub/samba/docs/security_level.txt" name="level.txt"> 239 <item><url url="ftp://samba.org/pub/samba/docs/wfw_slip.htm" name="slip.htm"> 240 </itemize> 241</itemize> 242 243<sect1>How do I subscribe to the Samba Mailing Lists?<p><label id="mailinglist"> 244Send email to <htmlurl url="mailto:listproc@samba.org" name="listproc@samba.org">. Make sure the subject line is 245blank, and include the following two lines in the body of the message: 246<tscreen><verb> 247subscribe samba Firstname Lastname 248subscribe samba-announce Firstname Lastname 249</verb></tscreen> 250Obviously you should substitute YOUR first name for "Firstname" and 251YOUR last name for "Lastname"! Try not to send any signature stuff, it 252sometimes confuses the list processor. 253 254The samba list is a digest list - every eight hours or so it 255regurgitates a single message containing all the messages that have 256been received by the list since the last time and sends a copy of this 257message to all subscribers. 258 259If you stop being interested in Samba, please send another email to 260<htmlurl url="mailto:listproc@samba.org" name="listproc@samba.org">. Make sure the subject line is blank, and 261include the following two lines in the body of the message: 262<tscreen><verb> 263unsubscribe samba 264unsubscribe samba-announce 265</verb></tscreen> 266The <bf>From:</bf> line in your message <em>MUST</em> be the same address you used when 267you subscribed. 268 269<sect1> Something's gone wrong - what should I do? <p> <label id="wrong"> 270<bf>[#] *** IMPORTANT! *** [#]</bf> 271<p>DO NOT post messages on mailing lists or in newsgroups until you have 272carried out the first three steps given here! 273 274Firstly, see if there are any likely looking entries in this FAQ! If 275you have just installed Samba, have you run through the checklist in 276<url url="ftp://samba.org/pub/samba/DIAGNOSIS.txt" name="DIAGNOSIS.txt">? It can save you a lot of time and effort. 277DIAGNOSIS.txt can also be found in the docs directory of the Samba distribution. 278 279Secondly, read the man pages for smbd, nmbd and smb.conf, looking for 280topics that relate to what you are trying to do. 281 282Thirdly, if there is no obvious solution to hand, try to get a look at 283the log files for smbd and/or nmbd for the period during which you 284were having problems. You may need to reconfigure the servers to 285provide more extensive debugging information - usually level 2 or 286level 3 provide ample debugging info. Inspect these logs closely, 287looking particularly for the string "Error:". 288 289Fourthly, if you still haven't got anywhere, ask the mailing list or 290newsgroup. In general nobody minds answering questions provided you 291have followed the preceding steps. It might be a good idea to scan the 292archives of the mailing list, which are available through the Samba 293web site described in the previous 294section. 295 296If you successfully solve a problem, please mail the FAQ maintainer a 297succinct description of the symptom, the problem and the solution, so 298I can incorporate it in the next version. 299 300If you make changes to the source code, _please_ submit these patches 301so that everyone else gets the benefit of your work. This is one of 302the most important aspects to the maintainence of Samba. Send all 303patches to <htmlurl url="mailto:samba@samba.org" name="samba@samba.org">. Do not send patches to Andrew Tridgell or any 304other individual, they may be lost if you do. 305 306<sect1> Pizza supply details <p> <label id="pizza"> 307Those who have registered in the Samba survey as "Pizza Factory" will 308already know this, but the rest may need some help. Andrew doesn't ask 309for payment, but he does appreciate it when people give him 310pizza. This calls for a little organisation when the pizza donor is 311twenty thousand kilometres away, but it has been done. 312 313Method 1: Ring up your local branch of an international pizza chain 314and see if they honour their vouchers internationally. Pizza Hut do, 315which is how the entire Canberra Linux Users Group got to eat pizza 316one night, courtesy of someone in the US 317 318Method 2: Ring up a local pizza shop in Canberra and quote a credit 319card number for a certain amount, and tell them that Andrew will be 320collecting it (don't forget to tell him.) One kind soul from Germany 321did this. 322 323Method 3: Purchase a pizza voucher from your local pizza shop that has 324no international affiliations and send it to Andrew. It is completely 325useless but he can hang it on the wall next to the one he already has 326from Germany :-) 327 328Method 4: Air freight him a pizza with your favourite regional 329flavours. It will probably get stuck in customs or torn apart by 330hungry sniffer dogs but it will have been a noble gesture. 331 332<sect>Compiling and installing Samba on a Unix host<p><label id="unix_install"> 333 334<sect1>I can't see the Samba server in any browse lists!<p><label id="no_browse"> 335 See <url url="ftp://samba.org/pub/samba/BROWSING.txt" name="BROWSING.txt"> 336 for more information on browsing. Browsing.txt can also be found 337 in the docs directory of the Samba source. 338 339If your GUI client does not permit you to select non-browsable 340servers, you may need to do so on the command line. For example, under 341Lan Manager you might connect to the above service as disk drive M: 342thusly: 343<tscreen><verb> 344 net use M: \\mary\fred 345</verb></tscreen> 346The details of how to do this and the specific syntax varies from 347client to client - check your client's documentation. 348 349<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"> 350See the next question. 351<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"> 352If you check what files are not showing up, you will note that they 353are files which contain upper case letters or which are otherwise not 354DOS-compatible (ie, they are not legal DOS filenames for some reason). 355 356The Samba server can be configured either to ignore such files 357completely, or to present them to the client in "mangled" form. If you 358are not seeing the files at all, the Samba server has most likely been 359configured to ignore them. Consult the man page smb.conf(5) for 360details of how to change this - the parameter you need to set is 361"mangled names = yes". 362 363<sect1>My client reports "cannot locate specified computer" or similar<p><label id="cant_see_server"> 364This indicates one of three things: You supplied an incorrect server 365name, the underlying TCP/IP layer is not working correctly, or the 366name you specified cannot be resolved. 367 368After carefully checking that the name you typed is the name you 369should have typed, try doing things like pinging a host or telnetting 370to somewhere on your network to see if TCP/IP is functioning OK. If it 371is, the problem is most likely name resolution. 372 373If your client has a facility to do so, hardcode a mapping between the 374hosts IP and the name you want to use. For example, with Man Manager 375or Windows for Workgroups you would put a suitable entry in the file 376LMHOSTS. If this works, the problem is in the communication between 377your client and the netbios name server. If it does not work, then 378there is something fundamental wrong with your naming and the solution 379is beyond the scope of this document. 380 381If you do not have any server on your subnet supplying netbios name 382resolution, hardcoded mappings are your only option. If you DO have a 383netbios name server running (such as the Samba suite's nmbd program), 384the problem probably lies in the way it is set up. Refer to Section 385Two of this FAQ for more ideas. 386 387By the way, remember to REMOVE the hardcoded mapping before further 388tests :-) 389 390<sect1>My client reports "cannot locate specified share name" or similar<p> <label id="cant_see_share"> 391This message indicates that your client CAN locate the specified 392server, which is a good start, but that it cannot find a service of 393the name you gave. 394 395The first step is to check the exact name of the service you are 396trying to connect to (consult your system administrator). Assuming it 397exists and you specified it correctly (read your client's doco on how 398to specify a service name correctly), read on: 399 400<itemize> 401<item> Many clients cannot accept or use service names longer than eight characters. 402<item> Many clients cannot accept or use service names containing spaces. 403<item> Some servers (not Samba though) are case sensitive with service names. 404<item> Some clients force service names into upper case. 405</itemize> 406 407<sect1>My client reports "cannot find domain controller", "cannot log on to the network" or similar <p> <label id="cant_see_net"> 408Nothing is wrong - Samba does not implement the primary domain name 409controller stuff for several reasons, including the fact that the 410whole concept of a primary domain controller and "logging in to a 411network" doesn't fit well with clients possibly running on multiuser 412machines (such as users of smbclient under Unix). Having said that, 413several developers are working hard on building it in to the next 414major version of Samba. If you can contribute, send a message to 415<htmlurl url="mailto:samba@samba.org" name="samba@samba.org"> ! 416 417Seeing this message should not affect your ability to mount redirected 418disks and printers, which is really what all this is about. 419 420For many clients (including Windows for Workgroups and Lan Manager), 421setting the domain to STANDALONE at least gets rid of the message. 422 423<sect1>Printing doesn't work :-(<p> <label id="no_printing"> 424Make sure that the specified print command for the service you are 425connecting to is correct and that it has a fully-qualified path (eg., 426use "/usr/bin/lpr" rather than just "lpr"). 427 428Make sure that the spool directory specified for the service is 429writable by the user connected to the service. In particular the user 430"nobody" often has problems with printing, even if it worked with an 431earlier version of Samba. Try creating another guest user other than 432"nobody". 433 434Make sure that the user specified in the service is permitted to use 435the printer. 436 437Check the debug log produced by smbd. Search for the printer name and 438see if the log turns up any clues. Note that error messages to do with 439a service ipc$ are meaningless - they relate to the way the client 440attempts to retrieve status information when using the LANMAN1 441protocol. 442 443If using WfWg then you need to set the default protocol to TCP/IP, not 444Netbeui. This is a WfWg bug. 445 446If using the Lanman1 protocol (the default) then try switching to 447coreplus. Also not that print status error messages don't mean 448printing won't work. The print status is received by a different 449mechanism. 450 451<sect1>My programs install on the server OK, but refuse to work properly<p><label id="programs_wont_run"> 452There are numerous possible reasons for this, but one MAJOR 453possibility is that your software uses locking. Make sure you are 454using Samba 1.6.11 or later. It may also be possible to work around 455the problem by setting "locking=no" in the Samba configuration file 456for the service the software is installed on. This should be regarded 457as a strictly temporary solution. 458 459In earlier Samba versions there were some difficulties with the very 460latest Microsoft products, particularly Excel 5 and Word for Windows 4616. These should have all been solved. If not then please let Andrew 462Tridgell know via email at <htmlurl url="mailto:samba@samba.org" name="samba@samba.org">. 463 464<sect1>My "server string" doesn't seem to be recognised<p><label id="bad_server_string"> 465OR My client reports the default setting, eg. "Samba 1.9.15p4", instead 466of what I have changed it to in the smb.conf file. 467 468You need to use the -C option in nmbd. The "server string" affects 469what smbd puts out and -C affects what nmbd puts out. 470 471Current versions of Samba (1.9.16 +) have combined these options into 472the "server string" field of smb.conf, -C for nmbd is now obsolete. 473 474<sect1>My client reports "This server is not configured to list shared resources" <p> <label id="cant_list_shares"> 475Your guest account is probably invalid for some reason. Samba uses the 476guest account for browsing in smbd. Check that your guest account is 477valid. 478 479See also 'guest account' in smb.conf man page. 480 481<sect1>Log message "you appear to have a trapdoor uid system" <p><label id="trapdoor_uid"> 482This can have several causes. It might be because you are using a uid 483or gid of 65535 or -1. This is a VERY bad idea, and is a big security 484hole. Check carefully in your /etc/passwd file and make sure that no 485user has uid 65535 or -1. Especially check the "nobody" user, as many 486broken systems are shipped with nobody setup with a uid of 65535. 487 488It might also mean that your OS has a trapdoor uid/gid system :-) 489 490This means that once a process changes effective uid from root to 491another user it can't go back to root. Unfortunately Samba relies on 492being able to change effective uid from root to non-root and back 493again to implement its security policy. If your OS has a trapdoor uid 494system this won't work, and several things in Samba may break. Less 495things will break if you use user or server level security instead of 496the default share level security, but you may still strike 497problems. 498 499The problems don't give rise to any security holes, so don't panic, 500but it does mean some of Samba's capabilities will be unavailable. 501In particular you will not be able to connect to the Samba server as 502two different uids at once. This may happen if you try to print as a 503"guest" while accessing a share as a normal user. It may also affect 504your ability to list the available shares as this is normally done as 505the guest user. 506 507Complain to your OS vendor and ask them to fix their system. 508 509Note: the reason why 65535 is a VERY bad choice of uid and gid is that 510it casts to -1 as a uid, and the setreuid() system call ignores (with 511no error) uid changes to -1. This means any daemon attempting to run 512as uid 65535 will actually run as root. This is not good! 513 514<sect>Common client questions<p> <label id="client_questions"> 515 516<sect1>Are there any Macintosh clients for Samba?<p> <label id="mac_clients"> 517Yes! Thursby now have a CIFS Client / Server called DAVE - see <url url="http://www.thursby.com/">. 518They test it against Windows 95, Windows NT and samba for compatibility issues. 519At the time of writing, DAVE was at version 1.0.1. The 1.0.0 to 1.0.1 update is available 520as a free download from the Thursby web site (the speed of finder copies has 521been greatly enhanced, and there are bug-fixes included). 522 523Alternatives - There are two free implementations of AppleTalk for 524several kinds of UNIX machnes, and several more commercial ones. 525These products allow you to run file services and print services 526natively to Macintosh users, with no additional support required on 527the Macintosh. The two free omplementations are Netatalk, 528<url url="http://www.umich.edu/~rsug/netatalk/">, and CAP, 529<url url="http://www.cs.mu.oz.au/appletalk/atalk.html">. What Samba offers 530MS Windows users, these packages offer to Macs. For more info on 531these packages, Samba, and Linux (and other UNIX-based systems) 532see <url url="http://www.eats.com/linux_mac_win.html"> 533 534<sect1>"Session request failed (131,130)" error<p> <label id="sess_req_fail"> 535The following answer is provided by John E. Miller: 536 537I'll assume that you're able to ping back and forth between the 538machines by IP address and name, and that you're using some security 539model where you're confident that you've got user IDs and passwords 540right. The logging options (-d3 or greater) can help a lot with that. 541DNS and WINS configuration can also impact connectivity as well. 542 543Now, on to 'scope id's. Somewhere in your Win95 TCP/IP network 544configuration (I'm too much of an NT bigot to know where it's located 545in the Win95 setup, but I'll have to learn someday since I teach for a 546Microsoft Solution Provider Authorized Tech Education Center - what an 547acronym...) [Note: It's under Control Panel | Network | TCP/IP | WINS 548Configuration] there's a little text entry field called something like 549'Scope ID'. 550 551This field essentially creates 'invisible' sub-workgroups on the same 552wire. Boxes can only see other boxes whose Scope IDs are set to the 553exact same value - it's sometimes used by OEMs to configure their 554boxes to browse only other boxes from the same vendor and, in most 555environments, this field should be left blank. If you, in fact, have 556something in this box that EXACT value (case-sensitive!) needs to be 557provided to smbclient and nmbd as the -i (lowercase) parameter. So, if 558your Scope ID is configured as the string 'SomeStr' in Win95 then 559you'd have to use smbclient -iSomeStr [otherparms] in connecting to 560it. 561 562<sect1>How do I synchronise my PC's clock with my Samba server? <p><label id="synchronise_clock"> 563To syncronize your PC's clock with your Samba server: 564<itemize> 565<item> Copy timesync.pif to your windows directory 566 <item> timesync.pif can be found at: 567 <url 568url="http://samba.org/samba/binaries/miscellaneous/timesync.pif"> 569<item> Add timesync.pif to your 'Start Up' group/folder 570<item> Open the properties dialog box for the program/icon 571<item> Make sure the 'Run Minimized' option is set in program 'Properties' 572<iteM> Change the command line section that reads [\\sambahost] to reflect the name of your server. 573<item> Close the properties dialog box by choosing 'OK' 574</itemize> 575Each time you start your computer (or login for Win95) your PC will 576synchronize its clock with your Samba server. 577 578Alternativley, if you clients support Domain Logons, you can setup Domain Logons with Samba 579 - see: <url url="ftp://samba.org/pub/samba/docs/BROWSING.txt" name="BROWSING.txt"> *** for more information. 580<p>Then add 581<tscreen><verb> 582NET TIME \\%L /SET /YES 583</verb></tscreen> 584as one of the lines in the logon script. 585<sect1>Problems with WinDD, NTrigue, WinCenterPro etc<p> 586<label id="multiple_session_clients"> 587 588All of the above programs are applications that sit on an NT box and 589allow multiple users to access the NT GUI applications from remote 590workstations (often over X). 591 592What has this got to do with Samba? The problem comes when these users 593use filemanager to mount shares from a Samba server. The most common 594symptom is that the first user to connect get correct file permissions 595and has a nice day, but subsequent connections get logged in as the 596same user as the first person to login. They find that they cannot 597access files in their own home directory, but that they can access 598files in the first users home directory (maybe not such a nice day 599after all?) 600 601Why does this happen? The above products all share a common heritage 602(and code base I believe). They all open just a single TCP based SMB 603connection to the Samba server, and requests from all users are piped 604over this connection. This is unfortunate, but not fatal. 605 606It means that if you run your Samba server in share level security 607(the default) then things will definately break as described 608above. The share level SMB security model has no provision for 609multiple user IDs on the one SMB connection. See <url url="ftp://samba.org/pub/samba/docs/security_level.txt" name="security_level.txt"> in 610the docs for more info on share/user/server level security. 611 612If you run in user or server level security then you have a chance, 613but only if you have a recent version of Samba (at least 1.9.15p6). In 614older versions bugs in Samba meant you still would have had problems. 615 616If you have a trapdoor uid system in your OS then it will never work 617properly. Samba needs to be able to switch uids on the connection and 618it can't if your OS has a trapdoor uid system. You'll know this 619because Samba will note it in your logs. 620 621Also note that you should not use the magic "homes" share name with 622products like these, as otherwise all users will end up with the same 623home directory. Use [\\server\username] instead. 624 625<sect1>Problem with printers under NT<p> <label id="nt_printers"> 626This info from Stefan Hergeth 627hergeth@f7axp1.informatik.fh-muenchen.de may be useful: 628 629 A network-printer (with ethernetcard) is connected to the NT-Clients 630via our UNIX-Fileserver (SAMBA-Server), like the configuration told by 631 Matthew Harrell harrell@leech.nrl.navy.mil (see WinNT.txt) 632<enum> 633<item>If a user has choosen this printer as the default printer in his 634 NT-Session and this printer is not connected to the network 635 (e.g. switched off) than this user has a problem with the SAMBA- 636 connection of his filesystems. It's very slow. 637 638<item>If the printer is connected to the network everything works fine. 639 640<item>When the smbd ist started with debug level 3, you can see that the 641 NT spooling system try to connect to the printer many times. If the 642 printer ist not connected to the network this request fails and the 643 NT spooler is wasting a lot of time to connect to the printer service. 644 This seems to be the reason for the slow network connection. 645 646<item>Maybe it's possible to change this behaviour by setting different 647 printer properties in the Print-Manager-Menu of NT, but i didn't try it yet. 648</enum> 649 650<sect1>Why are my file's timestamps off by an hour, or by a few hours?<p><label id="dst_bugs"> 651This is from Paul Eggert eggert@twinsun.com. 652 653Most likely it's a problem with your time zone settings. 654 655Internally, Samba maintains time in traditional Unix format, 656namely, the number of seconds since 1970-01-01 00:00:00 Universal Time 657(or ``GMT''), not counting leap seconds. 658 659On the server side, Samba uses the Unix TZ variable to convert 660internal timestamps to and from local time. So on the server side, there are 661two things to get right. 662<enum> 663<item>The Unix system clock must have the correct Universal time. 664 Use the shell command "sh -c 'TZ=UTC0 date'" to check this. 665 666<item>The TZ environment variable must be set on the server 667 before Samba is invoked. The details of this depend on the 668 server OS, but typically you must edit a file whose name is 669 /etc/TIMEZONE or /etc/default/init, or run the command `zic -l'. 670 671<item>TZ must have the correct value. 672<enum> 673 <item>If possible, use geographical time zone settings 674 (e.g. TZ='America/Los_Angeles' or perhaps 675 TZ=':US/Pacific'). These are supported by most 676 popular Unix OSes, are easier to get right, and are 677 more accurate for historical timestamps. If your 678 operating system has out-of-date tables, you should be 679 able to update them from the public domain time zone 680 tables at <url url="ftp://elsie.nci.nih.gov/pub/">. 681 682 <item>If your system does not support geographical timezone 683 settings, you must use a Posix-style TZ strings, e.g. 684 TZ='PST8PDT,M4.1.0/2,M10.5.0/2' for US Pacific time. 685 Posix TZ strings can take the following form (with optional 686 items in brackets): 687<verb> 688 StdOffset[Dst[Offset],Date/Time,Date/Time] 689</verb> 690 where: 691<itemize> 692<item> `Std' is the standard time designation (e.g. `PST'). 693 694<item> `Offset' is the number of hours behind UTC (e.g. `8'). 695 Prepend a `-' if you are ahead of UTC, and 696 append `:30' if you are at a half-hour offset. 697 Omit all the remaining items if you do not use 698 daylight-saving time. 699 700<item> `Dst' is the daylight-saving time designation 701 (e.g. `PDT'). 702 703 The optional second `Offset' is the number of 704 hours that daylight-saving time is behind UTC. 705 The default is 1 hour ahead of standard time. 706 707<item> `Date/Time,Date/Time' specify when daylight-saving 708 time starts and ends. The format for a date is 709 `Mm.n.d', which specifies the dth day (0 is Sunday) 710 of the nth week of the mth month, where week 5 means 711 the last such day in the month. The format for a 712 time is [h]h[:mm[:ss]], using a 24-hour clock. 713</itemize> 714 Other Posix string formats are allowed but you don't want 715 to know about them. 716</enum> 717</enum> 718On the client side, you must make sure that your client's clock and 719time zone is also set appropriately. [[I don't know how to do this.]] 720Samba traditionally has had many problems dealing with time zones, due 721to the bizarre ways that Microsoft network protocols handle time 722zones. A common symptom is for file timestamps to be off by an hour. 723To work around the problem, try disconnecting from your Samba server 724and then reconnecting to it; or upgrade your Samba server to 7251.9.16alpha10 or later. 726 727<sect1> How do I set the printer driver name correctly? <p><label id="printer_driver_name"> 728Question: 729 On NT, I opened "Printer Manager" and "Connect to Printer". 730 Enter ["\\ptdi270\ps1"] in the box of printer. I got the 731 following error message: 732<tscreen><verb> 733 You do not have sufficient access to your machine 734 to connect to the selected printer, since a driver 735 needs to be installed locally. 736</verb></tscreen> 737Answer: 738 739In the more recent versions of Samba you can now set the "printer 740driver" in smb.conf. This tells the client what driver to use. For 741example: 742<tscreen><verb> 743 printer driver = HP LaserJet 4L 744</verb></tscreen> 745with this, NT knows to use the right driver. You have to get this string 746exactly right. 747 748To find the exact string to use, you need to get to the dialog box in 749your client where you select which printer driver to install. The 750correct strings for all the different printers are shown in a listbox 751in that dialog box. 752 753You could also try setting the driver to NULL like this: 754<tscreen><verb> 755 printer driver = NULL 756</verb></tscreen> 757this is effectively what older versions of Samba did, so if that 758worked for you then give it a go. If this does work then let us know via <htmlurl url="mailto:samba@samba.org" name="samba@samba.org">, 759and we'll make it the default. Currently the default is a 0 length 760string. 761 762<sect1>I've applied NT 4.0 SP3, and now I can't access Samba shares, Why?<p><label id="NT_SP3_FIX"> 763As of SP3, Microsoft has decided that they will no longer default to 764passing clear text passwords over the network. To enable access to 765Samba shares from NT 4.0 SP3, you must do <bf>ONE</bf> of two things: 766<enum> 767<item> Set the Samba configuration option 'security = user' and implement all of the stuff detailed in <url url="ftp://samba.org/pub/samba/docs/ENCRYPTION.txt" name="ENCRYPTION.txt">. 768<item> Follow Microsoft's directions for setting your NT box to allow plain text passwords. see <url url="http://www.microsoft.com/kb/articles/q166/7/30.htm" name="Knowledge Base Article Q166730"> 769</enum> 770 771<sect>Specific client application problems<p> <label id="client_problems"> 772 773<sect1>MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"<p> <label id="cant_change_properties"> 774When installing MS Office on a Samba drive for which you have admin 775user permissions, ie. admin users = username, you will find the 776setup program unable to complete the installation. 777 778To get around this problem, do the installation without admin user 779permissions The problem is that MS Office Setup checks that a file is 780rdonly by trying to open it for writing. 781 782Admin users can always open a file for writing, as they run as root. 783You just have to install as a non-admin user and then use "chown -R" 784to fix the owner. 785 786<sect>Miscellaneous<p> <label id="miscellaneous"> 787<sect1>Is Samba Year 2000 compliant?<p><label id="Year2000Compliant"> 788The CIFS protocol that Samba implements 789negotiates times in various formats, all of which 790are able to cope with dates beyond 2000. 791 792</article> 793