Lemonde
  • Lemonde
  • 100% (Exalted)
  • Advanced Member Topic Starter
2 years ago
What are the implications of seeing this?

Log Name: System
Source: Microsoft-Windows-TerminalServices-RemoteConnectionManager
Date: 05/05/2020 17:38:21
Event ID: 1067
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: server01.domain.local
Description:
The RD Session Host server cannot register 'TERMSRV' Service Principal Name to be used for server authentication. The following error occured: The specified domain either does not exist or could not be contacted.
.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-TerminalServices-RemoteConnectionManager" Guid="{C76BAA63-AE81-421C-B425-340B4B24157F}" EventSourceName="TermService" />
<EventID Qualifiers="49152">1067</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-05-05T16:38:21.255087400Z" />
<EventRecordID>336162</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>server01.domain.local</Computer>
<Security />
</System>
<EventData>
<Data>The specified domain either does not exist or could not be contacted.
</Data>
</EventData>
</Event>

Does this mean that the network host TERMSERV will have the wrong IP?
Sponsor

Want to thank us? Use: Patreon or PayPal or Bitcoins: 12G4A52Znm5s35buKDEmKU2p2vQY69Nsyo

All opinions expressed within these pages are sent in by members of the public or by our staff in their spare time, and as such do not represent any opinion held by sircles.net Ltd or their partners.


sirclesadmin
11 days ago
This is a result of the server not finding the DNS server or the DNS server returning the wrong details for the Domain Controllers.

You can probably solve this by:
  1. Checking the DNS server IPs on the RD server and correcting any error
  2. Flushing the DNS - in an elevated CMD session type: ipconfig /flushdns to clear the DNS cache
  3. Re-registering with the DNS servers to overwrite any incorrect DNS record - in an elevated CD type: ipconfig /registerdns
  4. Checnking that the DNS servers are running and responsing to DNS requests