search for: feens

Samba 3.0.11 with Winbind running on Redhat Enterprise Linux 3, compiled with --with-pam (possibly another argument that I can't remember at this second). I applied it to my DC that is playing the PDC role today and all of a sudden Winbind could not enumerate any Active Directory information. Mind you, I'm not joined to the domain using Kerberos/ADS; the libs that come with RHEL3 are

Clients are Windows 2000; server is running Samba version 3.0.2a. We've been a W2K shop for some time but have started to get in a few Windows XP systems (principally laptops). The issue we're experiencing with the Win XP machines is that they can't map the homes share, either through a VPN or when connected directly to the network the samba server is on. All other shares remain

Clients are Windows 2000; server is running Samba version 3.0.2a. We're experiencing a sporadic issue with the homes share occasionally coming up missing. All other shares remain mappable and accessable. If the workstation is rebooted, it can once again access the share. This is new behavior; 2.2.8a did not have this problem. As of yet I haven't been able to figure out what

...: Free open-source (BSD) Opus software for high-quality remote podcasting, radio, voiceover www.feenphone.com 1-minute FeenPhone intro video: https://www.youtube.com/watch?v=uLM97Ue32Vw FeenPhone is already being used to connect remote co-hosts on live syndicated terrestrial radio show, Freedom Feens.

I haven't seen a solution yet, but here's what I'm running into: 3.0.13 with Winbind on Redhat Enterprise Linux 3, compiled with --with-pam as well as attempts with that and --with-acl-support - note that though the samba server is a member of a 2003 AD but not using "net ads" but "net rpc", everything works as desired on 3.0.11 (which I went back to to get this

I sent an email last night regarding a security issue we were having with our Windows 2000 domain controllers and Samba's interaction with them. It turns out part of the issue is that security settings don't propagate to the domain controllers without rebooting them all. But, slightly contrary to my previous email: The application to view these settings is (on a domain controller):

> From: Tom Holroyd <tomh at po.crl.go.jp> > > > > What he is proposing is for OpenSSH to disregard a system-wide policy > > > decision -- that root should not be permitted to directly log in from > > > the network. There are more reasons to disable remote logins as root > > > (vs. normal login then su) than just to prevent plaintext use of the

if ya' haven't seen it already, check out: http://www.canoe.ca/MoneyWSJ/wsj2-dow.html ad, sad, sad. on many fronts. I don't begin to understand how this might work; I suppose the MP3 degradation only applies to MS encoding software... *shrug* this may, however, provide a good leveraging point for Vorbis. have fun dongoodman

Okay, first the admisssions: I'll admit that I haven't been following the development as closely as I probably should have. And I'll admit in this case I might not be using Samba in the most efficient way possible. Also, I'm not 100% sure if I'm encountering a bug or just a seriously stupid misconfiguration issue. And I'm still collecting data on exactly what happened.