While working on a cron job issue, one of the customers wanted to know if they can run the SUA command through a task scheduler instead of cron job. Below are few steps which we can run from the korn/C shell on a system which has subsystem for Unix installed along with SUA SDK package. crontab...

Recently, we had a case where mapping Unix account through ADlookup was not working. Windows 2008 R2 as hosting the NFS share and Windows 2003 R2 was the DC. We performed the steps below: Populated User’s attribute in AD Configured the Netbios name in the NFS properties page Updated...

Recently we got an issue reported, where non admin local user were unable to do RSH from member server. Below were our observation based on our testing: As per our testing on lab machines, we found that the issue was coming when we were logged in as a non-admin local account The error message...

Recently we got a case where customer reported that he was unable to install the SUA SDk component on Windows 2008 R2. Customers had added the feature “SubSystem for UNIX-based Applications” and then click on the link as displayed on the image below. But this opens the Web page for...

We recently got an issue where the Server for NIS service was crashing at a startup. In the environment, customer had added W2K8 R2 based DC and installed IDMU in his existing W2K3R2 based IDMU setup. To begin with we tried checking if the numbers of available port are getting exhausted but that was...

Recently we got a case where customer was unable to access NFS share from Windows 2008 R2, Client for NFS. We tried mounting the NFS share using the command below: mount \\Unix Server\ NFS share The error we got after the command was completed was “Network Error 53”. Then to...

The timestamp gets modified to the current system date, while the files are copied from local drive to mounted NFS drive. File timestamp could be important for auditing purpose, running backup tools or for other reasons. The effected Windows O/S are: Windows 2003, SFU 3.5 , Client for NFS ...

Lot of times, we get request where customer are looking for having a persistent NFS mapping. Well NFS share on Windows clients are not available to all user’s session. One of the recommended option would be to add the NFS resource as a Network location. The steps below describes the same. ...

In recent past, we did have multiple customer reporting issues on files getting corrupted for the below scenario “files created in Windows EFS directory from UNIX clients over the NFS connection” The environment in questions was Windows 2008 R2 as NFS server and Linux client as NFS client...

Recently, we have a case where the customer was unable to copy the Password Sync encryption key from SFU 3.5 to Windows 2008 R2. The customer was getting the following error while copying the encryption key from Windows 2003, SFU 3.5 to Windows 2008 R2. However, the same key was getting copied to Windows...

Most of the domain controllers running on Windows 2003 and serving purpose of Server for NIS for *NIX systems are getting upgraded to Windows 2008 R2 these days. This needs some additional steps to be performed as Services for UNIX 3.5 no longer available on Windows 2008 R2 (as SFU 3.5 does not have...

Recently we got a case where customer was getting error while running the tar command with the P parameter. Customer was getting the error while running the command as a User who is part of the Domain user group. The O/S in question is Windows 2008 R2 x64 bit. On troubleshooting we found that the...

Recently I faced a scenario where Solaris 10 systems were unable to mount the NFS share from a Windows 2008 R2 system. The mount command was throwing error message as “Stale NFS file handle”. Upon investigation it turned out to be an issue with securehandlelevel. The is registry key has...

Consider this scenario: RHEL is working as a NIS Master server. Windows 2008 R2 box is installed with Password synchronization component. Also, the SSOD module has been configured to run on RHEL. PAM module has been added on the RHEL box as well. BTW, new SSOD for Windows 2008 R2 here : http://www...

On Windows 2008 R2; Client for NFS will behave differently depending on the options selected on the Security page of it. Default installation leaves all three options checked. With UNIX systems that can negotiate for Kerberos authentication; selecting Kerb5 and Kerb5i security options will result...