Re: Windows clients crashing nfs server?

2018-02-15 Thread Rupert Gallagher
Hello Tom,

All relevant ports are already open on the clients. This morning all clients 
failed to mount the shares. Resetting the software servers solved the problem. 
The logs are quiet.

Sent from ProtonMail Mobile

On Wed, Feb 14, 2018 at 19:07, Tom Smyth  wrote:

> Hello Rupert, I might hazard a guess that you open up Windows Firewall with 
> advanced security in windows pro 10 and allow the entire dynamic range of 
> ports that the port mapper might divert the client to, or simply allow all 
> traffic to / from the NFS server on the windows clients (just to test) I have 
> seen issues with Windows Firewall and some updates ( on windows services that 
> use RPC extensively such as MS SQL / SQL Browser) if your windows 10 
> environments are controlled by active directory you may have to set the 
> windows firewall settings in Group Policy (any more than this and im 
> wandering dangerously off OpenBSD Topic ) :) I hope this helps Thanks On 14 
> February 2018 at 15:52, Rupert Gallagher wrote: > This is a recurring problem 
> that is proving hard to fix. When windows 10 pro clients run their security 
> updates and the client restarts, they are unable to reconnect to the nfs 
> server. There is nothing wrong with the network, however, and the nfs servers 
> are up as usual. The only thing that recovers functionality is to stop and 
> restart portmap mountd and nfsd. Am I the only one with this problem? > > 
> Sent from ProtonMail Mobile -- Kindest regards, Tom Smyth Mobile: +353 87 
> 6193172 The information contained in this E-mail is intended only for the 
> confidential use of the named recipient. If the reader of this message is not 
> the intended recipient or the person responsible for delivering it to the 
> recipient, you are hereby notified that you have received this communication 
> in error and that any review, dissemination or copying of this communication 
> is strictly prohibited. If you have received this in error, please notify the 
> sender immediately by telephone at the number above and erase the message You 
> are requested to carry out your own virus check before opening any 
> attachment. @protonmail.com>

Re: Windows clients crashing nfs server?

2018-02-14 Thread Tom Smyth
Hello Rupert,

I might hazard a guess that you open up Windows Firewall with advanced
 security in windows pro 10 and allow the entire dynamic range of  ports
that the port mapper might divert the client to,
or simply allow all traffic to / from the NFS server on the windows clients
(just to test)

I have seen issues with Windows Firewall and some updates
( on windows services that use RPC extensively such as MS SQL / SQL Browser)

if your windows 10 environments are controlled by active directory you
 may have to set the windows
firewall settings in Group Policy (any more than this and im wandering
dangerously off OpenBSD Topic ) :)
I hope this helps
Thanks



On 14 February 2018 at 15:52, Rupert Gallagher  wrote:
> This is a recurring problem that is proving hard to fix. When windows 10 pro 
> clients run their security updates and the client restarts, they are unable 
> to reconnect to the nfs server. There is nothing wrong with the network, 
> however, and the nfs servers are up as usual. The only thing that recovers 
> functionality is to stop and restart portmap mountd and nfsd. Am I the only 
> one with this problem?
>
> Sent from ProtonMail Mobile



-- 
Kindest regards,
Tom Smyth

Mobile: +353 87 6193172
The information contained in this E-mail is intended only for the
confidential use of the named recipient. If the reader of this message
is not the intended recipient or the person responsible for
delivering it to the recipient, you are hereby notified that you have
received this communication in error and that any review,
dissemination or copying of this communication is strictly prohibited.
If you have received this in error, please notify the sender
immediately by telephone at the number above and erase the message
You are requested to carry out your own virus check before
opening any attachment.