All of lore.kernel.org
 help / color / mirror / Atom feed
* SFU to NFS Returns Error: "The semaphore timeout period has expired"
@ 2006-02-03 16:38 Steven Stromer
  0 siblings, 0 replies; only message in thread
From: Steven Stromer @ 2006-02-03 16:38 UTC (permalink / raw)
  To: nfs

We have a Fedora server hosting files that need to be accessed by 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, so no real directory services are needed there. 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 just yet.

Another key point to this network is that all three 'client' machines 
are connecting to the Fedora server via the public internet. Presently, 
we are limited to firewall, password, and NFS configuration protection, 
but we'll eventually force all these connections through encrypted 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 form the Win XP box to the Fedora 
box, 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 searched high and low 
for an answer. I feel so close, yet so far...

Thanks for an assistance!

Steven Stromer



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2006-02-03 17:31 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-02-03 16:38 SFU to NFS Returns Error: "The semaphore timeout period has expired" Steven Stromer

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.