Jump to content

Raster

Members
  • Posts

    4
  • Joined

  • Last visited

About Raster

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Uruguay
  1. oh, no indeed you are not mistaken. and i am sure that will make it easier to integrate with AD. mine will reject AD logins half the time.
  2. Oh wow, solved it in 1 try 👍 [root@eset ~]# service iptables status Redirecting to /bin/systemctl status iptables.service ● iptables.service - IPv4 firewall with iptables Loaded: loaded (/usr/lib/systemd/system/iptables.service; disabled; vendor preset: disabled) Active: inactive (dead) [root@eset ~]# Starting the service fixed the problem immediately, but If i understand that right Disabled means it won't start on reboot. I enabled it but vendor preset stays disabled. I hope It stays up after reboot. [root@eset ~]# systemctl enable iptables Created symlink from /etc/systemd/system/basic.target.wants/iptables.service to /usr/lib/systemd/system/iptables.service. [root@eset ~]# service iptables status Redirecting to /bin/systemctl status iptables.service ● iptables.service - IPv4 firewall with iptables Loaded: loaded (/usr/lib/systemd/system/iptables.service; enabled; vendor preset: disabled) Active: active (exited) since Thu 2019-06-27 20:38:05 CEST; 11min ago Main PID: 49265 (code=exited, status=0/SUCCESS) Jun 27 20:38:04 eset systemd[1]: Starting IPv4 firewall with iptables... Jun 27 20:38:05 eset iptables.init[49265]: iptables: Applying firewall rules: [ OK ] Jun 27 20:38:05 eset systemd[1]: Started IPv4 firewall with iptables. Thanks !!!!
  3. wont the VHD for Hyper-V work in Azure ? yes i get that you'd need to upload the almost 2gb vhd making it less than an ideal solution. If ir recall correctly you need to switch the disk from dynamically expanding to fixed beforehand, but it should work out of the box, just as it does on Hyper-V.
  4. I've spent the past 4 days trying to decipher what kind of malware is targetting and breaking my ESMC installation. making it completely unresponsive. restoring from backup and it worked for a few hours and dies again ... after combing thru logs and configs, i found that the web server also replies in port 8443 It seems stable for the past day, in that port (the old ERA used it too) but i am not a Linux expert and can't figure out why Apache isn't replying anymore. Is something targetting my https ports and shutting Apache down?. Any clues ?
×
×
  • Create New...