1<HTML> 2<HEAD> 3<TITLE> Samba Server FAQ: How do I get the CIFS, SMB and NetBIOS protocols?</TITLE> 4</HEAD> 5<BODY> 6<A HREF="Samba-Server-FAQ-1.html">Previous</A> 7Next 8<A HREF="Samba-Server-FAQ.html#toc2">Table of Contents</A> 9<HR> 10<H2><A NAME="s2">2. How do I get the CIFS, SMB and NetBIOS protocols?</A></H2> 11 12<P> 13<A NAME="ServerProtocols"></A> 14</P> 15<P>See the 16<A HREF="Samba-meta-FAQ.html#CifsSmb">meta FAQ on CIFS and SMB</A> if you don't have any idea what these protocols are.</P> 17<P>CIFS and SMB are implemented by the main Samba fileserving daemon, smbd. 18<F>.....</F></P> 19<P>nmbd speaks a limited amount of CIFS (...) but is mostly concerned with 20NetBIOS. NetBIOS is <F>....</F></P> 21<P>RFC1001, RFC1002 <F>...</F></P> 22<P>So, provided you have got Samba correctly installed and running you have 23all three of these protocols. Some operating systems already come with 24stacks for all or some of these, such as SCO Unix, OS/2 and <F>...</F> In this 25case you must <F>...</F></P> 26 27<H2><A NAME="ss2.1">2.1 What server operating systems are supported?</A></H2> 28 29<P> 30<A NAME="PortInfo"></A> 31</P> 32<P>At the last count, Samba runs on about 40 operating systems! This 33section looks at general questions about running Samba on the different 34platforms. Issues specific to particular operating systems are dealt 35with in elsewhere in this document.</P> 36<P>Many of the ports have been done by people outside the Samba team keen 37to get the advantages of Samba. The Samba team is currently trying to 38bring as many of these ports as possible into the main source tree and 39integrate the documentation. Samba is an integration tool, and so it has 40been made as easy as possible to port. The platforms most widely used 41and thus best tested are Linux and SunOS.</P> 42<P>This migration has not been completed yet. This means that some 43documentation is on web sites <F>...</F></P> 44<P>There are two main families of Samba ports, Unix and other. The Unix 45ports cover anything that remotely resembles Unix and includes some 46extremely old products as well as best-sellers, tiny PCs to massive 47multiprocessor machines supporting hundreds of thousands of users. Samba 48has been run on more than 30 Unix and Unix-like operating systems.</P> 49 50<H3>Running Samba on a Unix or Unix-like system</H3> 51 52<P> 53<A NAME="OnUnix"></A> 54</P> 55<P> 56<A HREF="../UNIX-SMB.txt">../UNIX-SMB.txt</A> describes some of the issues that confront a 57SMB implementation on unix, and how Samba copes with them. They may help 58people who are looking at unix<->PC interoperability.</P> 59<P>There is great variation between Unix implementations, especially those 60not adhering to the Common Unix Specification agreed to in 1996. Things 61that can be quite tricky are <F>.....</F></P> 62<P>There are also some considerable advantages conferred on Samba running 63under Unix compared to, say, Windows NT or LAN Server. Unix has <F>...</F></P> 64<P>At time of writing, the Makefile claimed support for: 65<UL> 66<LI> A/UX 3.0</LI> 67<LI> AIX</LI> 68<LI> Altos Series 386/1000</LI> 69<LI> Amiga</LI> 70<LI> Apollo Domain/OS sr10.3</LI> 71<LI> BSDI </LI> 72<LI> B.O.S. (Bull Operating System)</LI> 73<LI> Cray, Unicos 8.0</LI> 74<LI> Convex</LI> 75<LI> DGUX. </LI> 76<LI> DNIX.</LI> 77<LI> FreeBSD</LI> 78<LI> HP-UX</LI> 79<LI> Intergraph. </LI> 80<LI> Linux with/without shadow passwords and quota</LI> 81<LI> LYNX 2.3.0</LI> 82<LI> MachTen (a unix like system for Macintoshes)</LI> 83<LI> Motorola 88xxx/9xx range of machines</LI> 84<LI> NetBSD</LI> 85<LI> NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach).</LI> 86<LI> OS/2 using EMX 0.9b</LI> 87<LI> OSF1</LI> 88<LI> QNX 4.22</LI> 89<LI> RiscIX. </LI> 90<LI> RISCOs 5.0B</LI> 91<LI> SEQUENT. </LI> 92<LI> SCO (including: 3.2v2, European dist., OpenServer 5)</LI> 93<LI> SGI.</LI> 94<LI> SMP_DC.OSx v1.1-94c079 on Pyramid S series</LI> 95<LI> SONY NEWS, NEWS-OS (4.2.x and 6.1.x)</LI> 96<LI> SUNOS 4</LI> 97<LI> SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')</LI> 98<LI> Sunsoft ISC SVR3V4</LI> 99<LI> SVR4</LI> 100<LI> System V with some berkely extensions (Motorola 88k R32V3.2).</LI> 101<LI> ULTRIX.</LI> 102<LI> UNIXWARE</LI> 103<LI> UXP/DS</LI> 104</UL> 105</P> 106 107 108<H3>Running Samba on systems unlike Unix</H3> 109 110<P> 111<A NAME="OnUnlikeUnix"></A> 112</P> 113<P>More recently Samba has been ported to a number of operating systems 114which can provide a BSD Unix-like implementation of TCP/IP sockets. 115These include OS/2, Netware, VMS, StratOS, Amiga and MVS. BeOS, 116Windows NT and several others are being worked on but not yet available 117for use.</P> 118<P>Home pages for these ports are:</P> 119<P><F>... </F></P> 120 121 122<H2><A NAME="ss2.2">2.2 Exporting server resources with Samba</A></H2> 123 124<P> 125<A NAME="Exporting"></A> 126</P> 127<P>Files, printers, CD ROMs and other local devices. Network devices, 128including networked filesystems and remote printer queues. Other devices 129such as <F>....</F></P> 130<P>1.4) Configuring SHARES 1311.4.1) Homes service 1321.4.2) Public services 1331.4.3) Application serving 1341.4.4) Team sharing a Samba resource</P> 135<P>1.5) Printer configuration 1361.5.1) Berkeley LPR/LPD systems 1371.5.2) ATT SysV lp systems 1381.5.3) Using a private printcap file 1391.5.4) Use of the smbprint utility 1401.5.5) Printing from Windows to Unix 1411.5.6) Printing from Unix to Windows</P> 142 143 144<H2><A NAME="ss2.3">2.3 Name Resolution and Browsing</A></H2> 145 146<P> 147<A NAME="NameBrowsing"></A> 148</P> 149<P>See also 150<A HREF="../BROWSING.txt">../BROWSING.txt</A></P> 151<P>1.6) Name resolution issues 1521.6.1) LMHOSTS file and when to use it 1531.6.2) configuring WINS (support, server, proxy) 1541.6.3) configuring DNS proxy</P> 155<P>1.7) Problem Diagnosis 1561.8) What NOT to do!!!!</P> 157<P>3.2) Browse list managment 1583.3) Name resolution mangement</P> 159 160 161 162<H2><A NAME="ss2.4">2.4 Handling SMB Encryption</A></H2> 163 164<P> 165<A NAME="SMBEncryptionSteps"></A> 166</P> 167<P>SMB encryption is ...</P> 168<P>...in 169<A HREF="../ENCRYPTION.txt">../ENCRYPTION.txt</A> there is...</P> 170<P>Samba compiled with libdes - enabling encrypted passwords</P> 171 172 173<H3>Laws in different countries affecting Samba</H3> 174 175<P> 176<A NAME="CryptoLaws"></A> 177</P> 178 179<H3>Relationship between encryption and Domain Authentication</H3> 180 181 182 183 184<H2><A NAME="ss2.5">2.5 Files and record locking</A> 3.1.1) Old DOS clients 3.1.2) Opportunistic locking and the consequences 3.1.3) Files caching under Windows for Workgroups, Win95 and NT Some of the foregoing links into Client-FAQ</H2> 185 186 187<H2><A NAME="ss2.6">2.6 Managing Samba Log files</A></H2> 188 189<P> 190<A NAME="LogFiles"></A> 191</P> 192 193 194<H2><A NAME="ss2.7">2.7 I can't see the Samba server in any browse lists!</A></H2> 195 196<P> 197<A NAME="no_browse"></A> 198 199See 200<A HREF="ftp://samba.org/pub/samba/BROWSING.txt">BROWSING.txt</A> 201for more information on browsing. Browsing.txt can also be found 202in the docs directory of the Samba source.</P> 203<P>If your GUI client does not permit you to select non-browsable 204servers, you may need to do so on the command line. For example, under 205Lan Manager you might connect to the above service as disk drive M: 206thusly: 207<BLOCKQUOTE><CODE> 208<PRE> 209 net use M: \\mary\fred 210</PRE> 211</CODE></BLOCKQUOTE> 212 213The details of how to do this and the specific syntax varies from 214client to client - check your client's documentation.</P> 215 216 217<H2><A NAME="ss2.8">2.8 Some files that I KNOW are on the server doesn't show up when I view the files from my client! </A></H2> 218 219<P> 220<A NAME="missing_files"></A> 221 222See the next question.</P> 223 224 225<H2><A NAME="ss2.9">2.9 Some files on the server show up with really wierd filenames when I view the files from my client! </A></H2> 226 227<P> 228<A NAME="strange_filenames"></A> 229 230If you check what files are not showing up, you will note that they 231are files which contain upper case letters or which are otherwise not 232DOS-compatible (ie, they are not legal DOS filenames for some reason).</P> 233<P>The Samba server can be configured either to ignore such files 234completely, or to present them to the client in "mangled" form. If you 235are not seeing the files at all, the Samba server has most likely been 236configured to ignore them. Consult the man page smb.conf(5) for 237details of how to change this - the parameter you need to set is 238"mangled names = yes".</P> 239 240 241<H2><A NAME="ss2.10">2.10 My client reports "cannot locate specified computer" or similar</A></H2> 242 243<P> 244<A NAME="cant_see_server"></A> 245 246This indicates one of three things: You supplied an incorrect server 247name, the underlying TCP/IP layer is not working correctly, or the 248name you specified cannot be resolved.</P> 249<P>After carefully checking that the name you typed is the name you 250should have typed, try doing things like pinging a host or telnetting 251to somewhere on your network to see if TCP/IP is functioning OK. If it 252is, the problem is most likely name resolution.</P> 253<P>If your client has a facility to do so, hardcode a mapping between the 254hosts IP and the name you want to use. For example, with Man Manager 255or Windows for Workgroups you would put a suitable entry in the file 256LMHOSTS. If this works, the problem is in the communication between 257your client and the netbios name server. If it does not work, then 258there is something fundamental wrong with your naming and the solution 259is beyond the scope of this document.</P> 260<P>If you do not have any server on your subnet supplying netbios name 261resolution, hardcoded mappings are your only option. If you DO have a 262netbios name server running (such as the Samba suite's nmbd program), 263the problem probably lies in the way it is set up. Refer to Section 264Two of this FAQ for more ideas.</P> 265<P>By the way, remember to REMOVE the hardcoded mapping before further 266tests :-) </P> 267 268 269<H2><A NAME="ss2.11">2.11 My client reports "cannot locate specified share name" or similar</A></H2> 270 271<P> 272<A NAME="cant_see_share"></A> 273 274This message indicates that your client CAN locate the specified 275server, which is a good start, but that it cannot find a service of 276the name you gave.</P> 277<P>The first step is to check the exact name of the service you are 278trying to connect to (consult your system administrator). Assuming it 279exists and you specified it correctly (read your client's doco on how 280to specify a service name correctly), read on:</P> 281<P> 282<UL> 283<LI> Many clients cannot accept or use service names longer than eight characters.</LI> 284<LI> Many clients cannot accept or use service names containing spaces.</LI> 285<LI> Some servers (not Samba though) are case sensitive with service names.</LI> 286<LI> Some clients force service names into upper case.</LI> 287</UL> 288</P> 289 290 291<H2><A NAME="ss2.12">2.12 My client reports "cannot find domain controller", "cannot log on to the network" or similar </A></H2> 292 293<P> 294<A NAME="cant_see_net"></A> 295 296Nothing is wrong - Samba does not implement the primary domain name 297controller stuff for several reasons, including the fact that the 298whole concept of a primary domain controller and "logging in to a 299network" doesn't fit well with clients possibly running on multiuser 300machines (such as users of smbclient under Unix). Having said that, 301several developers are working hard on building it in to the next 302major version of Samba. If you can contribute, send a message to 303<A HREF="mailto:samba@samba.org">samba@samba.org</A> !</P> 304<P>Seeing this message should not affect your ability to mount redirected 305disks and printers, which is really what all this is about.</P> 306<P>For many clients (including Windows for Workgroups and Lan Manager), 307setting the domain to STANDALONE at least gets rid of the message.</P> 308 309 310<H2><A NAME="ss2.13">2.13 Printing doesn't work :-(</A></H2> 311 312<P> 313<A NAME="no_printing"></A> 314 </P> 315<P>Make sure that the specified print command for the service you are 316connecting to is correct and that it has a fully-qualified path (eg., 317use "/usr/bin/lpr" rather than just "lpr", if you happen to be using 318Unix).</P> 319<P>Make sure that the spool directory specified for the service is 320writable by the user connected to the service. </P> 321<P>Make sure that the user specified in the service is permitted to use 322the printer.</P> 323<P>Check the debug log produced by smbd. Search for the printer name and 324see if the log turns up any clues. Note that error messages to do with 325a service ipc$ are meaningless - they relate to the way the client 326attempts to retrieve status information when using the LANMAN1 327protocol.</P> 328<P>If using WfWg then you need to set the default protocol to TCP/IP, not 329Netbeui. This is a WfWg bug.</P> 330<P>If using the Lanman1 protocol (the default) then try switching to 331coreplus. Also not that print status error messages don't mean 332printing won't work. The print status is received by a different 333mechanism.</P> 334 335 336<H2><A NAME="ss2.14">2.14 My programs install on the server OK, but refuse to work properly</A></H2> 337 338<P> 339<A NAME="programs_wont_run"></A> 340 341There are numerous possible reasons for this, but one MAJOR 342possibility is that your software uses locking. Make sure you are 343using Samba 1.6.11 or later. It may also be possible to work around 344the problem by setting "locking=no" in the Samba configuration file 345for the service the software is installed on. This should be regarded 346as a strictly temporary solution.</P> 347<P>In earlier Samba versions there were some difficulties with the very 348latest Microsoft products, particularly Excel 5 and Word for Windows 3496. These should have all been solved. If not then please let Andrew 350Tridgell know via email at 351<A HREF="mailto:samba@samba.org">samba@samba.org</A>.</P> 352 353 354<H2><A NAME="ss2.15">2.15 My "server string" doesn't seem to be recognised</A></H2> 355 356<P> 357<A NAME="bad_server_string"></A> 358 359OR My client reports the default setting, eg. "Samba 1.9.15p4", instead 360of what I have changed it to in the smb.conf file.</P> 361<P>You need to use the -C option in nmbd. The "server string" affects 362what smbd puts out and -C affects what nmbd puts out.</P> 363<P>Current versions of Samba (1.9.16 +) have combined these options into 364the "server string" field of smb.conf, -C for nmbd is now obsolete.</P> 365 366 367<H2><A NAME="ss2.16">2.16 My client reports "This server is not configured to list shared resources" </A></H2> 368 369<P> 370<A NAME="cant_list_shares"></A> 371 372Your guest account is probably invalid for some reason. Samba uses the 373guest account for browsing in smbd. Check that your guest account is 374valid.</P> 375<P>See also 'guest account' in smb.conf man page.</P> 376 377 378<H2><A NAME="ss2.17">2.17 Issues specific to Unix and Unix-like systems</A></H2> 379 380<P> 381<A NAME="UnixIssues"></A> 382</P> 383 384<H3>Printing doesn't work with my Unix Samba server</H3> 385 386<P> 387<A NAME="no_printing"></A> 388 </P> 389<P>The user "nobody" often has problems with printing, even if it worked 390with an earlier version of Samba. Try creating another guest user other 391than "nobody".</P> 392 393<H3>Log message "you appear to have a trapdoor uid system" </H3> 394 395<P> 396<A NAME="trapdoor_uid"></A> 397 398This can have several causes. It might be because you are using a uid 399or gid of 65535 or -1. This is a VERY bad idea, and is a big security 400hole. Check carefully in your /etc/passwd file and make sure that no 401user has uid 65535 or -1. Especially check the "nobody" user, as many 402broken systems are shipped with nobody setup with a uid of 65535.</P> 403<P>It might also mean that your OS has a trapdoor uid/gid system :-)</P> 404<P>This means that once a process changes effective uid from root to 405another user it can't go back to root. Unfortunately Samba relies on 406being able to change effective uid from root to non-root and back 407again to implement its security policy. If your OS has a trapdoor uid 408system this won't work, and several things in Samba may break. Less 409things will break if you use user or server level security instead of 410the default share level security, but you may still strike 411problems.</P> 412<P>The problems don't give rise to any security holes, so don't panic, 413but it does mean some of Samba's capabilities will be unavailable. 414In particular you will not be able to connect to the Samba server as 415two different uids at once. This may happen if you try to print as a 416"guest" while accessing a share as a normal user. It may also affect 417your ability to list the available shares as this is normally done as 418the guest user.</P> 419<P>Complain to your OS vendor and ask them to fix their system.</P> 420<P>Note: the reason why 65535 is a VERY bad choice of uid and gid is that 421it casts to -1 as a uid, and the setreuid() system call ignores (with 422no error) uid changes to -1. This means any daemon attempting to run 423as uid 65535 will actually run as root. This is not good!</P> 424 425 426<H2><A NAME="ss2.18">2.18 Issues specific to IBM OS/2 systems</A></H2> 427 428<P> 429<A NAME="OS2Issues"></A> 430</P> 431<P> 432<A HREF="http://carol.wins.uva.nl/~leeuw/samba/samba2.html">Samba for OS/2</A></P> 433 434 435<H2><A NAME="ss2.19">2.19 Issues specific to IBM MVS systems</A></H2> 436 437<P> 438<A NAME="MVSIssues"></A> 439</P> 440<P> 441<A HREF="ftp://ftp.mks.com/pub/samba/">Samba for OS/390 MVS</A></P> 442 443 444<H2><A NAME="ss2.20">2.20 Issues specific to Digital VMS systems</A></H2> 445 446<P> 447<A NAME="VMSIssues"></A> 448</P> 449 450 451<H2><A NAME="ss2.21">2.21 Issues specific to Amiga systems</A></H2> 452 453<P> 454<A NAME="AmigaIssues"></A> 455</P> 456<P> 457<A HREF="http://www.gbar.dtu.dk/~c948374/Amiga/Samba/">Samba for Amiga</A></P> 458<P>There is a mailing list for Samba on the Amiga.</P> 459<P>Subscribing.</P> 460<P>Send an email to rask-samba-request@kampsax.dtu.dk with the word subscribe 461in the message. The list server will use the address in the Reply-To: or 462From: header field, in that order.</P> 463<P>Unsubscribing.</P> 464<P>Send an email to rask-samba-request@kampsax.dtu.dk with the word 465unsubscribe in the message. The list server will use the address in the 466Reply-To: or From: header field, in that order. If you are unsure which 467address you are subscribed with, look at the headers. You should see a 468"From " (no colon) or Return-Path: header looking something like</P> 469<P>rask-samba-owner-myname=my.domain@kampsax.dtu.dk</P> 470<P>where myname=my.domain gives you the address myname@my.domain. This also 471means that I will always be able to find out which address is causing 472bounces, for example. 473List archive.</P> 474<P>Messages sent to the list are archived in HTML. See the mailing list home 475page at 476<A HREF="http://www.gbar.dtu.dk/~c948374/Amiga/Samba/mailinglist/">http://www.gbar.dtu.dk/~c948374/Amiga/Samba/mailinglist/</A></P> 477 478 479<H2><A NAME="ss2.22">2.22 Issues specific to Novell IntraNetware systems</A></H2> 480 481<P> 482<A NAME="NetwareIssues"></A> 483</P> 484 485 486<H2><A NAME="ss2.23">2.23 Issues specific to Stratos VOS systems</A></H2> 487 488<P> 489<A NAME="NetwareIssues"></A> 490</P> 491<P> 492<A HREF="ftp://ftp.stratus.com/pub/vos/tools/">Samba for Stratus VOS</A></P> 493 494 495<HR> 496<A HREF="Samba-Server-FAQ-1.html">Previous</A> 497Next 498<A HREF="Samba-Server-FAQ.html#toc2">Table of Contents</A> 499</BODY> 500</HTML> 501