similar to: MAX PRINT JOBS bugg

On Sun, Dec 16, 2018 at 11:41:04PM +0100, Ronny Nilsson wrote: > I’ve noticed a large amount of UDP probe packets in my system. The default > udp_discovery_interval > is very low so I tried to increase it with configs > UDPDiscoveryInterval > UDPDiscoveryKeepaliveInterval > However, this doesn’t work! Every second a probe is sent no matter what. > > After some digging

Hello, I found that using rsync on OS X can give some problems when it comes to Extended Attributes (-X flag). The server I use has Ubuntu with the filesystem XFS and I am trying to backup a OS X system to it. The problem is as far as I understand it that Linux Kernel has a liming on 64k f?r Extended Attributes and OS X don?t have this limit. Some error output. rsync: rsync_xal_set:

Hi Thanks for the help. I've started to test it. Those every second probes are gone. However, there might still be something fishy with the UDP probes, but I'm uncertain. I can notice these debug messages somewhat too often: Sending type 2 probe reply length 18 to xxx Sending packet from server (MYSELF port 655) to xxx The "server" keeps resending UDP replies to the

Hi I’ve noticed a large amount of UDP probe packets in my system. The default udp_discovery_interval is very low so I tried to increase it with configs UDPDiscoveryInterval UDPDiscoveryKeepaliveInterval However, this doesn’t work! Every second a probe is sent no matter what. After some digging in the sources I found that the interval timer is cleared in udp_probe_h() which causes try_udp()

Hi, I'm trying to fix the printing problem in Samba 3.0.2a on Solaris 9: When I printed a file via Samba, I got the message smb: \> print /etc/hosts NT_STATUS_DISK_FULL opening remote file hosts-20027 I have checked all the file systems and all are OK. Below is the log file: [2004/12/09 11:44:18, 4] printing/nt_printing.c:print_access_check(4946) access check was SUCCESS

Hi all, I'm still a young man having trouble with his fresh new Samba 3 setup. I've got another small issue with Samba. Our Samba 3.0.2-2 (Debian Sarge) is acting as a PDC, but also hosts a few printers shares, with cups. Suddenly today only ONE of our printers stopped to work. From an XP Pro SP1 Client, we cannot print anymore. An attempt to print a test page fails, and here is what

Hello all, I have been trying set up a linux box as a print server for our mixed windows network. It has samba working - everybody can see it & a shared directory. I installed cups & that too seems to be fine - printing test pages from the web interface works perfectly. But i can't get them to talk. I think this is mostly as i can't find a decent howto & so am poking

Hi Samba-Team, I'm using Fedora Linux and running samba 4.1.9. When I submit 2 print jobs from 2 windows command prompts from one Client PC simultaneously below error is logged and the data is lost for one of the job. (CMD prompt: copy smbprint.txt \\IPaddress\Print) ----------------------------------------------------------------------------------------------------------- 2015/12/07

Hi Samba-Team, This issue can be reproducible in samba-4.2.5 also. Please find the attached log file for the same. Hope I may get some help to resolve it. Thanks and Regards, Shivappa On Mon, Apr 4, 2016 at 11:24 PM, shivappa sangapur <ssangapur3 at gmail.com> wrote: > Hi Samba-Team, > > I'm using Fedora Linux and running samba 4.1.9. > > When I submit 2 print jobs

Hello people, Today I noticed that there's a lot of this messages in the /var/log/messages: Jun 9 13:23:00 bcd samba[14033]: [2016/06/09 13:23:00.772684, 0] ../source4/lib/messaging/messaging.c:644(imessaging_init) Jun 9 13:23:00 bcd samba[14033]: Unable to setup messaging listener for '/opt/samba/private/smbd.tmp/msg/msg.14033.41':NT_STATUS_DISK_FULL Jun 9 13:23:00 bcd

Hi, Having a very odd problem with a printer that I've had up and running for over a year now with no previous issues. There have been no software or hardware updates recently that should have affected it. The printer is managed via CUPS and its details are loaded from the CUPS printcap. At some point late on the afternoon of the 11th, samba started rejecting print jobs sent to it.

I'm having a little problem with a HP 8550 Laser Color printer shared under samba. The printer works fine with local prints, I can see the resource printer from Win2k2 explorer. I install the remote printer in a W2k2 workstation, windows ask me for drivers, and then, I installed them. The problem is: when I'm triying to access the printer, windows told me: "Access denied, can

Mates, On my Suse 9.0 pro installation, I updated Samba from 2.2.8a to 3.0.7. The upgrade went flawlessly, Samba is happily sharing all the files it was before. However, I can no longer print via cups. I have a HP LJ4 attached to the Linux box that worked great before the upgrade. I have 2 XP clients. Now from the Windows side, I get the printer status showing 'access denied, unable to

Hi, I'm running samba 2.2.1a (RPM install) on RedHat 7.2 I've connected a Canon LBP-8 IV laserprinter to the network via a HP Jetdirect box. I've configured the printer within linux and printing goes fine. Now I'm trying to access the printer via samba from my win2k clients. Now, the problem is: When I'm trying to print to the printer (e.g. a testpage) I get the message

Greetings, all: I'm having trouble working out a printing problem between my Samba box, and my Windows 2000 client. Here's the background: Network: Home network with a Slackware 8 box running Samba, 1 Windows 2000 client, 1 Windows 98 client, and a LEAF Project firewall providing Internet access. The Samba server should only be available to local clients. Systems: Slackware box:

I've got Samba 2.2.3 running as a PDC for some Win9x and WinNT clients. Everything seems to be fine except that occasionally (but rather often, at least every second day) printing from one of the NT-clients is impossible. In the log file it says (word wrap here in the editor): [2002/02/26 18:04:21, 0] printing/printing.c:print_job_start(952) print_job_start: insufficient permissions to open

Hi, I have a FreeBSD 4.1.1-RELEASE and samba-2.2.4 installed in my server, I have a printer configured and working through samba. My problem is, when I reboot my server, my Windows 2000 with service pack 2, can't print anymore, when I sent a printer job, there is no error, but nothing appear on printer, the other shares area ok, and I can get files from this shares. Then I restart the

Hi there Brian! I've seen your email on one of the samba mailing list. This has been my problem for a long time. I just want to share this problem directly to you and i hope you can lend me your help. I'm trying to setup windows printer sharing using SAMBA installed on my Linux box (Redhat 7.3 as printer server) and windows 2000 pro as my client. My win2k clients are connected to a

Hello, I'm compiling samba 4.2.2 from source on a Linux From Scratch (LFS) system. Packages I have installed on the system are mixed from various versions of LFS (7.6 through 7.9). This is a 64-bit CPU running 32-bit OS: # uname -a Linux pjnas 4.4.4-asrockN3150-001-1_pj #1 SMP Fri Mar 4 22:40:03 CET 2016 i686 GNU/Linux Samba compiles fine, but a few selftests fail. The ones I'm worried

I'm having a difficult time setting up printing from a remote client to a Linux server. Please email replies to mlepage@cgowave-16-35.cgocable.net as I am having difficulty subscribing to the mailing list. The print server is a Debian 2.1 Linux system with an HP LaserJet 5000 connected via parallel port. It prints correctly using lpr, even as user nobody. Also, remote Linux machines can