search for: restrat

We recently migrated to an active directory controlled domain with the old linux pdc becoming just a member of the new domain. It previously had served as the WINS server. The WINS server settings update was missed on a few printers and these printers continued sending unicast name registration requests to the linux server. With over 300 requests per second being sent from these printers, it came

I have this file in my lib directory that I am using to encrypt/decrypt some stuff. While I am debugging it I have to contsantly start and restart the server in order for the changes to take effect (or for them to be recognized), why is that? Thanks, -S -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are

...destination IN_public all -- eth0 * 0.0.0.0/0 0.0.0.0/0 IN_public all -- eth1 * 0.0.0.0/0 0.0.0.0/0 IN_public all -- + * 0.0.0.0/0 0.0.0.0/0 ----------------------------------------------- Contents on iptables INPUT_ZONE after running 'systemctl restrat firewalld' ----------------------------------------------- [root at dev2 ~]# iptables -nL INPUT_ZONES Chain INPUT_ZONES (1 references) target prot opt in out source destination IN_trusted all -- eth1 * 0.0.0.0/0 0.0.0.0/0 IN_p...

I just noticed that when rebooting a CentOS 7 server the firewall comes back up with both interfaces set to REJECT, instead of the eth1 interface set to ACCEPT as defined in 'permanent' firewalld configuration files. All servers are up to date. By "just noticed" I mean that I finally investigated why a newly rebooted VM failed to allow NFS connections. Prior to doing that.