similar to: Multi instant samba does not work on samba 4.10.4

hi Jerry et al, when I use the 'ADD PRINTER WIZARD' it looks like this: ----------------------------------------- |[]\\whatevernthost\mydeskjetanywhere | |[]\\computeronmydesk\printernexttome | |[]\\Ididn'tevennowIm\sharingaprinter | |+[]SAMBAPRINTSERVER | ----------------------------------------- The shared printers on the SAMBA server get visible by

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

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.

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 Karthik, Thanks for the info. Maybe the documentation should be updated to explain the different AFR versions, I know I was confused. Also, when looking at the changelogs from my three bricks before fixing: Brick 1: trusted.afr.virt_images-client-1=0x000002280000000000000000 trusted.afr.virt_images-client-3=0x000000000000000000000000 Brick 2:

Hey Henrik, Good to know that the issue got resolved. I will try to answer some of the questions you have. - The time taken to heal the file depends on its size. That's why you were seeing some delay in getting everything back to normal in the heal info output. - You did not hit the split-brain situation. In split-brain all the bricks will be blaming the other bricks. But in your case the

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:

On Tue, 19 Feb 2019 18:40:03 -0500 samba.x.eliezer613 at spamgourmet.com wrote: > Hi Rowland, actually just trying to learn AD. Have a 'regular' samba > server running here for years. In as much as a smb.conf it seems to > have one : > > [global] >         dns forwarder = 192.168.25.253 >         netbios name = DC1 >         realm = DC1.INTERNAL >        

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

> What exactly is happening in my situation? As of now use FQDN due to lots of security fixed MS applies this is needed. So best is, dont use short (netbios) hostnames but FQDN. Read samba list subject: ( google for it ) > "Re: [Samba] Windows 10 point and print restriction" Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at

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, I have an existing Samba network consisting of a SAMBA PDC with win98 and XP clients (there is also some linux machines on the network connecting via NIS/NFS. Everything is running nicely. Now I want to add a samba print server to the domain. All this server needs to do is share a printer for the domain. For some reason I cannot get this printer server to share anything. Not even it's

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

I'm getting strange error when running rpcclient on localhost. rpcclient PRINTSERVER -A auth -d 3 -c "enumprinters" here's result: Initialising global parameters params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf" Processing section "[global]" added interface ip=10.223.11.1 bcast=10.223.11.255 nmask=255.255.252.0 not adding duplicate

Am 20.02.19 um 15:58 schrieb samba.x.eliezer613--- via samba: > Hi, not having much luck getting samba 4.8.3 to start on a CentOS 7.6 VM.... > > used samba-4.8.3.tar.gz > ./configure > make > make install > samba-tool domain provision --use-rfc2307 --interactive > > In /etc/samba there is one file, smb.conf with content of: > # Global parameters > [global] >

Contrary to best practices, on my boxes I'm always root so it is doing this when run as root. I'm getting the error for the daemon also when run as a system service in systemd. Configure line: ./configure \ --disable-cups \ --without-ldb-lmdb \ --prefix=/opt/samba \ --sysconfdir=/etc/samba \ --localstatedir=/var \ --with-systemd \ --systemd-install-services \

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:

Hi, I'm using samba-2.2.1a on a Debian Linux box as a Debian package. It only serves as a printserver for about 35 printers which are all in /etc/printcap. Samba exports them all through the [printers] section in smb.conf. "guest ok = yes" for the [printers] The problem is as follows: - printadmin (having uid 0) logs onto the printserver using a win2k client - printadmin

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