From fec4b31bc1a76e408732e1a80b366d97fcf38143 Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Fri, 10 Oct 2003 16:46:22 +0000 Subject: removing docs tree from 3.0 (This used to be commit 0a3eb5574c91685ab07436c67b031266fb329693) --- docs/docbook/faq/clientapp.xml | 101 ------------- docs/docbook/faq/errors.xml | 101 ------------- docs/docbook/faq/features.xml | 314 ----------------------------------------- docs/docbook/faq/general.xml | 124 ---------------- docs/docbook/faq/install.xml | 117 --------------- docs/docbook/faq/sambafaq.xml | 39 ----- 6 files changed, 796 deletions(-) delete mode 100644 docs/docbook/faq/clientapp.xml delete mode 100644 docs/docbook/faq/errors.xml delete mode 100644 docs/docbook/faq/features.xml delete mode 100644 docs/docbook/faq/general.xml delete mode 100644 docs/docbook/faq/install.xml delete mode 100644 docs/docbook/faq/sambafaq.xml (limited to 'docs/docbook/faq') diff --git a/docs/docbook/faq/clientapp.xml b/docs/docbook/faq/clientapp.xml deleted file mode 100644 index 3d44dd44c0..0000000000 --- a/docs/docbook/faq/clientapp.xml +++ /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/errors.xml b/docs/docbook/faq/errors.xml deleted file mode 100644 index 398286e3c9..0000000000 --- a/docs/docbook/faq/errors.xml +++ /dev/null @@ -1,101 +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 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. - - - - - diff --git a/docs/docbook/faq/features.xml b/docs/docbook/faq/features.xml deleted file mode 100644 index 271310b338..0000000000 --- a/docs/docbook/faq/features.xml +++ /dev/null @@ -1,314 +0,0 @@ - - -Features - - -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.xml b/docs/docbook/faq/general.xml deleted file mode 100644 index df0d23ce02..0000000000 --- a/docs/docbook/faq/general.xml +++ /dev/null @@ -1,124 +0,0 @@ - -General Information - - -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 the release manager, currently Jerry, 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 - - - - diff --git a/docs/docbook/faq/install.xml b/docs/docbook/faq/install.xml deleted file mode 100644 index 84b13f14d3..0000000000 --- a/docs/docbook/faq/install.xml +++ /dev/null @@ -1,117 +0,0 @@ - -Compiling and installing Samba on a Unix host - - -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. - - - - -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. - - - - diff --git a/docs/docbook/faq/sambafaq.xml b/docs/docbook/faq/sambafaq.xml deleted file mode 100644 index 4476070862..0000000000 --- a/docs/docbook/faq/sambafaq.xml +++ /dev/null @@ -1,39 +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-docs@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; -&clientapp; -&errors; -&features; - -- cgit