From 04cfbc7854bb793481e9050264a1f0cac1c6198a Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Fri, 29 Aug 2003 01:15:53 +0000 Subject: Update pre-release of RC2. Note: Due to config errors not all manpages were rebuilt. (This used to be commit 01fde1a40b11e73cc98f09ab2ebbd14ed0bed4cf) --- docs/faq/FAQ-Install.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/faq/FAQ-Install.html') diff --git a/docs/faq/FAQ-Install.html b/docs/faq/FAQ-Install.html index fc5b1e9812..c331922fdb 100644 --- a/docs/faq/FAQ-Install.html +++ b/docs/faq/FAQ-Install.html @@ -1,4 +1,4 @@ -Chapter 2. Compiling and installing Samba on a Unix host

Chapter 2. Compiling and installing Samba on a Unix host

My client reports "cannot locate specified share name" or similar

+Chapter 2. Compiling and installing Samba on a Unix host

Chapter 2. 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. @@ -7,7 +7,7 @@ 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?

+

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