M
Mufassa29
Hi Everyone
I've been beating my head against the ground with this one and haven't managed to identify the issue or any resolution. We have checked everything from switches, VLANS and routing. There is no issues with replication or DNS between the domain controllers either. Drivers are current, Firmware are on the latest levels etc.
We are experiencing the issue on a 3 Node Failover Cluster Running Server 2016 and SQL Server 2016 installed on the Nodes as a fail over SQL Cluster. Up till now we haven't had any issues and the issues started about three weeks ago.
Initial Join of Node to the Domain is successful. Reboot after Domain Join and opening Local Computer Group and Administrators Group displays Domain Users names successfully. Domain\Username. After a second reboot the Local Administrators group displays usernames as a SID. Testing of the trust relationship between the Member Server and Domain Controllers is successful. Uninstalling the network adapters and reinstalling the network adapters and applying the IP configuration on the affected machines resolves the issue as well and Domain Usernames are displayed correctly. After a reboot the issue is prevalent again and the usernames are displayed as SIDS instead of friendly names.
1. Usernames Displayed as SIDS - Domain Users can login successfully that has been added to the Local Administrators Group.
2. Browsing to the Domain controllers sysvol is successful and no authentication prompts appear.
3. The Windows Cluster runs and all roles move and fail over between nodes successfully.
4. Events in the Event viewer has warnings and errors, No time sync and net logon failure. After removing the network adapters as described above and re-installing via the console and configuration of the Network adapter with an IP, subnet etc the Local Computer Administrator groups are populated with friendly names again, after this the event viewer logs does not log any time or Net logon events and everything is normal. After reboot of the node the issue surfaces again.
Kind Regards
Leo
Continue reading...
I've been beating my head against the ground with this one and haven't managed to identify the issue or any resolution. We have checked everything from switches, VLANS and routing. There is no issues with replication or DNS between the domain controllers either. Drivers are current, Firmware are on the latest levels etc.
We are experiencing the issue on a 3 Node Failover Cluster Running Server 2016 and SQL Server 2016 installed on the Nodes as a fail over SQL Cluster. Up till now we haven't had any issues and the issues started about three weeks ago.
Initial Join of Node to the Domain is successful. Reboot after Domain Join and opening Local Computer Group and Administrators Group displays Domain Users names successfully. Domain\Username. After a second reboot the Local Administrators group displays usernames as a SID. Testing of the trust relationship between the Member Server and Domain Controllers is successful. Uninstalling the network adapters and reinstalling the network adapters and applying the IP configuration on the affected machines resolves the issue as well and Domain Usernames are displayed correctly. After a reboot the issue is prevalent again and the usernames are displayed as SIDS instead of friendly names.
1. Usernames Displayed as SIDS - Domain Users can login successfully that has been added to the Local Administrators Group.
2. Browsing to the Domain controllers sysvol is successful and no authentication prompts appear.
3. The Windows Cluster runs and all roles move and fail over between nodes successfully.
4. Events in the Event viewer has warnings and errors, No time sync and net logon failure. After removing the network adapters as described above and re-installing via the console and configuration of the Network adapter with an IP, subnet etc the Local Computer Administrator groups are populated with friendly names again, after this the event viewer logs does not log any time or Net logon events and everything is normal. After reboot of the node the issue surfaces again.
Kind Regards
Leo
Continue reading...