Configure SELINUX=disabled in the /etc/selinux/config file: # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # ...
Reboot your system. After reboot, confirm that the getenforce command returns Disabled.
Disable IPV6
# sysctl -w net.ipv6.conf.all.disable_ipv6=1
net.ipv6.conf.all.disable_ipv6 = 1
# sysctl -w net.ipv6.conf.default.disable_ipv6=1
net.ipv6.conf.default.disable_ipv6 = 1
Firewalld needs to be disabled too.
[root@usnyspmtaoem01 ~]# systemctl stop firewalld
[root@usnyspmtaoem01 ~]# systemctl status firewalld
SQL Server was happy enough to start up but I had no joy with getting connected - can only think this was an issue with ipv6 but never found the reason, I reckon there is some bug issue that needs to be fixed that I would love to get to the bottom of but just don't have the time. Eventually gave up and went down the Windows road and downloaded Windows Server 2019 and an evaluation copy of SQL Server 2017.
Relatively straight forward, but when trying to connect hit a few problems. Disabled the Windows Firewall (would not normally do this but machine already behind a firewall anyway, should have just created a rule to "punch through" on 1433). Also, had to enable "SQL Server and Windows Authentication mode" as the server was only set up with Windows Authentication and not applicable for my test environment. Even then had to enable the SA account as this is disabled by default for security - everything working ✔
Just need to build another server and get high availability working now - more to follow.
Just need to build another server and get high availability working now - more to follow.
SA user enabled |
Enable SQL Server and Windows Authenticaion mode |
No comments:
Post a Comment