similar to: printcap printer names

I'm trying to mount a share from an NT machine which has an space inside, i.e doing something like that: mount -t smbfs -o username=nardmann,password=xxx "//machine/for internal use" internal_use I always get the message Could not resolve mount point internal How do I mount such shares with whitespace inside the share name? -- Heiko Nardmann (Dipl.-Ing.), h.nardmann@secunet.de,

I have problems mounting a share from our NT server. Connecting to the share via smbclient '//snsrv051/public' -W ... -U ... and typing my password works nicely but smbmount '//snsrv051/public' /mnt/snsrv051/public -W secunet-si -U nardmann just gives me the following error message: Added interface ip=10.151.4.59 bcast=10.151.7.255 nmask=255.255.252.0 Server time is Fri Jan 29

> I have problems mounting a share from our NT server. > Connecting to the share via > smbclient '//snsrv051/public' -W ... -U ... > and typing my password works nicely but > smbmount '//snsrv051/public' /mnt/snsrv051/public -W secunet-si -U > nardmann > just gives me the following error message: > > Added interface ip=10.151.4.59 bcast=10.151.7.255

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I just set up a PDF printer via Samba 2.2.5 according to the article given in the German magazine iX of March. Now I have the problem that at the first time I done this a file appeared in the resulting pdfshare (the file created by Word which I test with) but afterwards I cannot get it running again (although I restarted smbd and nmbd). No

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am looking for a good and new book for Samba which includes descriptions for the new features (maybe using Samba and Win2K), too. Any proposals? - -- Heiko Nardmann (Dipl.-Ing.), h.nardmann@secunet.de, Software Development secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de), Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49

samba@samba.anu.edu.au wrote: > > SAMBA Digest 1853 > > For information on unsubscribing see http://samba.anu.edu.au/listproc > Topics covered in this issue include: > > 1) Re: long winded printing LARGE files soloution > by Heiko Nardmann <h.nardmann@secunet.de> > 2) Samba replacing NFS > by Jonathan Peterson

Steve Frampton [mailto:frampton@j-com.co.jp] of your address change Content-Length: 7142 samba@samba.org David Barroso <h4371719@alumnes.eup.udl.es> Jeremy Allison <jeremy@valinux.com> "Tulipant Gergely" <tulipant-gergely@dbrt.hu> Edwards Philip M Contr AFRL/SNRR <Philip.Edwards@wpafb.af.mil> Drenning Bruce <bdrenni@catholicrelief.org> Glenn

I always get the messages of this list in a digest format. This is bad to handle, esp. if you want to answer a question found in the digest. Does everyone else also get the list as a digest? Is there a way to switch to single messages? If not how do I easily answer messages which the subject correctly set? Or how do I automatically split the digest into the separate messages? For your

I wonder whether the following setup is possible with Samba since I have problems to get it running: I want password checking for Samba shares on a Linux Samba server to be done via the NT password server. This is mainly thought for the users home directories. Since the users already have given their password to the local workstation I have thought that they do not need to give it again when

Good afternoon, I've downloaded the newly released Samba package 2.0.0, and when trying to run "compile" (located in directory source of the package), after a moment, script fail with the following errors: >ERROR: No locking available. Running Samba would be unsafe >configure: error: summary failure. Aborting config. The following lines are extracted from last lines of

Hello I've searched quite a bit, but have so far been unsuccessful in finding an answer to a question I have concerning the upload of files via rsync over SSH. When downloading, I have been able to make use of SSH's benefits, yet still keep the rsync server safe from a shell accessible with a private SSH key lacking a passphrase by restricting the public key used by the rsync client to

Hi folks, I have a print server, running SPARC Solaris 9. I've just upgraded from Samba 3.0.10 to 3.0.22 and immediately hit system load issues which appear to be related to the use of "lpstat -v" to determine the available print queues. There are about 70 Unix print queues on this system. Running "lpstat -v" can take something like 20s of wall-clock time. lpstat

Previously, I was able to print within wine because the print dialogs would include the printers defined in the /etc/printcap file. Something changed, and now there are *no* printers defined within wine. I have tried reinstalling wine and all windows programs with no luck. Anyone have any hints where to start? Is there something else I need to configure? Richard rdlee@acm.org

Here's the scoop, Well Jeremy and I found the bug last night. Unfortunately it will not be fixed soon. The problem is a bug in our client side code wrt oversized PDUs. When the needed size > MAX_PDU_SIZE in a parsing struct, we need to fragment the PDU and use SMBwrite instead of a single SMBtrans. Fortunately, this has not gotten us into big trouble yet. Jeremy knows how to fix it,

First off, I'm upgrading my school's version of samba, they have 941 printers listed in the printcap file. The old version of samba works. When I run "smbd -D", it waits a few seconds then replies "IOT trap (core dumped)." gdb has errors tracing through it. Here is a snip from log.smb (the only log file I get) at level 10 logging (plus some extra debug statements I

Hi all, Am I the only person to have fallen over the following 'gotcha' ? Upgraded to 1.9.18p8 from 19.9.17p5 on Friday. Came in this morning to discover all Printing had died. Eventually tracked this down to the 'printcap name' setting in Samba jad changed. It default was '/etc/printcap' (it must have been as printing was fine up 17p5 and all previous versions).

According to all of the documentation I can find, an /etc/printcap file (or whatever filename is specified with the Printcap directive) is generated by cupsd ever time a printer is added or removed. On all of my CentOS 6.7 systems, this is NOT happening. I can restart cups and add or remove printers over and over and it still doesn't generate the printcap file. Is this a known issue, or is

Peter> My problem is browsing printers that names are more than Peter> 8 chars long. Any printer that is longer than 8 chars (in the Peter> printcap file) does not show up when browsing. Peter> Anybody else affected by this? Is there a fix? Jim> I had considered "fixing" the code but then I wondered whether I would run Jim> into DOS's 8.3 filenaming convention

Hi list. I'm having problems w/ printing using Samba on Redhat 8. Shared drives work fine yet my CUPS printing doesn't work. I sure appreciate any input. For what it's worth, I couldn't find any printing related errors in /var/log/samba/. I notice that the printcap doesn't have a sub-directory named cups like my old Debian box. Could that be it? Here's my smb.conf

I am using samba-2.2.7-3.7.2 on a redhat 7.2 server with an attached printer which is run by CUPS. It worked OK until I upgraded to samba-2.2.7-3.7.2. Now I can print locally on the server machine, but not from the windows machines on the LAN. The error message on the windows box is " Unable to create a print job." Another error, produced daily when samba is "re-initialized"