diff options
Diffstat (limited to 'docs/faq/sambafaq-3.html')
| -rw-r--r-- | docs/faq/sambafaq-3.html | 240 |
1 files changed, 135 insertions, 105 deletions
diff --git a/docs/faq/sambafaq-3.html b/docs/faq/sambafaq-3.html index 01401017b9..4432ee52d8 100644 --- a/docs/faq/sambafaq-3.html +++ b/docs/faq/sambafaq-3.html @@ -18,26 +18,24 @@ <P> <A NAME="mac_clients"></A> </P> -<P>In Rob Newberry's words (rob@eats.com, Sun, 4 Dec 1994):</P> -<P>The answer is "No." Samba speaks SMB, the protocol used for Microsoft -networks. The Macintosh has ALWAYS spoken Appletalk. Even with -Microsoft "services for Macintosh", it has been a matter of making the -server speak Appletalk. It is the same for Novell Netware and the -Macintosh, although I believe Novell has (VERY LATE) released an -extension for the Mac to let it speak IPX.</P> -<P>In future Apple System Software, you may see support for other -protocols, such as SMB -- Applet is working on a new networking -architecture that will --> -- make it easier to support additional -protocols. But it's not here yet.</P> -<P>Now, the nice part is that if you want your Unix machine to speak -Appletalk, there are several options. "Netatalk" and "CAP" are free, -and available on the net. There are also several commercial options, -such as "PacerShare" and "Helios" (I think). In any case, you'll have -to look around for a server, not anything for the Mac.</P> -<P>Depending on you OS, some of these may not help you. I am currently -coordinating the effort to get CAP working with Native Ethertalk under -Linux, but we're not done yet.</P> - +<P>lkcl - update 09mar97 - the answer is "Yes!". Thursby now have a +CIFS Client / Server - see +<A HREF="http://www.thursby.com/">http://www.thursby.com/</A>. They test it against +Windows 95, Windows NT and samba for compatibility issues. At +present, DAVE is at version 1.0.0. DAVE version 1.0.1 is in beta, +and will be released in April 97 (the speed of finder copies has +been greatly enhanced, and there are bug-fixes included).</P> +<P>Alternatives - There are two free implementations of AppleTalk for +several kinds of UNIX machnes, and several more commercial ones. +These products allow you to run file services and print services +natively to Macintosh users, with no additional support required on +the Macintosh. The two free omplementations are Netatalk, +<A HREF="http://www.umich.edu/~rsug/netatalk/">http://www.umich.edu/~rsug/netatalk/</A>, and CAP, +<A HREF="http://www.cs.mu.oz.au/appletalk/atalk.html">http://www.cs.mu.oz.au/appletalk/atalk.html</A>. What Samba offers +MS Windows users, these packages offer to Macs. For more info on +these packages, Samba, and Linux (and other UNIX-based systems) +see +<A HREF="http://www.eats.com/linux_mac_win.html">http://www.eats.com/linux_mac_win.html</A></P> <H2><A NAME="ss3.2">3.2 "Session request failed (131,130)" error</A></H2> @@ -76,20 +74,31 @@ it.</P> <A NAME="synchronise_clock"></A> </P> <P>To syncronize your PC's clock with your Samba server:</P> -<P>* Copy timesync.pif to your windows directory -* timesync.pif can be found at: -http://samba.canberra.edu.au/pub/samba/binaries/miscellaneous/timesync.pif -* Add timesync.pif to your 'Start Up' group/folder -* Open the properties dialog box for the program/icon -* Make sure the 'Run Minimized' option is set in program -'Properties' -* Change the command line section that reads \\sambahost to reflect -the name -of your server. -* Close the properties dialog box by choosing 'OK'</P> +<P> +<UL> +<LI> Copy timesync.pif to your windows directory</LI> +<LI> timesync.pif can be found at: +<A HREF="http://samba.canberra.edu.au/pub/samba/binaries/miscellaneous/timesync.pif">http://samba.canberra.edu.au/pub/samba/binaries/miscellaneous/timesync.pif</A></LI> +<LI> Add timesync.pif to your 'Start Up' group/folder</LI> +<LI> Open the properties dialog box for the program/icon</LI> +<LI> Make sure the 'Run Minimized' option is set in program 'Properties'</LI> +<LI> Change the command line section that reads \\sambahost to reflect the name of your server.</LI> +<LI> Close the properties dialog box by choosing 'OK'</LI> +</UL> +</P> <P>Each time you start your computer (or login for Win95) your PC will synchronize it's clock with your Samba server.</P> +<P>Alternativley, if you clients support Domain Logons, you can setup Domain Logons with Samba +- see: +<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/BROWSING.txt">BROWSING.txt</A> *** for more information.</P> +<P>Then add +<BLOCKQUOTE><CODE> +<PRE> +NET TIME \\%L /SET /YES +</PRE> +</CODE></BLOCKQUOTE> +as one of the lines in the logon script.</P> <H2><A NAME="ss3.4">3.4 Problems with WinDD, NTrigue, WinCenterPro etc</A></H2> @@ -137,24 +146,25 @@ home directory. Use \\server\username instead.</P> hergeth@f7axp1.informatik.fh-muenchen.de may be useful:</P> <P>A network-printer (with ethernetcard) is connected to the NT-Clients via our UNIX-Fileserver (SAMBA-Server), like the configuration told by -Matthew Harrell harrell@leech.nrl.navy.mil (see WinNT.txt)</P> -<P>1.) If a user has choosen this printer as the default printer in his +Matthew Harrell harrell@leech.nrl.navy.mil (see WinNT.txt) +<OL> +<LI>If a user has choosen this printer as the default printer in his NT-Session and this printer is not connected to the network (e.g. switched off) than this user has a problem with the SAMBA- -connection of his filesystems. It's very slow.</P> -<P>2.) If the printer is connected to the network everything works fine.</P> -<P>3.) When the smbd ist started with debug level 3, you can see that -the -NT spooling system try to connect to the printer many times. If -the -printer ist not connected to the network this request fails and -the -NT spooler is wasting a lot of time to connect to the printer -service. -This seems to be the reason for the slow network connection.</P> -<P>4.) Maybe it's possible to change this behaviour by setting different -printer properties in the Print-Manager-Menu of NT, but i didn't try -it yet.</P> +connection of his filesystems. It's very slow. +</LI> +<LI>If the printer is connected to the network everything works fine. +</LI> +<LI>When the smbd ist started with debug level 3, you can see that the +NT spooling system try to connect to the printer many times. If the +printer ist not connected to the network this request fails and the +NT spooler is wasting a lot of time to connect to the printer service. +This seems to be the reason for the slow network connection. +</LI> +<LI>Maybe it's possible to change this behaviour by setting different +printer properties in the Print-Manager-Menu of NT, but i didn't try it yet.</LI> +</OL> +</P> <H2><A NAME="ss3.6">3.6 Why are my file's timestamps off by an hour, or by a few hours?</A></H2> @@ -168,64 +178,70 @@ it yet.</P> namely, the number of seconds since 1970-01-01 00:00:00 Universal Time (or ``GMT''), not counting leap seconds.</P> <P>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.</P> -<P>1. The Unix system clock must have the correct Universal -time. -Use the shell command "sh -c 'TZ=UTC0 date'" to check this.</P> -<P>2. The TZ environment variable must be set on the server +internal timestamps to and from local time. So on the server side, there are +two things to get right. +<OL> +<LI>The Unix system clock must have the correct Universal time. +Use the shell command "sh -c 'TZ=UTC0 date'" to check this. +</LI> +<LI>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'.</P> -<P>3. TZ must have the correct value.</P> -<P>3a. If possible, use geographical time zone settings +/etc/TIMEZONE or /etc/default/init, or run the command `zic -l'. +</LI> +<LI>TZ must have the correct value. +<OL> +<LI>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 URL:ftp://elsie.nci.nih.gov/pub/.</P> -<P>3b. If your system does not support geographical time -zone +tables at +<A HREF="ftp://elsie.nci.nih.gov/pub/">ftp://elsie.nci.nih.gov/pub/</A>. +</LI> +<LI>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):</P> -<P>StdOffset<F>Dst[Offset</F>,Date/Time,Date/Time]</P> -<P>where:</P> -<P>`Std' is the standard time designation -(e.g. `PST').</P> -<P>`Offset' is the number of hours behind UTC -(e.g. `8'). +Posix TZ strings can take the following form (with optional +items in brackets): +<PRE> + StdOffset[Dst[Offset],Date/Time,Date/Time] +</PRE> + +where: +<UL> +<LI> `Std' is the standard time designation (e.g. `PST'). +</LI> +<LI> `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.</P> -<P>`Dst' is the daylight-saving time designation -(e.g. `PDT').</P> -<P>The optional second `Offset' is the number of +daylight-saving time. +</LI> +<LI> `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.</P> -<P>`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 <F>h</F>h<F>:mm[:ss</F>], using a 24-hour clock.</P> -<P>Other Posix string formats are allowed but you don't -want -to know about them.</P> -<P>On the client side, you must make sure that your client's clock and +The default is 1 hour ahead of standard time. +</LI> +<LI> `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 <F>h</F>h<F>:mm[:ss</F>], using a 24-hour clock.</LI> +</UL> + +Other Posix string formats are allowed but you don't want +to know about them.</LI> +</OL> +</LI> +</OL> + +On the client side, you must make sure that your client's clock and time zone is also set appropriately. <F>[I don't know how to do this.</F>] Samba traditionally has had many problems dealing with time zones, due to the bizarre ways that Microsoft network protocols handle time @@ -241,27 +257,41 @@ and then reconnecting to it; or upgrade your Samba server to <A NAME="printer_driver_name"></A> </P> <P>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.</P> -<P>Answer:</P> +On NT, I opened "Printer Manager" and "Connect to Printer". +Enter "\\ptdi270\ps1" in the box of printer. I got the +following error message: +<BLOCKQUOTE><CODE> +<PRE> + You do not have sufficient access to your machine + to connect to the selected printer, since a driver + needs to be installed locally. +</PRE> +</CODE></BLOCKQUOTE> + +Answer:</P> <P>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, I have:</P> -<P>printer driver = HP LaserJet 4L</P> -<P>and NT knows to use the right driver. You have to get this string +example, I have: +<BLOCKQUOTE><CODE> +<PRE> + printer driver = HP LaserJet 4L +</PRE> +</CODE></BLOCKQUOTE> + +and NT knows to use the right driver. You have to get this string exactly right.</P> <P>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.</P> -<P>You could also try setting the driver to NULL like this:</P> -<P>printer driver = NULL</P> -<P>this is effectively what older versions of Samba did, so if that +<P>You could also try setting the driver to NULL like this: +<BLOCKQUOTE><CODE> +<PRE> + printer driver = NULL +</PRE> +</CODE></BLOCKQUOTE> + +this is effectively what older versions of Samba did, so if that worked for you then give it a go. If this does work then let me know and I'll make it the default. Currently the default is a 0 length string.</P> |