From b39559c4e52b9f83a9f57510e490d0a75dbbe0df Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Thu, 1 May 2003 13:58:23 +0000 Subject: Merge over Alexanders' conversion to docbook XML (This used to be commit e75624c382d640747b54ba43f134fa043d23b7fe) --- docs/docbook/faq/clientapp.sgml | 101 ----------- docs/docbook/faq/config.sgml | 11 -- docs/docbook/faq/errors.sgml | 178 ------------------- docs/docbook/faq/features.sgml | 376 ---------------------------------------- docs/docbook/faq/general.sgml | 170 ------------------ docs/docbook/faq/install.sgml | 333 ----------------------------------- docs/docbook/faq/sambafaq.sgml | 37 ---- 7 files changed, 1206 deletions(-) delete mode 100644 docs/docbook/faq/clientapp.sgml delete mode 100644 docs/docbook/faq/config.sgml delete mode 100644 docs/docbook/faq/errors.sgml delete mode 100644 docs/docbook/faq/features.sgml delete mode 100644 docs/docbook/faq/general.sgml delete mode 100644 docs/docbook/faq/install.sgml delete mode 100644 docs/docbook/faq/sambafaq.sgml (limited to 'docs/docbook/faq') diff --git a/docs/docbook/faq/clientapp.sgml b/docs/docbook/faq/clientapp.sgml deleted file mode 100644 index 6d687bf772..0000000000 --- a/docs/docbook/faq/clientapp.sgml +++ /dev/null @@ -1,101 +0,0 @@ - -Specific client application problems - - -MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'" - -When installing MS Office on a Samba drive for which you have admin -user permissions, ie. admin users = username, you will find the -setup program unable to complete the installation. - - - -To get around this problem, do the installation without admin user -permissions The problem is that MS Office Setup checks that a file is -rdonly by trying to open it for writing. - - - -Admin users can always open a file for writing, as they run as root. -You just have to install as a non-admin user and then use "chown -R" -to fix the owner. - - - - - -How to use a Samba share as an administrative share for MS Office, etc. - - -Microsoft Office products can be installed as an administrative installation -from which the application can either be run off the administratively installed -product that resides on a shared resource, or from which that product can be -installed onto workstation clients. - - - -The general mechanism for implementing an adminstrative installation involves -running X:\setup /A, where X is the drive letter of either CDROM or floppy. - - - -This installation process will NOT install the product for use per se, but -rather results in unpacking of the compressed distribution files into a target -shared folder. For this process you need write privilidge to the share and it -is desirable to enable file locking and share mode operation during this -process. - - - -Subsequent installation of MS Office from this share will FAIL unless certain -precautions are taken. This failure will be caused by share mode operation -which will prevent the MS Office installation process from re-opening various -dynamic link library files and will cause sporadic file not found problems. - - - - -As soon as the administrative installation (unpacking) has completed -set the following parameters on the share containing it: - - - - [MSOP95] - path = /where_you_put_it - comment = Your comment - volume = "The_CD_ROM_Label" - read only = yes - available = yes - share modes = no - locking = no - browseable = yes - public = yes - - - - - -Now you are ready to run the setup program from the Microsoft Windows -workstation as follows: \\"Server_Name"\MSOP95\msoffice\setup - - - - - - - -Microsoft Access database opening errors - - -Here are some notes on running MS-Access on a Samba drive from Stefan Kjellberg - - - -Opening a database in 'exclusive' mode does NOT work. Samba ignores r/w/share modes on file open. -Make sure that you open the database as 'shared' and to 'lock modified records' -Of course locking must be enabled for the particular share (smb.conf) - - - - - diff --git a/docs/docbook/faq/config.sgml b/docs/docbook/faq/config.sgml deleted file mode 100644 index 78f73252a2..0000000000 --- a/docs/docbook/faq/config.sgml +++ /dev/null @@ -1,11 +0,0 @@ - -Configuration problems - - -I have set 'force user' and samba still makes 'root' the owner of all the files I touch! - -When you have a user in 'admin users', samba will always do file operations for -this user as 'root', even if 'force user' has been set. - - - diff --git a/docs/docbook/faq/errors.sgml b/docs/docbook/faq/errors.sgml deleted file mode 100644 index 6476ec064e..0000000000 --- a/docs/docbook/faq/errors.sgml +++ /dev/null @@ -1,178 +0,0 @@ - - -Common errors - - -Not listening for calling name - - - -Session request failed (131,129) with myname=HOBBES destname=CALVIN -Not listening for calling name - - - - -If you get this when talking to a Samba box then it means that your -global "hosts allow" or "hosts deny" settings are causing the Samba -server to refuse the connection. - - - -Look carefully at your "hosts allow" and "hosts deny" lines in the -global section of smb.conf. - - - -It can also be a problem with reverse DNS lookups not functioning -correctly, leading to the remote host identity not being able to -be confirmed, but that is less likely. - - - - -System Error 1240 - - -System error 1240 means that the client is refusing to talk -to a non-encrypting server. Microsoft changed WinNT in service -pack 3 to refuse to connect to servers that do not support -SMB password encryption. - - -There are two main solutions: - -enable SMB password encryption in Samba. See the encryption part of -the samba HOWTO Collection - -disable this new behaviour in NT. See the section about -Windows NT in the chapter "Portability" of the samba HOWTO collection - - - - - - - -smbclient ignores -N ! - - -When getting the list of shares available on a host using the command -smbclient -N -L -the program always prompts for the password if the server is a Samba server. -It also ignores the "-N" argument when querying some (but not all) of our -NT servers. - - - - -No, it does not ignore -N, it is just that your server rejected the -null password in the connection, so smbclient prompts for a password -to try again. - - - -To get the behaviour that you probably want use smbclient -L host -U% - - - -This will set both the username and password to null, which is -an anonymous login for SMB. Using -N would only set the password -to null, and this is not accepted as an anonymous login for most -SMB servers. - - - - - -The data on the CD-Drive I've shared seems to be corrupted! - - -Some OSes (notably Linux) default to auto detection of file type on -cdroms and do cr/lf translation. This is a very bad idea when use with -Samba. It causes all sorts of stuff ups. - - - -To overcome this problem use conv=binary when mounting the cdrom -before exporting it with Samba. - - - - - -Why can users access home directories of other users? - - - -We are unable to keep individual users from mapping to any other user's -home directory once they have supplied a valid password! They only need -to enter their own password. I have not found *any* method that I can -use to configure samba to enforce that only a user may map their own -home directory. - - - - -User xyzzy can map his home directory. Once mapped user xyzzy can also map -*anyone* elses home directory! - - - -This is not a security flaw, it is by design. Samba allows -users to have *exactly* the same access to the UNIX filesystem -as they would if they were logged onto the UNIX box, except -that it only allows such views onto the file system as are -allowed by the defined shares. - - - -This means that if your UNIX home directories are set up -such that one user can happily cd into another users -directory and do an ls, the UNIX security solution is to -change the UNIX file permissions on the users home directories -such that the cd and ls would be denied. - - - -Samba tries very hard not to second guess the UNIX administrators -security policies, and trusts the UNIX admin to set -the policies and permissions he or she desires. - - - -Samba does allow the setup you require when you have set the -"only user = yes" option on the share, is that you have not set the -valid users list for the share. - - - -Note that only user works in conjunction with the users= list, -so to get the behavior you require, add the line : - -users = %S - -this is equivalent to: - -valid users = %S - -to the definition of the [homes] share, as recommended in -the smb.conf man page. - - - - - -Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable" - -A domain controller has to announce on the network who it is. This usually takes a while. - - - - -I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs -Your loopback device isn't working correctly. Make sure it's running. - - - - diff --git a/docs/docbook/faq/features.sgml b/docs/docbook/faq/features.sgml deleted file mode 100644 index bc1081e5c0..0000000000 --- a/docs/docbook/faq/features.sgml +++ /dev/null @@ -1,376 +0,0 @@ - - -Features - - -How can I prevent my samba server from being used to distribute the Nimda worm? - -Author: HASEGAWA Yosuke (translated by TAKAHASHI Motonobu) - - -Nimba Worm is infected through shared disks on a network, as well as through -Microsoft IIS, Internet Explorer and mailer of Outlook series. - - - -At this time, the worm copies itself by the name *.nws and *.eml on -the shared disk, moreover, by the name of Riched20.dll in the folder -where *.doc file is included. - - - -To prevent infection through the shared disk offered by Samba, set -up as follows: - - - - -[global] - ... - # This can break Administration installations of Office2k. - # in that case, don't veto the riched20.dll - veto files = /*.eml/*.nws/riched20.dll/ - - - - -By setting the "veto files" parameter, matched files on the Samba -server are completely hidden from the clients and making it impossible -to access them at all. - - - -In addition to it, the following setting is also pointed out by the -samba-jp:09448 thread: when the -"readme.txt.{3050F4D8-98B5-11CF-BB82-00AA00BDCE0B}" file exists on -a Samba server, it is visible only as "readme.txt" and dangerous -code may be executed if this file is double-clicked. - - - -Setting the following, - - veto files = /*.{*}/ - -any files having CLSID in its file extension will be inaccessible from any -clients. - - - -This technical article is created based on the discussion of -samba-jp:09448 and samba-jp:10900 threads. - - - - -How can I use samba as a fax server? - -Contributor: Gerhard Zuber - -Requirements: - -UNIX box (Linux preferred) with SAMBA and a faxmodem -ghostscript package -mgetty+sendfax package -pbm package (portable bitmap tools) - - - -First, install and configure the required packages. Be sure to read the mgetty+sendfax -manual carefully. - - -Tools for printing faxes - -Your incomed faxes are in: -/var/spool/fax/incoming - -print it with: - - -for i in * -do -g3cat $i | g3tolj | lpr -P hp -done - - - - -g3cat is in the tools-section, g3tolj is in the contrib-section -for printing to HP lasers. - - - -If you want to produce files for displaying and printing with Windows, use -some tools from the pbm-package like the following command: g3cat $i | g3topbm - | ppmtopcx - >$i.pcx -and view it with your favourite Windows tool (maybe paintbrush) - - - - - -Making the fax-server - -fetch the file mgetty+sendfax/frontends/winword/faxfilter and place it in /usr/local/etc/mgetty+sendfax/(replace /usr/local/ with whatever place you installed mgetty+sendfax) - -prepare your faxspool file as mentioned in this file -edit fax/faxspool.in and reinstall or change the final -/usr/local/bin/faxspool too. - - - -if [ "$user" = "root" -o "$user" = "fax" -o \ - "$user" = "lp" -o "$user" = "daemon" -o "$user" = "bin" ] - - -find the first line and change it to the second. - - -make sure you have pbmtext (from the pbm-package). This is -needed for creating the small header line on each page. - - -Prepare your faxheader /usr/local/etc/mgetty+sendfax/faxheader - - -Edit your /etc/printcap file: - -# FAX -lp3|fax:\ - :lp=/dev/null:\ - :sd=/usr/spool/lp3:\ - :if=/usr/local/etc/mgetty+sendfax/faxfilter:sh:sf:mx#0:\ - :lf=/usr/spool/lp3/fax-log: - - -Now, edit your smb.conf so you have a smb based printer named "fax" - - - - -Installing the client drivers - - -Now you have a printer called "fax" which can be used via -TCP/IP-printing (lpd-system) or via SAMBA (windows printing). - - - -On every system you are able to produce postscript-files you -are ready to fax. - - - -On Windows 3.1 95 and NT: - - - -Install a printer wich produces postscript output, - e.g. apple laserwriter - - -Connect the "fax" to your printer. - - -Now write your first fax. Use your favourite wordprocessor, -write, winword, notepad or whatever you want, and start -with the headerpage. - - - -Usually each fax has a header page. It carries your name, -your address, your phone/fax-number. - - - -It carries also the recipient, his address and his *** fax -number ***. Now here is the trick: - - - -Use the text: - -Fax-Nr: 123456789 - -as the recipients fax-number. Make sure this text does not -occur in regular text ! Make sure this text is not broken -by formatting information, e.g. format it as a single entity. -(Windows Write and Win95 Wordpad are functional, maybe newer - versions of Winword are breaking formatting information). - - - -The trick is that postscript output is human readable and -the faxfilter program scans the text for this pattern and -uses the found number as the fax-destination-number. - - - -Now print your fax through the fax-printer and it will be -queued for later transmission. Use faxrunq for sending the -queue out. - - - - - -Example smb.conf - - -[global] - printcap name = /etc/printcap - print command = /usr/bin/lpr -r -P %p %s - lpq command = /usr/bin/lpq -P %p - lprm command = /usr/bin/lprm -P %p %j - -[fax] - comment = FAX (mgetty+sendfax) - path = /tmp - printable = yes - public = yes - writable = no - create mode = 0700 - browseable = yes - guest ok = no - - - - - - -Samba doesn't work well together with DHCP! - - -We wish to help those folks who wish to use the ISC DHCP Server and provide -sample configuration settings. Most operating systems today come ship with -the ISC DHCP Server. ISC DHCP is available from: -ftp://ftp.isc.org/isc/dhcp - - - -Incorrect configuration of MS Windows clients (Windows9X, Windows ME, Windows -NT/2000) will lead to problems with browsing and with general network -operation. Windows 9X/ME users often report problems where the TCP/IP and related -network settings will inadvertantly become reset at machine start-up resulting -in loss of configuration settings. This results in increased maintenance -overheads as well as serious user frustration. - - - -In recent times users on one mailing list incorrectly attributed the cause of -network operating problems to incorrect configuration of Samba. - - - -One user insisted that the only way to provent Windows95 from periodically -performing a full system reset and hardware detection process on start-up was -to install the NetBEUI protocol in addition to TCP/IP. This assertion is not -correct. - - - -In the first place, there is NO need for NetBEUI. All Microsoft Windows clients -natively run NetBIOS over TCP/IP, and that is the only protocol that is -recognised by Samba. Installation of NetBEUI and/or NetBIOS over IPX will -cause problems with browse list operation on most networks. Even Windows NT -networks experience these problems when incorrectly configured Windows95 -systems share the same name space. It is important that only those protocols -that are strictly needed for site specific reasons should EVER be installed. - - - -Secondly, and totally against common opinion, DHCP is NOT an evil design but is -an extension of the BOOTP protocol that has been in use in Unix environments -for many years without any of the melt-down problems that some sensationalists -would have us believe can be experienced with DHCP. In fact, DHCP in covered by -rfc1541 and is a very safe method of keeping an MS Windows desktop environment -under control and for ensuring stable network operation. - - - -Please note that MS Windows systems as of MS Windows NT 3.1 and MS Windows 95 -store all network configuration settings a registry. There are a few reports -from MS Windows network administrators that warrant mention here. It would appear -that when one sets certain MS TCP/IP protocol settings (either directly or via -DHCP) that these do get written to the registry. Even though a subsequent -change of setting may occur the old value may persist in the registry. This -has been known to create serious networking problems. - - - -An example of this occurs when a manual TCP/IP environment is configured to -include a NetBIOS Scope. In this event, when the administrator then changes the -configuration of the MS TCP/IP protocol stack, without first deleting the -current settings, by simply checking the box to configure the MS TCP/IP stack -via DHCP then the NetBIOS Scope that is still persistent in the registry WILL be -applied to the resulting DHCP offered settings UNLESS the DHCP server also sets -a NetBIOS Scope. It may therefore be prudent to forcibly apply a NULL NetBIOS -Scope from your DHCP server. The can be done in the dhcpd.conf file with the -parameter: -option netbios-scope ""; - - - -While it is true that the Microsoft DHCP server that comes with Windows NT -Server provides only a sub-set of rfc1533 functionality this is hardly an issue -in those sites that already have a large investment and commitment to Unix -systems and technologies. The current state of the art of the DHCP Server -specification in covered in rfc2132. - - - - - -How can I assign NetBIOS names to clients with DHCP? - - -SMB network clients need to be configured so that all standard TCP/IP name to -address resolution works correctly. Once this has been achieved the SMB -environment provides additional tools and services that act as helper agents in -the translation of SMB (NetBIOS) names to their appropriate IP Addresses. One -such helper agent is the NetBIOS Name Server (NBNS) or as Microsoft called it -in their Windows NT Server implementation WINS (Windows Internet Name Server). - - - -A client needs to be configured so that it has a unique Machine (Computer) -Name. - - - -This can be done, but needs a few NT registry hacks and you need to be able to -speak UNICODE, which is of course no problem for a True Wizzard(tm) :) -Instructions on how to do this (including a small util for less capable -Wizzards) can be found at - - -http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html - - - - -How do I convert between unix and dos text formats? - - -Jim barry has written an -excellent drag-and-drop cr/lf converter for -windows. Just drag your file onto the icon and it converts the file. - - - -The utilities unix2dos and dos2unix(in the mtools package) should do -the job under unix. - - - - - -Does samba have wins replication support? - - -At the time of writing there is currently being worked on a wins replication implementation(wrepld). - - - - - diff --git a/docs/docbook/faq/general.sgml b/docs/docbook/faq/general.sgml deleted file mode 100644 index 38bcdf49e3..0000000000 --- a/docs/docbook/faq/general.sgml +++ /dev/null @@ -1,170 +0,0 @@ - -General Information - - -Where can I get it? - -The Samba suite is available at the samba website. - - - - -What do the version numbers mean? - -It is not recommended that you run a version of Samba with the word -"alpha" in its name unless you know what you are doing and are willing -to do some debugging. Many, many people just get the latest -recommended stable release version and are happy. If you are brave, by -all means take the plunge and help with the testing and development - -but don't install it on your departmental server. Samba is typically -very stable and safe, and this is mostly due to the policy of many -public releases. - - - -How the scheme works: - -When major changes are made the version number is increased. For -example, the transition from 1.9.15 to 1.9.16. However, this version -number will not appear immediately and people should continue to use -1.9.15 for production systems (see next point.) - -Just after major changes are made the software is considered -unstable, and a series of alpha releases are distributed, for example -1.9.16alpha1. These are for testing by those who know what they are -doing. The "alpha" in the filename will hopefully scare off those who -are just looking for the latest version to install. - -When Andrew thinks that the alphas have stabilised to the point -where he would recommend new users install it, he renames it to the -same version number without the alpha, for example 1.9.16. - -Inevitably bugs are found in the "stable" releases and minor patch -levels are released which give us the pXX series, for example 1.9.16p2. - - - - -So the progression goes: - - -1.9.15p7 (production) -1.9.15p8 (production) -1.9.16alpha1 (test sites only) -: -1.9.16alpha20 (test sites only) -1.9.16 (production) -1.9.16p1 (production) - - - - -The above system means that whenever someone looks at the samba ftp -site they will be able to grab the highest numbered release without an -alpha in the name and be sure of getting the current recommended -version. - - - - - -What platforms are supported? - -Many different platforms have run Samba successfully. The platforms -most widely used and thus best tested are Linux and SunOS. - - -At time of writing, there is support (or has been support for in earlier -versions): - - - -A/UX 3.0 -AIX -Altos Series 386/1000 -Amiga -Apollo Domain/OS sr10.3 -BSDI -B.O.S. (Bull Operating System) -Cray, Unicos 8.0 -Convex -DGUX. -DNIX. -FreeBSD -HP-UX -Intergraph. -Linux with/without shadow passwords and quota -LYNX 2.3.0 -MachTen (a unix like system for Macintoshes) -Motorola 88xxx/9xx range of machines -NetBSD -NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach). -OS/2 using EMX 0.9b -OSF1 -QNX 4.22 -RiscIX. -RISCOs 5.0B -SEQUENT. -SCO (including: 3.2v2, European dist., OpenServer 5) -SGI. -SMP_DC.OSx v1.1-94c079 on Pyramid S series -SONY NEWS, NEWS-OS (4.2.x and 6.1.x) -SUNOS 4 -SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later') -Sunsoft ISC SVR3V4 -SVR4 -System V with some berkely extensions (Motorola 88k R32V3.2). -ULTRIX. -UNIXWARE -UXP/DS - - - - - -How do I subscribe to the Samba Mailing Lists? - -Look at the samba mailing list page - - - - -Pizza supply details - -Those who have registered in the Samba survey as "Pizza Factory" will -already know this, but the rest may need some help. Andrew doesn't ask -for payment, but he does appreciate it when people give him -pizza. This calls for a little organisation when the pizza donor is -twenty thousand kilometres away, but it has been done. - - - -Method 1: Ring up your local branch of an international pizza chain -and see if they honour their vouchers internationally. Pizza Hut do, -which is how the entire Canberra Linux Users Group got to eat pizza -one night, courtesy of someone in the US. - - - -Method 2: Ring up a local pizza shop in Canberra and quote a credit -card number for a certain amount, and tell them that Andrew will be -collecting it (don't forget to tell him.) One kind soul from Germany -did this. - - - -Method 3: Purchase a pizza voucher from your local pizza shop that has -no international affiliations and send it to Andrew. It is completely -useless but he can hang it on the wall next to the one he already has -from Germany :-) - - - -Method 4: Air freight him a pizza with your favourite regional -flavours. It will probably get stuck in customs or torn apart by -hungry sniffer dogs but it will have been a noble gesture. - - - - - diff --git a/docs/docbook/faq/install.sgml b/docs/docbook/faq/install.sgml deleted file mode 100644 index 88520fc71d..0000000000 --- a/docs/docbook/faq/install.sgml +++ /dev/null @@ -1,333 +0,0 @@ - -Compiling and installing Samba on a Unix host - - -I can't see the Samba server in any browse lists! - -See Browsing.html in the docs directory of the samba source -for more information on browsing. - - - -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 -Lan Manager you might connect to the above service as disk drive M: -thusly: - - net use M: \\mary\fred - -The details of how to do this and the specific syntax varies from -client to client - check your client's documentation. - - - - -Some files that I KNOW are on the server doesn't show up when I view the files from my client! -See the next question. - - - -Some files on the server show up with really wierd filenames when I view the files from my client! - -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 -DOS-compatible (ie, they are not legal DOS filenames for some reason). - - - -The Samba server can be configured either to ignore such files -completely, or to present them to the client in "mangled" form. If you -are not seeing the files at all, the Samba server has most likely been -configured to ignore them. Consult the man page smb.conf(5) for -details of how to change this - the parameter you need to set is -"mangled names = yes". - - - - -My client reports "cannot locate specified computer" or similar - -This indicates one of three things: You supplied an incorrect server -name, the underlying TCP/IP layer is not working correctly, or the -name you specified cannot be resolved. - - - -After carefully checking that the name you typed is the name you -should have typed, try doing things like pinging a host or telnetting -to somewhere on your network to see if TCP/IP is functioning OK. If it -is, the problem is most likely name resolution. - - - -If your client has a facility to do so, hardcode a mapping between the -hosts IP and the name you want to use. For example, with Lan Manager -or Windows for Workgroups you would put a suitable entry in the file -LMHOSTS. If this works, the problem is in the communication between -your client and the netbios name server. If it does not work, then -there is something fundamental wrong with your naming and the solution -is beyond the scope of this document. - - - -If you do not have any server on your subnet supplying netbios name -resolution, hardcoded mappings are your only option. If you DO have a -netbios name server running (such as the Samba suite's nmbd program), -the problem probably lies in the way it is set up. Refer to Section -Two of this FAQ for more ideas. - - - -By the way, remember to REMOVE the hardcoded mapping before further -tests :-) - - - - - -My client reports "cannot locate specified share name" or similar - -This message indicates that your client CAN locate the specified -server, which is a good start, but that it cannot find a service of -the name you gave. - - - -The first step is to check the exact name of the service you are -trying to connect to (consult your system administrator). Assuming it -exists and you specified it correctly (read your client's docs 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. - - - - -Printing doesn't work - -Make sure that the specified print command for the service you are -connecting to is correct and that it has a fully-qualified path (eg., -use "/usr/bin/lpr" rather than just "lpr"). - - - -Make sure that the spool directory specified for the service is -writable by the user connected to the service. In particular the user -"nobody" often has problems with printing, even if it worked with an -earlier version of Samba. Try creating another guest user other than -"nobody". - - - -Make sure that the user specified in the service is permitted to use -the printer. - - - -Check the debug log produced by smbd. Search for the printer name and -see if the log turns up any clues. Note that error messages to do with -a service ipc$ are meaningless - they relate to the way the client -attempts to retrieve status information when using the LANMAN1 -protocol. - - - -If using WfWg then you need to set the default protocol to TCP/IP, not -Netbeui. This is a WfWg bug. - - - -If using the Lanman1 protocol (the default) then try switching to -coreplus. Also not that print status error messages don't mean -printing won't work. The print status is received by a different -mechanism. - - - - -My client reports "This server is not configured to list shared resources" - -Your guest account is probably invalid for some reason. Samba uses the -guest account for browsing in smbd. Check that your guest account is -valid. - - -See also 'guest account' in smb.conf man page. - - - - -Log message "you appear to have a trapdoor uid system" - -This can have several causes. It might be because you are using a uid -or gid of 65535 or -1. This is a VERY bad idea, and is a big security -hole. Check carefully in your /etc/passwd file and make sure that no -user has uid 65535 or -1. Especially check the "nobody" user, as many -broken systems are shipped with nobody setup with a uid of 65535. - - -It might also mean that your OS has a trapdoor uid/gid system :-) - - -This means that once a process changes effective uid from root to -another user it can't go back to root. Unfortunately Samba relies on -being able to change effective uid from root to non-root and back -again to implement its security policy. If your OS has a trapdoor uid -system this won't work, and several things in Samba may break. Less -things will break if you use user or server level security instead of -the default share level security, but you may still strike -problems. - - - -The problems don't give rise to any security holes, so don't panic, -but it does mean some of Samba's capabilities will be unavailable. -In particular you will not be able to connect to the Samba server as -two different uids at once. This may happen if you try to print as a -"guest" while accessing a share as a normal user. It may also affect -your ability to list the available shares as this is normally done as -the guest user. - - - -Complain to your OS vendor and ask them to fix their system. - - - -Note: the reason why 65535 is a VERY bad choice of uid and gid is that -it casts to -1 as a uid, and the setreuid() system call ignores (with -no error) uid changes to -1. This means any daemon attempting to run -as uid 65535 will actually run as root. This is not good! - - - - - -Why are my file's timestamps off by an hour, or by a few hours? - -This is from Paul Eggert eggert@twinsun.com. - - - -Most likely it's a problem with your time zone settings. - - - -Internally, Samba maintains time in traditional Unix format, -namely, the number of seconds since 1970-01-01 00:00:00 Universal Time -(or ``GMT''), not counting leap seconds. - - - -On the server side, Samba uses the Unix TZ variable to convert -internal timestamps to and from local time. So on the server side, there are -two things to get right. - -The Unix system clock must have the correct Universal time. Use the shell command "sh -c 'TZ=UTC0 date'" to check this. -The TZ environment variable must be set on the server before Samba is invoked. The details of this depend on the server OS, but typically you must edit a file whose name is /etc/TIMEZONE or /etc/default/init, or run the command `zic -l'. - - - -TZ must have the correct value. - - -If possible, use geographical time zone settings -(e.g. TZ='America/Los_Angeles' or perhaps - TZ=':US/Pacific'). These are supported by most -popular Unix OSes, are easier to get right, and are -more accurate for historical timestamps. If your -operating system has out-of-date tables, you should be -able to update them from the public domain time zone -tables at ftp://elsie.nci.nih.gov/pub/. - - -If your system does not support geographical timezone -settings, you must use a Posix-style TZ strings, e.g. -TZ='PST8PDT,M4.1.0/2,M10.5.0/2' for US Pacific time. -Posix TZ strings can take the following form (with optional - items in brackets): - - StdOffset[Dst[Offset],Date/Time,Date/Time] - - where: - - - -`Std' is the standard time designation (e.g. `PST'). -`Offset' is the number of hours behind UTC (e.g. `8'). -Prepend a `-' if you are ahead of UTC, and -append `:30' if you are at a half-hour offset. -Omit all the remaining items if you do not use -daylight-saving time. - -`Dst' is the daylight-saving time designation -(e.g. `PDT'). - -The optional second `Offset' is the number of -hours that daylight-saving time is behind UTC. -The default is 1 hour ahead of standard time. - - -`Date/Time,Date/Time' specify when daylight-saving -time starts and ends. The format for a date is -`Mm.n.d', which specifies the dth day (0 is Sunday) -of the nth week of the mth month, where week 5 means -the last such day in the month. The format for a -time is [h]h[:mm[:ss]], using a 24-hour clock. - - - - - - -Other Posix string formats are allowed but you don't want -to know about them. - - -On the client side, you must make sure that your client's clock and -time zone is also set appropriately. [[I don't know how to do this.]] -Samba traditionally has had many problems dealing with time zones, due -to the bizarre ways that Microsoft network protocols handle time -zones. - - - - -How do I set the printer driver name correctly? -Question: - On NT, I opened "Printer Manager" and "Connect to Printer". - Enter ["\\ptdi270\ps1"] in the box of printer. I got the - following error message - - - - You do not have sufficient access to your machine - to connect to the selected printer, since a driver - needs to be installed locally. - - - - Answer: - - In the more recent versions of Samba you can now set the "printer -driver" in smb.conf. This tells the client what driver to use. For -example: - - printer driver = HP LaserJet 4L - -With this, NT knows to use the right driver. You have to get this string -exactly right. - -To find the exact string to use, you need to get to the dialog box in -your client where you select which printer driver to install. The -correct strings for all the different printers are shown in a listbox -in that dialog box. - - - - diff --git a/docs/docbook/faq/sambafaq.sgml b/docs/docbook/faq/sambafaq.sgml deleted file mode 100644 index e9e5ed7a3c..0000000000 --- a/docs/docbook/faq/sambafaq.sgml +++ /dev/null @@ -1,37 +0,0 @@ - - - - - - -]> - - -Samba FAQ - - - Samba Team - October 2002 - - - - -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 3.0. Please send any -corrections to the samba documentation mailinglist at -samba-doc@samba.org. -This FAQ was based on the old Samba FAQ by Dan Shearer and Paul Blackman, -and the old samba text documents which were mostly written by John Terpstra. - - - -&general; -&install; -&config; -&clientapp; -&errors; -&features; - -- cgit