What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Router: MoFi 4500 4GXeLTE-V2, Sim2

If you think it's connected to the lease duration you could try changing the lease time from 12h to 0. I don't know whether the MOFI will accept a value of 0 (or 0h), but quite often a lease time of 0 is interpreted is "infinite". In other words the client never renews the lease, other than at boot time.

With DHCP leases, perhaps set them to 5 minutes and see what happens...

When I was managing a large production network, we had 12 hours, but going into a change, we'd drop it down to 5 minutes until the work was done...
 
Sorry to bother you again, but I thought I'd mention something curious and see what the explanation might be. First, here are two conditions that precede the curious event:

(1) To do our normal, everyday computer work, we need a directory of localhost2 mounted on localhost1 and a directory of localhost1 mounted on localhost2.

(2) When we have a lightning storm, I power down MOFI and both computers and pull all the plugs from the wall electrical receptacles.

Now here's the strange procedure that is required to bring both computers back up and to perform the two mounts:

(1) Boot MOFI.

(2) Boot localhost2.

(3) Boot localhost1.

(4) Mount a directory of localhost1 onto localhost2. SUCCESS.

(5) Mount a directory of localhost2 onto localhost1. DOESN'T WORK:

Code:
[root@localhost1 kmorgan]# mount -t nfs localhost2.lan:/home /mnt/localhost2
mount.nfs: access denied by server while mounting localhost2.lan:/home
[root@localhost1 kmorgan]#

(6) Reboot localhost2.

(7) Mount a directory of localhost2 onto localhost1. SUCCESS. Didn't work in step (5).

(8) Mount a directory of localhost1 onto localhost2. SUCCESS.

We still get the result that we want, but why does it take the extra rebooting? Just thought it would be an interesting question to pose. :)

Thanks so much.
 
Nothing obvious comes to mind. If you boot localhost1 before localhost2 is the problem reversed?

I would use "localhost2" instead of "localhost2.lan" in your mount command. Also check the /etc/exports file on both machines as described in post #8 and check that they don't use the ".lan" suffix. Just so everything is consistent.
 
Old friends meet again!

(1) "If you boot localhost1 before localhost2 is the problem reversed?" -- Yes.

(2) "I would use 'localhost2' instead of 'localhost2.lan' in your mount command." -- I'll try it. Might have to wait awhile--my wife has a project going on localhost2.

(3) "Also check the /etc/exports file on both machines as described in post #8 and check that they don't use the '.lan' suffix." -- Neither file has the ".lan" attached. However, I must admit something. I left the parameters the way I had them in the "old days" -- (rw, sync) and didn't add the ones that you had -- (rw,sync,no_root_squash,no_all_squash) :eek:
 
(3) Leave the options as they were. I was just using the default options on my server as an example.

Maybe it's a timing issue. Does it only happen after you've rebooted the MOFI? Perhaps you have to wait a bit longer before booting the first PC.
 
At long last, I'm back! :rolleyes:

Experiment #1: "Does it only happen after you've rebooted the MOFI?"

Yes. I shut down both computers while leaving MOFI on. Then I booted localhost2 followed localhost1. When both were up, I did the mount command for localhost1 onto localhost2 and then the mount command for localhost2 onto localhost1. Both were successful.

Experiment #2: "Perhaps you have to wait a bit longer before booting the first PC."

I power-cycled MOFI and then brought it back up. I waited a little over half an hour. Then I booted localhost2 followed localhost1. When both were up, I did the mount command for localhost1 onto localhost2: success. Then did the mount command for localhost2 onto localhost1: failure--got the "access denied by server" error. :confused:
 
I think the only way to know what the problem is would be to look at the NFS server log and see why it's refusing the request.
 
Where is the NFS server log?

Also, if it is mounting localhost1 onto localhost2 that gets the error message, which computer is it that "denies access"? I would think it should be localhost2.
 
I don't know anything about what OS you're running (you may have said but I've long since forgotten) but I'd start by looking in /var/log/messages.

Look in the log of both machines, but I'd expect any error messages to be on the server machine. In other words, the machine where the files are actually stored, not where they're remotely mounted.
 

Similar threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top