|
⇤ ← Revision 1 as of 2022-11-28 14:19:57
Size: 844
Comment:
|
← Revision 2 as of 2022-11-28 14:20:20 ⇥
Size: 852
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 11: | Line 11: |
| '''Events''': EventId 14550, DfsSvc - "The DFS Namespace service could not initialize cross forest trust information on this domain controller, but it will periodically retry the operation. ..." | '''Events''': !EventId 14550, !DfsSvc - "The DFS Namespace service could not initialize cross forest trust information on this domain controller, but it will periodically retry the operation. ..." |
| Line 13: | Line 13: |
| '''Solution''': Changed HKLM\CurrentControlSet\Services\Netlogon\Parameters\SysvolReady to 1. ... and it worked! No reboot needed. | '''Solution''': Changed {{{HKLM\CurrentControlSet\Services\Netlogon\Parameters\SysvolReady}}} to 1. ... and it worked! No reboot needed. |
Troubleshooting Windows Server
Troubleshooting for Windows 2019-2022 can be found below in sections.
Could not start Domain tool X a controller could not be found... or words to that effect
Problem: Had error "Naming information cannot be located because the spcified domain either does not exist or could not be contacted"
Platform: Windows 2022 Server Standard
Events: EventId 14550, DfsSvc - "The DFS Namespace service could not initialize cross forest trust information on this domain controller, but it will periodically retry the operation. ..."
Solution: Changed HKLM\CurrentControlSet\Services\Netlogon\Parameters\SysvolReady to 1. ... and it worked! No reboot needed.
Credit: See https://www.exchangeonline.in/naming-information-located-because-domain-exist-contacted/