From 2a85f0cf33f303e091ce6f6bea7b7a072cd81c14 Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Wed, 15 Jan 2003 22:29:27 +0000 Subject: syncing docs with HEAD (This used to be commit d8fe70c3b4be548244e9d7b7ea533e64232df001) --- docs/faq/clientapp.html | 24 ++++++------- docs/faq/errors.html | 33 +++++++++++------ docs/faq/install.html | 10 +++--- docs/faq/samba-faq.html | 96 ++++++++++++++++++++++++++++++------------------- 4 files changed, 99 insertions(+), 64 deletions(-) (limited to 'docs/faq') diff --git a/docs/faq/clientapp.html b/docs/faq/clientapp.html index 3196fd285e..b48e236377 100644 --- a/docs/faq/clientapp.html +++ b/docs/faq/clientapp.html @@ -10,8 +10,8 @@ REL="HOME" TITLE="Samba FAQ" HREF="samba-faq.html">PrevChapter 3. Specific client application problemsChapter 4. Specific client application problems

3.1. MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"

4.1. 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 @@ -98,9 +98,9 @@ CLASS="SECT1" >

3.2. How to use a Samba share as an administrative share for MS Office, etc.

4.2. 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 @@ -160,9 +160,9 @@ CLASS="SECT1" >

3.3. Microsoft Access database opening errors

4.3. Microsoft Access database opening errors

Here are some notes on running MS-Access on a Samba drive from PrevCompiling and installing Samba on a Unix hostConfiguration problemsChapter 4. Common errorsChapter 5. Common errors

4.1. Not listening for calling name

5.1. Not listening for calling name

4.2. System Error 1240

5.2. System Error 1240

System error 1240 means that the client is refusing to talk to a non-encrypting server. Microsoft changed WinNT in service @@ -139,9 +139,9 @@ CLASS="SECT1" >

4.3. smbclient ignores -N !

5.3. smbclient ignores -N !

4.4. The data on the CD-Drive I've shared seems to be corrupted!

5.4. 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 @@ -190,9 +190,9 @@ CLASS="SECT1" >

4.5. Why can users access home directories of other users?

5.5. Why can users access home directories of other users?

5.6. 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.

3. Configuration problems
3.1. I have set 'force user' and samba still makes 'root' the owner of all the files I touch!
4. Specific client application problems
3.1. 4.1. MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"
3.2. 4.2. How to use a Samba share as an administrative share for MS Office, etc.
3.3. 4.3. Microsoft Access database opening errors
4. 5. Common errors
4.1. 5.1. Not listening for calling name
4.2. 5.2. System Error 1240
4.3. 5.3. smbclient ignores -N !
4.4. 5.4. The data on the CD-Drive I've shared seems to be corrupted!
4.5. 5.5. Why can users access home directories of other users?
5.6. Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable"
5. 6. Features
5.1. 6.1. How can I prevent my samba server from being used to distribute the Nimda worm?
5.2. 6.2. How can I use samba as a fax server?
5.2.1. 6.2.1. Tools for printing faxes
5.2.2. 6.2.2. Making the fax-server
5.2.3. 6.2.3. Installing the client drivers
5.2.4. 6.2.4. Example smb.conf
5.3. 6.3. Samba doesn't work well together with DHCP!
5.4. 6.4. How can I assign NetBIOS names to clients with DHCP?
5.5. 6.5. How do I convert between unix and dos text formats?
6.6. Does samba have wins replication support?