Firebird installation on Debian server

Sep 11

Installing Firebird on Debian (Jessie in my case) gave a problem: after installing and starting the server I was not able to connect to the database server:

Your user name and password are not defined. Ask your database administrator to set up a Firebird login.

using the sysdba password I entered in the installation dialog.

Unfortunately it seems the installation procedure has a bug, and does not accept the entered password, but attributes a random password. This random password can you find in the file


The connect with this random password succeedes and you can change your password afterwards – but you must change it with both the Firebird administration tools and inside this file.

The password can be changed with the gsec tool:

gsec -user sysdba -password <password_from_SYSDBA.password>
modify sysdba -pw <your_new_password>

And another speciality for Debian:

The isql tool is called isql-fb

Windows 10 do not likes the netlogon share on server (Samba or Windows)

Aug 28

Today, I had an interesting issue: Windows 10 (workgroup setting, local account) does not connect to the Samba netlogon share, even with the latest Samba version (4.2.3), it asks username and password.
Access to other shares works without any issue.
I had also checked the HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\AllowInsecureGuest setting – it does not change anything.
My temporary solution was to create a new share, identical to the netlogon share, with another name – I choosed netlogonw10. Calling the login script from this share works.

The same is true also for netlogon shares on Windows servers, if the machine is not in the Windows domain

Add Windows 7 PC to Samba Domain after IP address change

Aug 16

Today, I had to change all IP addresses on a customers Samba network. (Really, the customer had two separate networks, and I have unified them to one).

After this, I had to add several Windows 7 PCs to the Samba domain, but the process failed, and the logs on the Samba server had no entries on this.

The error message was:

“The specified domain either does not exist or could not be contacted”

I had added the registry entries specified here:

but nothing.

Finally, the nblookup tool downloadable from Microsofts website pointed me in the right direction: incorrect wins data!

The solution was simple:

/etc/init.d/samba stop
rm /var/lib/samba/wins.*
/etc/init.d/samba start

This recreated the correct wins database wins.tdb and the PC could be joined to the database.

winbindd at 100% cpu after system crash

Aug 17

After a power shortage, nobody could connect to the Samba shares of a Debian Linux server, and a look at “top” on the Linux server showed that the winbindd process used 100% cpu.

The solution was easy:

/etc/init.d/samba stop
/etc/init.d/winbind stop

a kill -9 <processnumber> to the running winbindd process.

Find and remove the gencache.tdb file (/var/lib/samba/gencache.tdb on my Debian server).

/etc/init.d/samba start
/etc/init.d/winbind start
/etc/init.d/samba stop
net rpc join -U administrator%<admin_password>
/etc/init.d/samba start

This fixed the problem.

Configuration: Domain master is a Windows SBS 2003, main file server a Debian Linux Lenny server using winbind as primary autentication mechanism.