6.1 HP IBRIX X9000 Network Storage System File System User Guide (TA768-96061, June 2012)

• When creating certificates, verify that the hostname matches the Vhost name.
When creating a certificate, the hostname should match the Vhost name or the domain name
issued when mapping a network drive or opening the file directly using the URL such as https://
storage.hp.com/share/foo.docx.
• Consider the assigned IP address when mapping a network drive on Windows.
When mapping a network drive in Windows, if the IP address assigned to the Vhost is similar
to the format 10.2.4.200, there should be a corresponding entry in the Windows hosts file.
Instead of using the IP address in the mapping, use the name specified in the hosts file. For
example, 10.2.4.200 can be mapped as srv1vhost1, and you can issue the URL https://
srv1vhost1/share when mapping the network drive.
• Unlock locked files.
Use the command BitKinex to unlock locked files if the files do not unlock before closing
the application.
• Remove zero byte files created by Microsoft Excel.
Microsoft Excel creates 0 byte files on the WebDAV shares. For example, after editing the
file foo.xlsx and saving it more than once, a file such as ~$foo.xlsx is created with 0
bytes in size. Delete this file using a tool such as BitKinex, or remove the file on the file system.
For example, if the file system is mounted at /ifs1 and the share directory is /ifs1/dir1,
remove the file /ifs1/dir1/~$foo.xlsx.
• Use the correct URL path when mapping WebDAV shares on Windows 2003.
When mapping WebDAV shares on Windows 2003, the URL should not end with a trailing
slash (/). For example, http://storage.hp.com/share can be mapped, but http://
storage.hp.com/ cannot be mapped. Also, you cannot map https:// because of
limitations with Windows 2003.
• Delete read-only files through Windows Explorer.
If you map a network drive for a share that includes files designated as read-only on the server,
and you then attempt to delete one of those files, the file appears to be deleted. However,
when you refresh the folder (using the REFRESH command), the folder containing the deleted
file in Windows Explorer reappears. This behavior is expected in Windows Explorer.
NOTE: Symbolic links are not implemented in the current WebDAV implementation (Apache’s
mod-dav module).
NOTE: After mapping a network drive of a WebDAV share on Windows, Windows Explorer
reports an incorrect folder size or available free space on the WebDAV share.
Troubleshooting HTTP
HTTP WebDAV share is inaccessible through Windows Explorer when files
greater than 10k are created
When files greater than 10k are created, the HTTP WebDAV share is inaccessible through Windows
Explorer and the following error appears: Windows cannot access this disc: This
disc might be corrupt. This condition is seen in various Windows clients such as Windows
2008, Windows 7, and Windows Vista. The condition persists even if the share is disconnected
and re-mapped through Windows Explorer. The files are accessible on the file serving node and
through BitKinex.
Use the following workaround to resolve this condition:
Troubleshooting HTTP 115