| sstromer -> Error Message: "The semaphore timeout period has expired" (Feb. 1, '06, 8:24:12 PM) |
Installing and configuring SFU 3.5 has been no less than a very frustrating experience. The documentation is so patchy it needs about as many hotfixes as SFU 3.5 already has available. When I finally get this working, I promise to write some to try to save some other poor soul. In the meanwhile, I could use some HELP.
We have a Fedora server hosting files that need to be accessed by a one LINUX, one Mac and one WIN box (three developers working on one website), and have opted for NFS over Samba. The LINUX and MAC boxes were no problem - The exported shares on the Fedora box are all set to map to one user/group account, which serves our purposes just fine for the moment. We are not running NIS, Active Directory or any other Directory Service. There are simply not enough machines to make it worth the configuration time, yet.
Another key point to this network is that all three 'client' machines are connecting to the server over the public internet. Presently, we are limited to firewall and password protection, but we'll eventually force all these connections through VPNs.
On the Windows XP box, I have installed Client for NFS, Server For PCNFS, and User Name Mapping. On this machine there are simple maps containing the one user and the one group that need to match the Fedora box. After much configuration experimentation, I have finally got to the point where when mapping the share, I receive a 'NFS Login Successful' box displaying the correct UserName, UID and Primary GID. In this box, I click 'Yes' to accept the current login, as the window prompts. I wait for 30 seconds for the connection to complete, and the map to be created, but I receive the error "The semaphore timeout period has expired", and the connection never completes.
Usually, around this time, if I go to a command prompt, and attempt to use the 'mapadmin' command for anything, like 'list' I receive the error "Unable to perform the requested operation as the mapping service cannot be contacted." This seems strange, because I'm assuming that the mapping service was just used to reach the point of seeing the 'NFS Login Successful' box mentioned earlier. Am I missing some large server part that needs to be installed, is having one Win box providing its own User Name Mapping and PCNFS insufficient for consistent mapping service availability, or is there some simple timout setting that will help me to get past the semaphore timeout error? I have search high and low for an answer. I feel so close, yet so far...
Thanks! |
|
|
|