From troy at trogfish.com Sat Aug 3 02:32:40 2002 From: troy at trogfish.com (Troy Phagan) Date: Fri Feb 13 23:41:29 2004 Subject: samba.org website Message-ID: Hi, I apologize for this in advance since this is not about Samba documentation per se, but about the samba.org website itself. I could not find any direct email addresses for a website maintainer, (except for the talented & overwhelmed "tridge") so I am using (hopefully not abusing...) this list in the hopes this information is helpful. So, here goes.... I'm a newbie, and have been trying to use the SWAT tool on my redhat 7.3 machine, without success. In my endeavers, I have looked at the links to the gui alternatives at http://samba.org/samba/GUI/ However, I have found that some of the links and linked pages are broken, or very dated. The (http://samba.org/samba/GUI/) page could use some updating. I only provide this feedback as constructive criticism from a newbie's view. Please let me emphasize "constructive. " Here is what I have found: "KSamba", according to the info at the listed link (http://www.kneschke. de/projekte/ksamba), it says the project is dead. I did not find any related links to any KSamba information. "B+B Samba Admin Tool" link and info seems to be relevant, but I did not pursue the links further. As a newbie, I cannot tell if the tool is relevant to all distrib's and flavors of *nix or not. There is no link to the "SWAT" tool under the SWAT heading. The "Webmin" project seems very alive, & current. (I think I am going to try this next on my box...) The "SMB2WWW Gateway software" link works, but the info at the site (http://samba.org/samba/smb2www/index.html) seems very dated. (Seems the project died in 1998?) I don't know if the tool is still relevant to the current version of Samba. "SMB2WWW - another one" project web page is dated at March 27th 1997. The info & the project may be relevant, but the info at the site is over my head. The link under the "bbSAT" heading: http://www.hpe3000.de/angebote/software/tools. htm is browseable, but is in German (i think it's German?....) Also, I think this is the same thing as the B+B Samba Admin tool, but documented in German. The JAVA based "smbconftool" project and link is still up, but advertises as being a "1.0 Beta Currently this software is bare minimum functionality. " "smb-mode.el - Emacs mode" link is broken. (http://users.gtn.net/fraserm/smbmode. html)? "GSMB - a GTK interface to smbpasswd" This project's page is a bit confusing in English & French, and it seems to have stalled as of 1999-09-30. "xSMBrowser - a GUI interface to smbclient" This project's link & pages seem relevant. The link goes to the owner's page of various projects, not directly to the project itself. The owner says, "Note that this project is getting a bit dated, but still seems very popular (~1000 dl/week). Word to the wise: Study this program and samba, and then create an open source C++ networking project for Linux. If you've got the knowhow, you'll be a GNU hero. " "Liveserver SMB Browser" The link is broken (returns a 404 error in German?) "SambaSentinel" -This link is broken. Also, the link English link http://samba.org/samba/about.html is lacking key content. Curiously, there is content at http://de.samba. org/samba/about.html Lastly, the "survey" link and content appears to very dated, and many links on the page are broken. http://www.samba.org/samba/survey/ Again, please accept this as humble feedback with the intent that this information can expedite the usage of a very useful tool. Regards, Troy P From satish.paladugula at sun.com Wed Aug 7 17:11:57 2002 From: satish.paladugula at sun.com (Satish Paladugula) Date: Fri Feb 13 23:41:29 2004 Subject: Samba error messages. Message-ID: <3D5154DD.27589E64@sun.com> Hi Team, I have smaba 2.2.4 installed on Solaris 9 on Ultra-1 box. I am getting bunch of the follwing error messages recorded in /var/adm/messages Aug 7 09:49:27 admmpk10 nmbd[17284]: [ID 702911 daemon.error] query_name_response: Multiple (2) responses received for a query on subnet UNICAST_SUBNET for name CB.ICQ.COM<00>. Aug 7 09:51:47 admmpk10 nmbd[17284]: [ID 702911 daemon.error] [2002/08/07 09:51:47, 0] nmbd/nmbd_namequery.c:(104) And also when I restat the smdb and nmdb I see the following error messages Aug 7 09:35:46 admmpk10 nmbd[17284]: [ID 702911 daemon.error] [2002/08/07 09:35:46, 0] nmbd/nmbd_become_dmb.c:(291) Aug 7 09:35:46 admmpk10 nmbd[17284]: [ID 702911 daemon.error] [2002/08/07 09:35:46, 0] nmbd/nmbd_become_dmb.c:(305) Aug 7 09:35:46 admmpk10 nmbd[17284]: [ID 702911 daemon.error] [2002/08/07 09:35:46, 0] nmbd/nmbd_become_dmb.c:(114) Any help to how to fix this problem is greately apprecited. Thank you Satish From dave at ftii.ws Wed Aug 21 20:30:39 2002 From: dave at ftii.ws (Dave Cava) Date: Fri Feb 13 23:41:29 2004 Subject: Some users cannot authenticate on Win2K machines Message-ID: <000001c24952$0b69bc60$960110ac@IQEnergy.com> We are running Samba 2.2.2 on an HP-UX 10.20 server with Windows 9x and 2K/XP clients. All users are able to log on to any 9x machine, but only some users can log onto the Windows 2K/XP machines. The message for those who cannot logon is the standard 'check username and password. make sure capslock is not on', etc. We have checked the logs, etc. and cannot kind a disparity between those who can logon and those who cannot. Please help ASAP. Thanks so much. dave cava Dairy Barn Stores From kevenk at earthlink.net Thu Aug 22 05:49:14 2002 From: kevenk at earthlink.net (Keven Knuth) Date: Fri Feb 13 23:41:29 2004 Subject: perplex why the following info is no longer in docs Message-ID: <5.1.0.14.2.20020821223829.00a34090@mail.earthlink.net> Took me hours to figure out how to get printing to work from Windows 98 to Redhat Linux 7.3. No clue if the problem I had happens with other OSes. Basically I keep getting a permissions problem when a non-root user printed from the Windows box to the printer attached to the linux box. The below howto had my answer set path = /tmp. My question is why is the following howto info not included with Samba any longer, particularly the troubleshooting part? I went thru the /usr/local/samba/docs/* many times and never found this simple solution. Maybe its there and I am just blind. /shrug Keven http://www.tldp.org/HOWTO/SMB-HOWTO-9.html 9. Sharing A Linux Printer With Windows Machines To share a Linux printer with Windows machines, you need to make certain that your printer is set up to work under Linux. If you can print from Linux, setting up an SMB share of the printer is stright forward. Note that Windows users must have an account on the Linux/Samba server in order to print. Windows 95/98 will attempt to authenticate to the print server using the username and password used on login to the Windows box.This means that if you clicked 'Cancel' when logging onto Windows, you can't print (or connect to other SMB services)! Windows NT allows one to explicitely provide a username and password when connecting to a printer. See the Printing HOWTO to set up local printing. Add printing configuration to your smb.conf: [global] printing = bsd printcap name = /etc/printcap load printers = yes log file = /var/log/samba-log.%m lock directory = /var/lock/samba [printers] comment = All Printers security = server path = /var/spool/lpd/lp browseable = no printable = yes public = yes writable = no create mode = 0700 [ljet] security = server path = /var/spool/lpd/lp printer name = lp writable = yes public = yes printable = yes print command = lpr -r -h -P %p %s Make certain that the printer path (in this case under [ljet]) matches the spool directory in /etc/printcap! The lines: printcap name = /etc/printcap load printers = yes controls whether all the printers in /etc/printcap should be loaded by default. If you do this, there is no reason to set up printers individually. The section [printers] specifies options for the printers that you wish to explicitly difine. If the printing subsystem you are using doesn't work this way (BSD), you need to set up a fake printcap file (or to use the 'print command' technique, see below). For more information on the printcap system see the Printing HOWTO. A useful technique to test the network connection is to change the print command to: print command = cp %S /tmp/print.%P.%S The resulting file can then be analyzed. NOTE: There are some problems sharing printers on UNIX boxes with Windows NT machines using Samba. One problem is with NT seeing the shared printer properly. To fix this, see the notes in the Samba distribution in the file docs/WinNT.txt. The other deals with password problems. See the comments in the same file for an annoying gain of understanding and failure to fix the problem. Oleg L. Machulskiy ( machulsk@shade.msu.ru) suggests that a better print command to use in the above example would be: print command = smb2ps %s | lpr -r -h -P %p where 'smb2ps' is a script which transforms the spool file received from Windows into usual a usable Postscript file. It must cut off first 3 lines and last 2 lines, because these lines contain some PJL or PCL codes. That approach is only needed if your Windows machine is printing PCL and not real Postscript. I have found that Windows 95/98/NT don't have a generic Postscript driver per se, but the "Digital turbo Printserver 20" driver acts as a good general Postscript driver for most setups. I have also heard that the "Apple LaserWriter II NTX" driver works for this purpose. If you are creating a printer spool directory instead of using one created by a Linux distribution's installation utility, be careful of permissions! Neil Fraser ( neilf@necon.co.za) suggested setting the permissions of the spool directory (in his case, /var/spool/lpd/lpr) to 4755 (note the suid bit). This worked for him when the owner of the directory was 'root' and the group was 'lp'. Jeff Stern ( jstern@eclectic.ss.uci.edu) reported that he had to set the permissions on his spool directory to 777 in order for non-priviledged users to print, although he notes that he could have also added users to the 'lp' group. This is a decision for local systems administrators; if printing security is an issue, then lock it down. In home environments, you will probably want everyone to be able to print. Dr. Michael Langner ( langner@fiz-chemie.de) points out that write permission problems on the /var/spool/lpd/ tree could be avoided by use something like "path = /tmp" and "print command = lpr -r -P%p %s" instead. Sometimes, a Postscript parsing error will occur with Postscript printing from Windows machines that causes an extra page to be printed at the end of every print job. The last page will always have "%%[ Lastpage ]%%" at the top of it. This seems to happen with Windows 95 and 98 only and is because the Postscript is malformed. One way to handle that is to use a script to remove that bit of bad Postscript from the spooled jobs. Another way is to try to find a better Windows Postscript driver. Probably the best way is to us LPRng instead of Postscript to print to a Samba server. Erik Ratcliffe ( erik@caldera.com) Caldera tells me that using LPRng means that any printer driver can be used from Windows machines. On the Samba server, they used an /etc/printcap entry that looked like this: raw:\ :rw:sh: :lp=/dev/lp1 :sd=/var/spool/lpd/raw :fx=flp LPRng doesn't require :\ at the end of every line. A printer entry will still need to be made in /etc/smb.conf for the physical printer. The print command line needs to use the "raw" entry in /etc/printcap and data must be sent to the printer in binary form. Try a print command line like this: print command = lpr -b -Praw %s You may also need to set the spooling on the Windows95 end to print directly to the printer instead of spooling. If you constantly get a extra page printing at the end of print jobs from Windows clients, try adding an "sf" directive in /etc/printcap. This will suppress form feeds separating jobs, but will not effect form feeds within documents. Next Previous Contents -------------- next part -------------- HTML attachment scrubbed and removed From Volker.Lendecke at SerNet.DE Tue Aug 27 08:20:54 2002 From: Volker.Lendecke at SerNet.DE (Volker.Lendecke@SerNet.DE) Date: Fri Feb 13 23:41:29 2004 Subject: Spaces discarded after Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Lars Müller from SuSE found 'smbdto' in smb.conf.5. In the docbook there's smbd to ... So the eats spaces when converting to manpages. Any idea? Volker -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Key-ID ADE377D8, Fingerprint available: phone +49 551 3700000 iD8DBQE9azZiZeeQha3jd9gRAr0MAJwI4tEnU9aN1BbelWI7HJq/ValGMgCbBTnI XVAzhCw1eLqF+x+BUoqYpi8= =AR1g -----END PGP SIGNATURE----- From jerry at samba.org Tue Aug 27 13:40:17 2002 From: jerry at samba.org (Gerald (Jerry) Carter) Date: Fri Feb 13 23:41:29 2004 Subject: Spaces discarded after In-Reply-To: Message-ID: On Tue, 27 Aug 2002 Volker.Lendecke@SerNet.DE wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi! > > Lars M?ller from SuSE found 'smbdto' in smb.conf.5. In the docbook > there's smbd to ... > > So the eats spaces when converting to manpages. Any idea? This is actually done by a naive perl script. See the Makefile for details. The problem was that the docbook2X tools were inserting tags I didn't like. Feel free to improve it :-) See docs/docbook/scripts/strip-links.pl cheers, jerry