Browse by Tags

Related Posts
  • Blog Post: Accessing NFS shares through an application

    We do get a lots of cases in which customer is looking to mount a NFS share as a System account so that the share is available even when the users logs off. This is usually required in scenarios where customer is running certain application which would access the NFS share. The best option is to...
  • Blog Post: Important Tips on NFS (Part 4)

    What registry keys can be modified, if the number of Unix clients are more? We can make the following registry changes: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Rpcxdr\Parameters · Right-click DefaultConcurrentConnections, and then click Modify è default value...
  • Blog Post: Adding NFS resource as a Network location for persistent access

    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. ...
  • Blog Post: NFS over Distributed File System

    What is DFS? 1) Group shared folders located on different servers by transparently connecting them to one or more DFS namespaces 2) DFS Namespace: Virtual view of shared folders 3) Using the DFS tools, an administrator selects which shared folders to present in the namespace, designs the hierarchy...
  • Blog Post: Service logon credentails for 'Client for NFS' service

    On Windows 2003, SFU 3.5: In SFU 3.5, the default logon type is ‘local system’. We can however change the service logon type to “domain admin” credentials. The service still works. On Windows 2003 R2: The ‘client for NFS’ service logon type is designed to...
  • Blog Post: Updating SFU 3.5 - Gateway for NFS to the latest possible drivers

    Services for UNIX 3.5 is on maintenance mode now and there will be no other update to this (read expect few scenarios). Additionally Gateway for NFS has been removed in Windows 2003 R2 and onwards. I know still a considerable amount of systems uses Gateway for NFS from Services for UNIX 3.5. The best...
  • Blog Post: Client for NFS on Windows 2008 R2 and Security options

    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...
  • Blog Post: Unlocking restricted ports for Windows NFS Client

    A very common way to restrict a normal user to pose as root In UNIX world is to restrict certain ports commonly known as “secure ports”. Generally a deamon runs and does port monitoring to ensure any attempt to access such secure ports by a normal user is blocked. The TCP ports 1-1024 are reserved for...
  • Blog Post: Symantec backup is unable to locate NFS drive

    Recently we got a case where customer was trying to do a backup of a NFS share using Symantec. He was trying on Windows 2008 R2 and was running into issues. However, it worked in Windows 2003 SP2 + SFU 3.5 Gateway environment. In W2K3, we had a product called Gateway for NFS. Gateway for NFS used...
  • Blog Post: How to programmatically access NFS share using Windows API

    Recently, we got a case where the customer wanted to programmatically access NFS share using Windows API. We have an API “WNetAddConnection2” which can be used programmatically for accessing NFS share. So we tested and wrote a code for the customer using this API to mount the NFS share...
  • Blog Post: Making NFS volumes available to Windows Users

    Very frequently we come across requirement to mount a NFS share for users. A very general approach to mount the share as Administrator or to run the mount command wrapped up in a script. This way the mount works properly but the same mounted drive will not be available for all the users. My experience...
  • Blog Post: "Client for NFS" service cannot be started after stopping it from services console

    On Windows 7 the “Client for NFS” service behaves some way differently than its earlier versions on SFU 3.5 and on Windows 2003 R2. The difference is once “Client for NFS” service is stopped using services console; you cannot start it using Services console; using net start...
  • Blog Post: Important Tips on NFS (Part 3)

    Why we are unable to do a p ersistent mount across logons? Even using the command below to mount NFS share does not work: Ø net use W: \\Server\Sharename /persistent:yes This behavior is by design and due to security enhancement in Windows. NFS mounted drive letters are session specific...
  • Blog Post: Important Tips on NFS (Part 1)

    How can we map users in Windows 2008? In windows 2008\2008 R2, we have the following options: 1. Fetching maps from a windows 2003\2003 R2 mapping server 2. Using Adlookup for mapping domain accounts 3. Using ADLDS for local accounts Why the mapping information is not getting saved...
  • Blog Post: Getting Network Error 53 “Network path not found"

    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...
  • Blog Post: Concepts on multiple user mapping

    We do get a lot of questions on multiple users mapping between Windows and Unix users. I have tried to list the questions and the answers for them through this blog: How does multiple user name mapping works <Answer> We can map a Windows-based account only to a single UNIX-based account...
  • Blog Post: Getting Red X sign on mounted NFS volume from Windows client

    Windows NFS client is known not to handle multiple path NFS shares. The issue is by design and comes when the client is mounting an NFS share which is more than 26 characters in length. Users would be able to access the NFS shares after mounting it to a drive letter but a red X (disconnected) sign...
  • Blog Post: Windows Vista and Older NFS Servers

    Windows Vista and Older NFS Servers Sometime back I came across a problem where the Windows Vista client was not able to mount a NFS version 2 share from a SCO NFS server. At first, it looked like the Vista is using high ports while the server is probably expecting the client to use privileged ports...
  • Blog Post: Explorer Windows on windows NFS client freezes while access shares hosted on NetApp

    Recently we got a case where the explorer window on the Windows NFS client was freezing intermittently and the unfreezing while it trying to access NFS share. The NFS share was hosted on NetApp filer and hence was a multipath. Initially we thought that it could be an issue with the multipath NFS share...
  • Blog Post: Unable to access NFS shares from Windows 2008 NFS client

    We recently got a case where customer was trying to access NFS share hosted on Unix machine from Windows 2008. Issue was isolated to this windows 2008 client only. We tried accessing the share from Windows client with the following options: · Mount command returns Network error ‘5’ · ‘net use...
  • Blog Post: List of Hotfix for SFU 3.5

    Please find the list of Hotfix for SFU 3.5. For Server for NFS: http://support.microsoft.com/kb/939767 for Nfssvc.exe/Nfssvr.sys ( 8.0.2254.19) http://support.microsoft.com/kb/933397 for Nfssvr.sys ( 8.0.2254.20) ( You would first need to install the above patch to update the nfssvc...
  • Blog Post: Unable to start “Client for NFS” service on Windows 2003 R2 x64

    Recently we got a case where customer was having issue starting Client for NFS service. It was returning an error message “failed to load dependencies” We checked the “Client for NFS” service properties and found that the dependencies were listed properly. We also...
  • Blog Post: Persistent drive mappings do not work with Client for NFS

    Persistent drive mappings do not work with Client for NFS After SFU 3.5 was shipped, there have been a lot of changes in Windows networking client stack. Some of these changes affected the way persistent drive mappings for NFS shares are handled in Windows and as a result, it doesn’t work anymore...
  • Blog Post: How can we control the permission on the files created from Windows NFS client

    We do get a lots of issue where the customer reports that “Permission ere not getting inherited on the newly created files and folder on the NFS client side”. This scenario is intended for the scenario where Windows is the NFS client (running “client for NFS”) service. Usually...
  • Blog Post: Secondary GID not working with ADlookup

    Recently we had a case where users from Windows 7, NFS client were unable to access the NFS share. Adlookup was set up properly. And changing the setting to fetch the information from Windows 2003, User name mapping server resolved the issue. Note: We did not change any settings on the Unix NFS server...