MadDoberman
MIS
Hello,
We had Hummingbird's NFS server in a NT machine and the NFS client in a Solaris 5.8 box. This allows an UNIX app to access an NT app's log file in a mounted directory. This combination was OK for a while and then our UNIX administrator complained about the the NFS connection was screwing up the Solaris box. He then proceeded to "adjust" the Solaris box. Since then the filesystem from the NT machine cannot be mounted from the Solaris box. The UNIX administrator maintained that the problem was caused by the directory at the mount point contains embedded blanks. The directory involved in this case is "c:\\Program files\whatsup" which does have embedded blanks. We changed the directory name to "c:\\Progra~1\whatsup" in the NFS server and the Solaris box was able to see both names under the showmount command. However, when he tried to mount either of the directories, he got a "srmount error" instead. Our UNIX administrator insisted that there is nothing he can do about it!
Has anybody out there ever ran into the same problem? Is there any solution to this? Physically renaming the NT directory is NOT an option as the NT app does not allow it. Any help is appreciated.
Mad Doberman.
We had Hummingbird's NFS server in a NT machine and the NFS client in a Solaris 5.8 box. This allows an UNIX app to access an NT app's log file in a mounted directory. This combination was OK for a while and then our UNIX administrator complained about the the NFS connection was screwing up the Solaris box. He then proceeded to "adjust" the Solaris box. Since then the filesystem from the NT machine cannot be mounted from the Solaris box. The UNIX administrator maintained that the problem was caused by the directory at the mount point contains embedded blanks. The directory involved in this case is "c:\\Program files\whatsup" which does have embedded blanks. We changed the directory name to "c:\\Progra~1\whatsup" in the NFS server and the Solaris box was able to see both names under the showmount command. However, when he tried to mount either of the directories, he got a "srmount error" instead. Our UNIX administrator insisted that there is nothing he can do about it!
Has anybody out there ever ran into the same problem? Is there any solution to this? Physically renaming the NT directory is NOT an option as the NT app does not allow it. Any help is appreciated.
Mad Doberman.