Ask a question


How can we help you today?

Ask Question
Manage notifications
Subscribe to this question
Paul Thomson

SBS2011 to 2019 Std with On Prem Exch 2016 post migration issues

A couple of little issues after migration from SBS 2011 to 2019 standard & Exchange 2016 (on Server 2019).

Workstations - "DNS_PROBE_FINISHED_BAD_CONFIG" in web browser - takes 10 - 60 seconds to find web page

On the 2019 Domain server - "Windows Could not start the Diagnostic Policy Service service on local computer, Error5: Access denied" - event when run as "Administrator" - discovered this as the network icon has a Yellow "!"  (IPv4 settings - preferred DNS server is 127.0.0.1, while the server IP address is on 192.168.100.xxx range & no alternate DNS server) - when "Troubleshoot Problems" cannot start Diagnostic Policy service"

Googled some pages - one was to change permissions in regedit - which I discovered same issue "Don't have permission"

Also - Sonicwall firewall, Printer and NAS cannot connect to LDAP anymore!

Any help/advice would greatly be appreciated

Thanks

Paul

asked05/25/2020 07:34
79 views
Add Comment
Last Activity 05/25/2020 08:42

1 Answer(s)

  • Mariette Knap

    Hello Paul,

    Some comments or tips

    1. Check with an IPconfig /all what DNS settings those workstations have. It should have the IP address of your Domain Controller because that is also the DNS server. Anything else is wrong
    2. Ignore the Diagnostic Policy Server.
    3. Check DNS settings on the new DC and make sure it has only Preferred DNS server settings set to 127.0.0.1 if you do not have another DC. Also meaning that the SBS must have been demoted.
    4. Windows Server 2019 by default no longer supports SMB 1.0 because it is obsolete and insecure. The lack of this is probably the reason why those devices cannot use LDAP. Either update those devices or enable SMB 1.0. If those devices use SMB 2.0 you may need to turn on "Enable insecure guest logons",  see Guest access in SMB2 disabled by default in Windows 10 and Windows Server 2016. I would change that on a seperate Group Policiy and apply to whatever it is needed on, in this case it is the DC only I think.
    answered 05/25/2020 07:49
    Add Comment
    Paul Thomson

    Thanks for the quick reply!

    1. IPconfig /all - results in the DNS server pointed to the new 2019 DC - so that is correct

    3. In "Network Connection Details" IPv4 DNS server is blank - but going into IPv4 Properties "Use the following DNS server address is ticked and preferred DNS server is 127.0.0.1 - no alternate DNS server. SBS 2011 has been demoted to a workgroup and is turned off.

    4. - Im assuming has to do with the above issue. Another site that I have finished migrating from SBS2011 to 2016 std - Sonicwall exact same model/firmware as this one, can connect via LDAP without any issue. Also exact same settings as point 3 above. So the exact same as this one! Only difference is server 2016. Diagnostic Policy Service is also running etc.

     

    Thanks again

    Mariette Knap

    You have migrated to Windows Server 2019 and that differs from 2016 concerning Ldap issue

    replied 05/25/2020 08:42
    Reply
    replied 05/25/2020 08:14
Add an Answer