similar to: Is building a load balance setup like this workable?

Hi; When I set the security to domain, although I can join the domain I can't print to the RedHat 5.2 (kernel 2.0.36) Samba 2.0.3 Server, which I am planning to use as a printserver. When the security is share level I succeed to print, but any user is able to cancel the job. I tried both printing = bsd and lprng. The printers are connected to Intel printservers. The cilents are Win95 and

> Dear Sirs, > > I would like to know if there is a way to share printers connected to > print > servers (Intel Print Servers are used in my company) so that Linux takes > the spooling job on to himself, using Samba. I succeded to define the > printserver queues under Linux (by the Intel's PrintServer software) but > when more than one users try to print on the same

Nobody who can help use with this issue? A developer already began to fix it 3/4 year ago, but never created a patch that finally fix the whole problem. -------- Original-Nachricht -------- Betreff: Re: [Samba] Samba 3.4 / 3.5: Printer settings not available for normal users Datum: Tue, 18 Jan 2011 09:32:58 +0100 Von: Marc Muehlfeld <Marc.Muehlfeld at medizinische-genetik.de> An: Jack

Okay, I've got some progress now. Have fairly decent printserver working. I've been able to reproduce the same postive and negative results in two physical servers and now (finaly destination) a vmware server. What's working: ADS integration, this is a domain member Printer driver installation (for a few drivers) Printer installation / removal Printing. What's not working:

I have the following situation at the hospital I work at. we are a windows shop (not my fault), and as such use windows 2k3 file and print servers. Recently passing 400 printers has apparently put too much strain on our main printserver - called ntprn (been a windows shop for a while). Okay, so now we are going to split the load amongst two or more printservers... ntprn1 and ntprn2. Our users

I have a workgroup server with samba operating well and have configured openvpn on it. That also seems to be working well. I also have other servers at different locations with samba/openvpn working. To access the openvpn server I use Windows and manually map a drive to a drive letter using U: as \\servername\sharename The shares work but I am mapping _through_ the samba server - that is I have

Thanks Rowland, Contents of /etc/hosts: /127.0.0.1 localhost////127.0.0.1 printserver//////# The following lines are desirable for IPv6 capable hosts////::1 ip6-localhost ip6-loopback////fe00::0 ip6-localnet////ff00::0 ip6-mcastprefix////ff02::1 ip6-allnodes////ff02::2 ip6-allrouters/// and /etc/hostname: /printserver/ I have changed workgroup name now, and removed the .LOCAL in the end. I

Hi all, Samba 4.3.11 is serving printers in my office from a server called "printserver". If a Windows 7 client tries to reach it using a short name \\prinserver , it can see the list of printers, but can't connect to any of them: "Windows couldn't connect to the printer" pop-up appears immediately. Weirdly, it doesn't happen all the times, sometimes it can

Hi Karthik and Ben, I'll try and reply to you inline. On 21 December 2017 at 07:18, Karthik Subrahmanya <ksubrahm at redhat.com> wrote: > Hey, > > Can you give us the volume info output for this volume? # gluster volume info virt_images Volume Name: virt_images Type: Replicate Volume ID: 9f3c8273-4d9d-4af2-a4e7-4cb4a51e3594 Status: Started Snapshot Count: 2 Number of Bricks:

hi, I'm having trouble printing with smbclient via an embedded USB printserver. This printserver is a nifty little $35 box with an Ethernet jack and a USB jack that provides network access to your USB printer as a Windows share (a poor man's Jetdirect, if you will). I can connect to the printer with smbclient, but when I try to print anything, even a small text file, I always get the

Hi Henrik, Thanks for providing the required outputs. See my replies inline. On Thu, Dec 21, 2017 at 10:42 PM, Henrik Juul Pedersen <hjp at liab.dk> wrote: > Hi Karthik and Ben, > > I'll try and reply to you inline. > > On 21 December 2017 at 07:18, Karthik Subrahmanya <ksubrahm at redhat.com> > wrote: > > Hey, > > > > Can you give us the

Hi, I'm trying to upload printer drivers to my jessie samba 4.1.17 print server, but I'm getting: "Failed to add driver. Access denied", and I don't understand why. The domain join is OK (verified with net ads testjoin) and on the DC I have given the SePrintOperatorPrivilege to the Domain Admins group, of which I am a member: root at DC2:~# net rpc rights list

Hi. Tonight, I upgraded our Samba print server running Samba 3.0.30 to Samba 3.2.7. This netbios name of this server is 'EUPRYMNA' and the DNS-name 'euprymna.falw.vu.nl'. Since this is a difficult name to remember, we created a DNS-alias 'printserver.falw.vu.nl'. Connecting to printers by calling the server by it's DNS-alias worked in 3.0.30. After the upgrade

Greetings Samba Fans! I'm experiencing a strange problem which started after installation of Service Pack 2 for Windows XP: When a user tries to print there is a long delay (sometimes around 2 minutes) before the printer properties page is opened. This only affects Windows XP with Service Pack 2 installed. I did a 'tcpdump' on the printserver and observed something quite strange:

Running RH6.0 I am able to print just fine from linux, the problem now is getting smb printing working. I am using an Intel Netport Express PRO/100 printserver. Previous to my upgrade from RH5.2 when I had the printer directly connected to the samba server, I was able to print just fine from the windows client machines (not using the raw method) My /etc/printcap is as follows ##PRINTTOOL3##

I read an email in here where Volker replied to a person saying that share level was really weird these days, etc. Here's the full context: ************ > I have a server that contains share level users , but would like to be > in AD domain for any new users. Not on the same IP. You are sure that you mean share level? This is really, really weird these days. If you want

Hi all, I am running samba 3.0.6. I am having an issue on my print server regarding how the printer ends up registering itself on the Windows clients. We have a machine named "bob", "bob" has an alias both in DNS and in the netbios name in Samba of "printserver", "bob" has an IP address of 192.168.1.1. In a seemingly random fashion sometimes when I add

Not sure what's going on here, but it's got to be a permissions thing it would seem. Background: working ADS. Samba 3.5.6 atop Freebsd 8.1 as domain member When I attempt to load drivers with Windows XP Pro (32bit), everything is fine. I can load either x32 drivers or x64 drivers. The same cannot be said for Windows 7. I cannot correctly load drivers with Windows 7, and here is a

Hello, currently I am trying to setup a Samba environment (Samba AD DC, Samba Fileserver, Samba Printserver) using Samba version 4.5.8-Debian and CUPS version 2.2.1-8 on Debian 9 "Stretch". I am trying to setup "Point'n'Print" atm. While my Active Directory domain and the fileserver work well with my Windows 7 clients, I am having some issues with the printserver.

Hello I just upgraded our PDC from 3.0.22 to 3.0.23 with all the bells and whistles. I am running OpenLdap as a backend and did what's been written in the Changelog regarding indexing. The new version started up fine and worked all right. Netlogons, shares, printing etc. I could also assign ACLs to my files as before. The PDC also works as a printserver running cups with the drivers