Simple life, Complicated mind

Tuesday, July 22, 2014

Sharing Shared folders files between Linux, FreeBSD and Windows

FreeBSD Windows Server 2008 Note
NFS Server Client Windows Server 2008 has a built-in NFS client.
NFS Client Server Windows Server 2008 has a built-in NFS server.
SFTP Server Client SyncBack Pro, FileZilla.
SFTP Client Server Core FTP, Bitvise SSH Server WinSSHD, VanDyke Vshell.
SMB/CIFS Server Client
SMB/CIFS Client Server mount_smbfs
RSYNC Server Client
RSYNC Client Server
Samba Server Client
Samba Client Server

Note: The Server Message Block (SMB) Protocol is a network file sharing protocol, and as implemented in Microsoft Windows is known as Microsoft SMB Protocol. The set of message packets that defines a particular version of the protocol is called a dialect. The Common Internet File System (CIFS) Protocol is a dialect of SMB. Both SMB and CIFS are also available on VMS, several versions of Unix, and other operating systems.

Acrnois Image Backup shared folder firewall ports

Acrnois Image Backup

TCP/UDP ports: 9876, 9877

Windows Shared Folders

TCP ports: 139, 445
UDP ports: 137, 138

Monday, July 21, 2014

NULL SID Security Log Event ID 4625 when attempting logon to 2008 R2 Remote Desktop Session Host

NULL SID Security Log Event ID 4625 when attempting logon to 2008 R2 Remote Desktop Session Host

Domain sid inconsistent



  • Select "Enter System Out-of-Box Experience (OOBE)"
  • Check "Generalize"

Saturday, July 19, 2014

The server was unable to allocate from the system nonpaged pool because the server has reached the configured limit for nonpaged pool allocations


After several days of backing up clients to a windows 7 machine acting as a BDR, the clients are no longer able to connect. Rebooting the BDR resolves the issue for a few days. 
Looking in the System Event viewer the following entry will be shown.
Error 2017
"The server was unable to allocate from the system nonpaged pool because the server has reached the configured limit for nonpaged pool allocations."


Windows 7 is not designed to handle the large traffic generated by backing up multiple clients. 


The following registry keys can be adjusted to help windows 7 manage the high traffic.
Set the following registry key to '1′ (default value is 0 - zero):
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache
Set the following registry entry to '3' (default value is 1):
A restart is required after making the changes.
Windows 7 should not be used as a backup destination.  Windows 7 is a workstation OS and not intended by Microsoft to be used as a file server.

Acronis Advanced Backup TIB, XML and Catalog files

Catalog contains catalog (that you can see on the 'data view' tab). Without it you can use 'archive view' instead. It will be regenerated on the next backup or manually by 'catalog now' function.
Without xml files archives are restorable, too, however xml files will be regenerated automatically during restore and will not contain some information from the original files. For example, if archive contains several full backups, new xml file will be generated for each chain of full and dependent backups. Archive name will be changed to something like Archive_2013_01_20_ ... (i.e. orignal name + date) If you need to continue backing up to the archive, xml files must not be deleted.

Thursday, July 17, 2014

Static NFS mounts vs autofs direct map mounts

Static NFS mounts vs autofs direct map mounts

Do you use static nfs mounts or automount? If you use automount, the mount needs to get re-established if not acessed for a while, thus delaying the first page load.


It's actually hard to argue one way or the other. The only item I can point out (happened to me) is that if you are using static mounts as in fstab and someone/thing makes an error the system may not boot and you'll have to go into rescue mode to get the system back online. That won't happen when using autofs.

How to mount SMB CIFS Windows shared folder under FreeBSD

This document provides help on mounting SMB/CIFS shares under FreeBSD Operating System.
The mount_smbfs command mounts a share from a remote server using SMB/CIFS protocol. You can easily mount MySharedFolder share using the following syntax:
1mount_smbfs -I //myUser@serverName/mySharedFolder /mnt/mySharedFolder
Where, is the IP address of the remote computer.
myUser is your user name.
serverName is NETBIOS Server Name.
mySharedFolder is CIFS share name.
/mnt/mySharedFolder is the local mount point directory.
You will be prompted for your password. Once this happens you can change to the directory and view the contents using cd and ls command:
1cd /mnt/mySharedFolder
2ls -la
To avoid password prompt, you have to create a .nsmbrc file in your home directory:
1vi ~/.nsmbrc
Set username and password as follows:
Note: Both the hostname and the username need to be in uppercase.
Now mount mySharedFolder as follows:
1mount_smbfs -N -I //myUser@serverName/mySharedFolder /mnt/mySharedFolder
The -N option forces to read a password from ~/.nsmbrc file. At run time, mount_smbfs reads the ~/.nsmbrc file for additional configuration parameters and a password. If no password is found, mount_smbfs prompts for it. You need to use the -N option while writing a shell script.
mount_smbfs does not make the mount permanent. If the FreeBSD system is rebooted, you will have to mount the share again. To make the mount occur each time you start the FreeBSD system, you can put an entry in your/etc/fstab file. An example file would look like this:
//myUser@serverName/mySharedFolder /mnt/mySharedFolder smbfs rw,-N,-I192.168.1.1 0 0
Next, you have to add the username and password to /etc/nsmb.conf: