Hi,
I just updated the firmware on my TS 877 today, and I noticed that after rebooting my NAS I can lo longer authenticate via AD, unless I manually go through the AD connection Wizard again.
My DC is actually a VM on the QNAP so I understand that it may cause a small issue since the DC won't immediately be available upon boot, however I thought there would be some repeat checks periodically etc. The DC appears as 'Standby' if I go to 'Edit Redundant Domain Controller' section.
I also tried setting my QNAP as a Read-Only domain controller on the same domain but I still had the same issues.
Any ideas?
Running Windows Domain Controller as VM Issues
-
fatpizza
- Starting out
- Posts: 21
- Joined: Tue May 06, 2014 10:38 am
-
fatpizza
- Starting out
- Posts: 21
- Joined: Tue May 06, 2014 10:38 am
Re: Running Windows Domain Controller as VM Issues
Also, I'd prefer not to set the QNAP as a fully fledged DC since I feel that's a workaround rather than fix.
-
SKahle83
- New here
- Posts: 5
- Joined: Sat Mar 16, 2019 4:52 pm
Re: Running Windows Domain Controller as VM Issues
Hey fatpizza, did you ever get anywhere with this? I also setup Win 2019 Server on a Virtual Station VM acting as the DC / AD / DNS, and then I updated the QNAP firmware a few hours later and totally bombed my setup. I can't even get the QNAP to rejoin the domain now.