search for: zandbergen

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

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

On 29/10/2020 17:13, Pim Zandbergen via samba wrote: > I have this old Centos 6 server running Samba 3.6 as a member server > in a domain with two Windows Server 2012R2 DC's. > > Through a series of promotions and demotions, the DC's were replaced > with Windows Server 2019 DC's. > > Although I expect...

I will take your suggestion. Still, Samba 3.6 appears to support SMBv2 just fine. Windows 10 PC's and Windows 2019 Servers are able to connect as a client, with SMBv1 disabled. As long as there's a Windows 2012 R2 server doing the backend authentication. Pim On 10/29/2020 7:09 PM, Rowland penny via samba wrote: > I suggest you upgrade your Centos 6 server, it will go EOL in a month

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

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

I have this old Centos 6 server running Samba 3.6 as a member server in a domain with two Windows Server 2012R2 DC's. Through a series of promotions and demotions, the DC's were replaced with Windows Server 2019 DC's. Although I expected problems to arise from that, this has been working fine for months, until the Samba server was reset by the server's watchdog card. Suddenly,

...ch hppa # -arch sparc # To compile 4-way fat, you would append # -arch m68k -arch i386 -arch hppa -arch sparc # FLAGSM = -DNEXT3_0 # LIBSM = # NOTE: ISC is also known as "INTERACTIVE" # This is for Sunsoft ISC SVR3V4 running in POSIX mode # contributed by pim@cti-software.nl (Pim Zandbergen) # FLAGSM = -posix -D_SYSV3 -DISC -DSHADOW_PWD # LIBSM = -lsec -lcrypt -linet # This is for Sunsoft ISC SVR3V4 running in iBCS2 mode # contributed by pim@cti-software.nl (Pim Zandbergen) # FLAGSM = -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_SYSV3\ # -DISC -DSHADOW_PWD -DREPLACE_GETWD -DREPLACE_RE...