search for: macroscoop

I'm trying to setup an idmap ldap backend for a Samba member server in an ADS domain. I'm using Samba 3.0.14a as distributed in Fedora Core 4. All the LDAP stuff seems to work, except the LDAP database is not being populated. The only thing happening is Samba modifying the ou=Idmap,dc=mydomain,dc=com dn. I was under the impression that Samba would automatically populate the LDAP

I have disabled NetBIOS over TCP/IP on our network, both for Windows and for Samba hosts. Samba hosts have these directives in their smb.conf disable netbios = yes smb ports = 445 But I still see NetBIOS broadcasts and responses coming from Samba hosts, probably because they are still running nmbd. Can I just shut nmbd down or does it still have use? Thanks, Pim

We have a system running fedora 8 using pptpd from the poptop yum repository. See http://www.poptop.org/ pptpd/pppd use the winbind plugin from the ppp package to authenticate to Active Directory. This works just fine. Then I found the same setup would not work on a fedora 9 setup. In order to exclude any possible configuration errors I built a virtual machine and simulated an upgrade. This

Our Windows 2003 domain controllers and Samba member servers support both ipv4 and ipv6. Our DNS server resolves hostnames both to ipv4 and ipv6 addresses. Recently, this turned out to be a problem when within a regular Fedora 11 update, samba 3.2 was replaced with samba 3.4. samba-3.4.2-0.42.fc11.i586 to be exact. Everything Active Directory related stopped working and I had to stop winbind

After upgrading one of our servers from Fedora 7 to Fedora 9, from Samba 3.0 to 3.2.0-2.17.fc9 I noticed this strange phenomena: Windows 2003 and XP clients freeze when you type "\\server" in an explorer address bar where "server" is the name of the Samba 3.2 host. Windows 2000 clients don't freeze. 2003/XP clients don't freeze when you enter

Is anyone else seeing Vista (final) will not "connect" to a samba-hosted printer? I'm getting error 0x00000057. I can connect to the port only and install a local driver, though. It's just that the drivers will not load correctly. The drivers do load partly, because I can see driver-specific attributes if I go to "Properties" rather than "Connect". But a test