similar to: Linux to windows printing

Applied the update: $ sudo samba --version Version 4.9.5-Debian The results of `posix_open' and `queue' cmds stay the same. Printer is idle on print cmd. A GUI problem with endless authentication request was shot down: 1. Delete the printer 2. Add a new one 3. Network Printer -> Search -> 192.168.0.100 -> Authorization Reqired: username "user", password

I think I need to start over configuring Samba. What I have: ServerAD - Windows 2000 Active Directory Server (10.1.1.251) ServerSuse - Suse Enterprise Server 10.1 (10.1.1.249) LDAP is running Want to run Samba here. ServerSuse2 - Suse Enterprise Server 10 (10.1.1.240) Files I want to share with Windows Machines or Users. What I have so far (smb.conf): realm = CYYCD.COM

I keep getting this error when I attempt to print from Windows 2000 to my printer attached to my Linux Server. "Test page failed to print. Would you like to view the print trouble shooter for assistance? Unable to create a print job." If I attempt to use the command net use lpt1:\\server\printer/ persistent, where server is the computer name of the server and printer is the share

At my workplace, we have a Windows machine which is simultaneously a Print Server and an Accounting Server. The network has got a Samba-LDAP PDC. I want to configure Linux desktops to be able to print to the Windows server (in other words, to a shared SMB printer). But since there is an accounting server, the print job needs to carry SMB authentication credentials. So I need the username/password

I've seen a lot on printing from Win boxes to printers on Linux boxes. I've found very little on printing from Linux to Windows printers. The HOWTO has some information and I've found several other sources, but I still can't get my Linux box to print to a Windows 2000 printer. I'm using Mandrake Linux 8.2, Samba 2.2.3a, CUPS (I'm not sure of the version, I think

Hello out there in samba land, Do to the lack of a stable print spooler in windows 2000 server we have switched to redhat 8.0 to set up our spooler. We are using cups in samba and we're trying to set printers so that everyone can access and use them. we can see all of the printers and even add them. however once they are added when you double click on them to access on the printer it

Machine info- (names are netbios names) LINUXBOX OS: LFS-4.1 Linux SAMBA 2.2.8 No CUPS installed Ran SWAT once just to get a basic config file, no shares from this machine. DESKTOP OS: Windows XP Home SP1 Sharing a HP Deskjet 648C through LPT1 Sharing is enabled on LAN connection Only has one user, Mike, that has no password I can do "smbclient -L DESKTOP" and it will list its shares.

I am getting this when trying to update a machine: warning: rpmts_HdrFromFdno: V3 DSA signature: NOKEY, key ID 6b8d79e6 public key not available for rsync-2.6.4-1.2.el4.rf.i386.rpm This brings yum to a halt. Here is my yum.conf: [main] cachedir=/var/cache/yum debuglevel=2 logfile=/var/log/yum.log pkgpolicy=newest distroverpkg=centos-release tolerant=1 exactarch=1 retries=20 obsoletes=1

I am able to see my printer as a share. Well better put, I see four representations of my printer: ascii, lp2, lp-mono, and raw. I tried the naive thing and just selected lp2 and added the cannon bjc 4000 driver for NT. This didn't work. I get an error report: %%[ Error: undefined; offending Command: K ]%% . . . a bunch of strings that I don't understand. This does not look like the

Try this. Check the enabled Guest account, go to Devices and Printers in Control Panel, right click on the network shared default printer and select Printer properties. Next select the Security tab on the Printer Properties page, and you should see Everyone in the list of users. Check the permissions for Everyone. At minimum, Print should be checked in the Allow check box. The print

Printing from windows clients to Samba through cups works perfectly but old (finished) print jobs are piling up in the print queue for the printer on the client side. I never had this problem with the clients when the server was running RedHat 6.2 with Samba 2.2.8 and LPD. The server has been replaced with a server running a RedHat Enterprise Linux rebuild (TaoLinux). The Samba version is

It's official -------- Original Message -------- Subject: Red Hat Enterprise Linux 4 Update 1 Availability Announcement Red Hat is pleased to announce the availability of Update 1 for the Red Hat Enterprise Linux 4 family of products, including: - Red Hat Enterprise Linux AS (v. 4) for x86, AMD64/EM64T, Itanium, POWER, S/390 and zSeries - Red Hat Enterprise Linux ES (v. 4) for

Hello all, When I do 'sip show channels' I have seen a lot of entries where these calls has already been terminated. Some of these channels are bolong to calls being made 2 days ago but still showing from the CLI. They look like 10.223.51.173 0022676583 130b36625fc 00102/00103 unknow(d) Rx: BYE 10.223.51.173 0022676583 5533069e578 00102/00103 unknow(d) Rx: BYE 10.223.51.173

I have some stuck channels that I think I'm going to have to bounce Asterisk to get rid of, but am curious to know what they are and how they've managed to accumulate. The show up with a channel identifier of '(None)' as in the output below, and do not show up in the soft hangup list, and so can't be cleared by that method. Here is the output from iax2 show channels:

I am having a problem with accessing a Samba share from a Windows 7 system. I think I have the Samba system configured correctly because I can join the Domain. root at ubuntu-server:/home/daved/AddToDCScripts# net rpc join -U Administrator Enter Administrator's password: Joined domain DEMLAND. I can use the smbclient to access the domain controller without a problem: root at

Thank you for answer. Logged in as Guest, then went to Security tab. I see `Everyone', it is given all permissions. Then I went to `Current permissions' tab (I have localized OS at the moment, so probably it is not correct name) and typed in `Everyone' and `Guest' as well: all five permission types are checked. $ smbclient -L 192.168.0.100 -m SMB2     Sharename      

Am 15.08.2016 um 16:33 schrieb L.P.H. van Belle via samba: > Hai Sven, > > Start here : > http://www.infoworld.com/article/3107306/microsoft-windows/microsoft-admits-to-distributing-windows-printing-bugs-in-kb-3177725-and-kb-3176493.html > .. ms bug again.. > Thank you for the tip! Had installed KB3177725 already mid last week at one customer, so far no calls but that can

Hai Sven, Start here : http://www.infoworld.com/article/3107306/microsoft-windows/microsoft-admits-to-distributing-windows-printing-bugs-in-kb-3177725-and-kb-3176493.html .. ms bug again.. > Verzonden: maandag 15 augustus 2016 15:05 > Aan: 'samba at lists.samba.org' > Onderwerp: Re: [Samba] Windows 10 point and print restriction > > Hi Louis, > > Thanks for

I have a Windows 7 workstation with physically connected printer and Linux laptop (Linux Mint 19). They are connected to each other via router with internet cord plugged in. I managed to establish file exchange between them: create a shared resource on one computer, then access it from another. But the same trick with printer just do not work: as soon as I try to access it via network from

Hi, I've been using R for many years and have always tried to keep my R version up to date, and when I switched from 2.7.1 to 2.7.2 I'm suddenly having trouble printing from the graphics device. I have Windows XP, and installed both versions of R from the binaries. If I start 2.7.2 and simply do: > plot(1:10) the default R Graphics Device window opens as usual. However, when I