similar to: XP Pro And Samba

Does anyone have any hints or suggestions on getting some JetDirect-based printers set up for bidirectional printing in Samba? We're using LPRng 3.8.0, ifhp 3.4.7, and samba 2.2.2 From the LPRng standpoint, the printers seem to be set up for bidirectional communication fine.. but how do we get Samba to allow bidirectional communication? Thanks in advance! Glenn --- Glenn E. Sieb,

Hmm...I've never tried it with a local user and a domain group. I've certainly done stuff like: chown DOMAIN+David:"DOMAIN+Domain Users" * and had it work before... -----Original Message----- From: Glenn Sieb [mailto:ges@lumeta.com] Sent: Monday, November 26, 2001 11:00 AM To: Samba Mailing List Subject: Hmm. Silly(ish) question re: winbind I know that winbindd allows Samba

Hello, I have been trying off and on over the last couple months to get printer drivers installed on the server side of samba. And have emailed the list with copious notes, got nowhere, and gave up. (I realize that is is a beta feature and am not complaining at all: I can live with out it) But; I have a little bit more info after trying to install the printer driver from a client and failing

I almost afraid to ask - but, I have Samba installed and operational. When I try to login to http://localhost:901 I get a logon screen. I type root then the password. But it keeps comming back as bad usersnam or password. I know thjis is simple. But it's my fist time tyring to use samba and I cannot find any answers on the internet. Thanks for your help

Can someone explain why I get emails like this: > -----Original Message----- > From: samba-bounces+ges=lumeta.com@lists.samba.org > [mailto:samba-bounces+ges=lumeta.com@lists.samba.org] On > Behalf Of Andrew Bartlett > Sent: Thursday, February 19, 2004 4:33 PM > To: Gary Hostetler > Cc: samba@lists.samba.org > Subject: Re: [Samba] Bought the book still lost > >

We just popped 2.2.6rc2 on to see if we could resolve a few printing issues, and now I can't seem to do the printer sharing on any printers on the server... In [global]: workgroup = CORP netbios name = NEWLUCY security = DOMAIN encrypt passwords = Yes update encrypted = Yes password server = LUNA pam password change = Yes

I'm sitting here tonight trying to get WinXP to map a printer on a Samba share. First off, one thing I find disturbing is that XP seems to be aware of Samba servers. When I open a window to one, it says on the window bar "Samba 2.0.7 (nameofserver)" *shudder*. Anywho. I'm trying to map to a printer, and it seems to take forever and a week to come up. I've managed to map

We just went through a massive renumber, and cleanup of some services. I went to rejoin our main Samba server to the domain and I get: error setting trust account password: NT_STATUS_NO_USER_SESSION_KEY I've deleted the machine account on the domain, I've double checked the smb.conf to make sure I have the right domain controller set, and I'm issuing: smbpasswd -j CORP -r

I'm having problems with samba using the 2K PDC. I've gotten it to successfully join the 2K PDC via smbpasswd. Winbindd is running and I can ping it. I've tried googling, but was unsuccessful at finding something useful. The Windows 2K event viewer shows: The session setup from the computer DATASRV failed to authenticate. The name of the account referenced in the security database is

Just FYI, the FAQ is pretty good about addressing the browsing issues some people have been mentioning. Here at Lumeta, I could never quite understand why our domain would show some boxes from one person's PC and others from another, after all, we're one domain with a Samba server, so what's the deal, right? Well, after reading the FAQ (

(Some more info) I have a FreeBSD server running Samba 2.2.8 now (updated from 2.2.7).. I've turned log levels to 10... I have a user who needs this machine to do her job, and she uses Mac OS X, the latest 10.2 updates have been applied. She routinely cannot connect to this box, and gets an error -36, which means she needs to reboot every time she gets this. The logs show *NOTHING* when

Hey everyone, Can someone help me out with how to modify my /etc/pam.conf in FreeBSD for use with Winbind/pam_smb? Thanks in advance, Glenn --- Glenn E. Sieb, System Administrator Lumeta Corp. mailto:ges@lumeta.com +1 732 357-3514 (V) +1 732 564-0731 (Fax)

Is anyone willing to share their mods for /etc/pam.conf? Thanks! Glenn :) --- Glenn E. Sieb, System Administrator Lumeta Corp. mailto:ges@lumeta.com +1 732 357-3514 (V) +1 732 564-0731 (Fax)

Greetings... Our current production server is running 2.0.7 (we are getting ready to deploy 2.2.5 shortly)... and I experienced this interesting problem.. In Apache, if I had it listening to ports 444 and 445 for SSL, Samba would suddenly stop working on that machine. I killed Apache, and suddenly everyone could get to Samba again.. I started it, and everyone would get errors saying the

I am finding myself in need of some printer drivers for two HP printers (HP4550N, HP8150DN) that do NOT have the nifty pretty interface? The ones where it was pretty barebones, no "form storage" or anything. I'm running 2.2.6rc2 and users still can't seem to change any settings for printers, and if I can run the older (< 5e versions) drivers, then people can change

Good Day All! I am attempting to configure deliver as our LDA. I am also configuring the server to use Postfix instead of Sendmail. I have followed the all the documentation and examples I could find. Below are my Dovecot and Postfix configs. Can someone please smack me upside the head and tell me why I am getting "user unknown" errors? If i don't use deliver as the LDA, all

Hi, Is there an ETA on the openssl security update (CVE-2016-0799) for CentOS 6.7? I saw the openssl update for CentOS 7 on 5/9, eagerly awaiting the same for 6.7. Thanks! -->Pat

On 05/11/2016 09:45 AM, Steve Snyder wrote: > > On Wednesday, May 11, 2016 11:20am, "Patrick Rael" <prael at lumeta.com> said: > >> Hi, >> Is there an ETA on the openssl security update (CVE-2016-0799) for >> CentOS 6.7? I saw the openssl update for CentOS 7 on 5/9, eagerly >> awaiting >> the same for 6.7. >> >> Thanks!

I have a FreeBSD server running Samba 2.2.7.. I've turned log levels to 10... I have a user who needs this machine to do her job, and she uses Mac OS X. She routinely cannot connect to this box, and gets an error -36. The logs show *NOTHING* when she tries to connect. The machine is properly joined to the domain, and I can reach it from Winblows. Help? Thanks, G. SMB log: [2003/06/30

I'm using RC15 on Solaris 9. The wiki indicates that when a dovecot-shared file exists, "Dovecot uses the same permissions and GID when it creates index files, dovecot-uidlist file, new mail files, etc." In my case, Dovecot *is* creating new index files based on dovecot-shared, but dovecot-uidlist and individual message files don't completely match the permissions/group