Applies to: QSM 4 and XEVO 3 #

How to use net use to mount CIFS share in windows? #

1. Open PowerShell or cmd
2. Enter cmd “net use G: \\192.168.30.106\folder /user:ADdomain\admin 1234”
3. This means you will mount the folder to G: via AD user. You can check it in the windows OS.

How to mount NFS share in windows? #

1. Install “Microsoft Services for NFS”:

• Go to the “Control Panel” on your Windows machine.
• Click on “Programs” or “Programs and Features.”
• Click on “Turn Windows features on or off.”
• Locate and check “Services for NFS” under “Services for Network File System.”
• Click “OK” and follow the prompts to install.

2. Configure NFS Client:

• Once installed, open “Services for NFS” from the Start menu.
• Click on “Client” in the left pane.
• Check the “Enable NFS client” box.

3. Mount NFS Share:

• Open the cmd.
• Use the command “mount ip:/nfs-share/share Z:” to mount the NFS share.

4. Access the Mounted Share

How to clear specific CIFS connection cache in windows? #

1. Enter windows cmd
2. Use net use to check the all CIFS connections.
3. Use command “net use /d \\192.168.195.1” to clear specific CIFS connection.

Why windows 10 OS can’t connect to CIFS share? #

In recent windows update, you may can’t access CIFS suddenly, please follow the steps below to troubleshooting:

1. Please ensure windows login as administrator first.
2. Follow the link below to adjust the parameter, in some scenarios, it can be solve by set “AllowInsecureGuestAuth” value to 1.

Why can’t I access an SMB share from Windows 10? #

If you can’t access an SMB share from Windows 10, check whether the connection requires guest access. Windows security policies may block unauthenticated guest connections.

We recommend connecting with a valid storage system account that has permission to access the share. If guest access is required, have your system administrator review the applicable security policy. In this specific scenario, setting AllowInsecureGuestAuth to 1 may allow the connection, but it enables insecure guest logons and should only be considered after assessing the security implications.

For steps and configuration details, see Microsoft’s guide: Can’t access shared folders from File Explorer.

Why can’t I use SFTP to connect to windows share? #

Windows file exploer does not support SFP. So access via File Explorer using sftp://192.168.201.75

–> Redirects to an FTP connection for access.

Why is there a performance difference in SMB between Windows 10 and Windows 11?  #

There are two default differences between Windows 10 and Windows 11. We recommend trying the following adjustments first to observe whether they help improve SMB performance:

1. Open gpedit.msc, navigate to: Computer Configuration → Administrative Templates → Network → Lanman Workstation
2. Enable the policy “Disable SMB Compression”, then restart the Windows host and observe the SMB transfer performance.
3. If there is no improvement, open secpol.msc, navigate to: Local Policies → Security Options
4. Search for settings related to digital signature, disable all relevant options, then restart the Windows host and observe the SMB transfer performance again.

Windows NFS Client Behavior Verification #

1. Install the NFS client feature on Windows 11 Pro.
2. Create the NFS host configuration.
3. Mount the NFS share using the following command:
   mount \\192.168.194.66\share\fsr1 X:
4. Navigate to the mounted path and create a new folder.
5. Check the result in File Manager.

The expected behavior was that the folder should be displayed normally, similar to CIFS.
However, a permission-related issue was observed. After entering the mounted path, the system showed access denied behavior, and filenames appeared as garbled characters.

This is a known issue of the Windows NFS Client.

The Windows NFS Client, especially Services for NFS or the built-in Windows NFSv3/v4 client, uses ASCII or specific code pages such as BIG5 or GB2312 instead of the widely adopted UTF-8 encoding.

As a result, filename display and permission handling may behave abnormally when non-ASCII characters are involved.

Applies to: QSM 4 #

How to troubleshooting Linux multipath issues?  #

1. Use ping to verify network connectivity between the Linux host and the storage system.
2. If network connectivity is working properly, restart the multipathd service.
3. If the issue persists, contact QSAN Support and provide your network topology, the multipath.conf file, and debug logs for further assistance.

Why can’t I establish iSCSI sessions in MPIO? #

Third-party multipath software installed on the host may interfere with the MPIO configuration used to connect to QSAN storage. If such software is installed, check for potential conflicts.

In a previously reported case, the issue was resolved by uninstalling Infortrend EonPath, restarting the host, enabling the Windows Multipath I/O feature, and establishing iSCSI connections through both QSAN storage controllers.

Before removing multipath software, verify whether it is required for other connected storage systems and schedule a maintenance window, as the change and host restart may interrupt storage access.

Why is an FC LUN not detected by the host even though the FC link is up? #

If the Fibre Channel (FC) links are up but the host cannot detect the LUN, check the FC switch zoning and host group configuration.

1. Verify that the FC host group contains the correct host WWPNs and that the LUN is mapped to the intended host group.
2. Check the FC switch zoning to ensure that the host HBA ports can communicate with the appropriate storage target ports.
3. If the configuration is correct and the issue persists, consider a direct connection test between the host and storage system, bypassing the FC switch, provided your configuration supports it. Schedule a maintenance window if cabling changes may interrupt storage access.

How to configure iSCSI boot from QSAN storage? #

iSCSI boot allows a host to start its operating system from a LUN on QSAN storage. Configuration requirements vary depending on the host’s network adapter, firmware, and operating system. Confirm that your adapter supports iSCSI boot and refer to the adapter vendor’s documentation for detailed instructions.

1. Create a storage pool and volume on the QSAN system, then configure the iSCSI target and map the volume to the host.
2. Open the host’s BIOS/UEFI or network adapter configuration utility and enable iSCSI boot.
3. Configure the host’s initiator IQN and network settings, along with the storage target IQN, target IP address, and boot LUN.
4. After the host detects the target LUN, use the operating system installation media to install the operating system onto that LUN. Follow the adapter and operating system vendors’ instructions for any required drivers and boot settings.

Incorrect Linux FC LUN rescan may cause multipath device issues  #

Issue Description: #

In a Linux Fibre Channel environment, users may attempt to rescan FC LUNs using the command rescan-scsi-bus.sh.

If the command is executed without the proper arguments, the system may detect LUNs incompletely or incorrectly. This can later lead to abnormal multipath behavior, such as incorrect device mapping or missing paths.

---

Root Cause: #

Running rescan-scsi-bus.sh without full parameters may only partially rescan SCSI devices.

When FC paths are not fully refreshed, multipathd may build device maps based on incomplete discovery results.

This can result in stale devices, duplicated entries, or missing multipath members.

---

Resolution: #

Perform a full and safe rescan using the following complete command:

rescan-scsi-bus.sh -m -f -r

-m ensures multipath awareness

-f forces rescan

-r removes stale devices before re-adding

This prevents incorrect device entries and ensures multipath constructs properly.