T
TheLizardBloke
Hi,
I'm having some weird issues following updating a couple of Windows 10 workstations to feature update 20H2 and wondering if anyone can give me some pointers.
Network Configuration
2 Windows 2016 servers that are configured as domain controllers and running DNS (let's call them DC1 and Dc2). Both are up to date with updates. DC1 is the primary.
Workstation 1 Windows 10 laptop running feature update 20H2. This device does not have any issues showing up in the Event Viewer and can see/browse all other resources in the network EXCEPT DC2. Attempts to access this device via RDP fail immediately with the error "An Internal Error Occurred" This machine has a static IP address and an entry in DNS
This machine is no longer available to browse DC2 from the "Network" icon (double-clicking DC2). If I try \\dc2 that also fails with a diagnostic error 0x80070035. I've followed all the solutions I could find that make sense for my environment and everything checks out. I'm also allowing SMB1 on this laptop. Again, even with the RDP error there's nothing in the Event Log.
I CAN browse it by using the IP address i.e. \\192.168.1.9 but CANNOT connect to it using RDP with the IP address.
Workstation 2 Windows 10 desktop running update 20H2. This machine CAN browse DC2 from both the "Network" icon AND IP address, however, it has recently started throwing a dialog at login that says "The security database on the server does not have a record for this computer". If I remove the ethernet cable and log in with cached credentials, then reconnect the cable, everything is fine until the next login.
DC1 This server has no problems browsing DC2 and I can RDP to DC2 from this box without problems. There are no issues in the Event Viewer and DNS appears to be replicating.
DC2 This server can browse all network resources and can RDP to DC1 without issue. I have made sure all necessary services are running and that it is replicating with DC1. No issues in the Event Viewer.
I ran an sfc/scannow on DC2 but this did not reveal any integrity problems
To me, this still sounds like DNS and I'm tempted to flatten and rebuild DC2 but that's a pain I just don't need in my life right now, so I'm wondering if anyone else has some suggestions?
Thanks in advance
Continue reading...
I'm having some weird issues following updating a couple of Windows 10 workstations to feature update 20H2 and wondering if anyone can give me some pointers.
Network Configuration
2 Windows 2016 servers that are configured as domain controllers and running DNS (let's call them DC1 and Dc2). Both are up to date with updates. DC1 is the primary.
Workstation 1 Windows 10 laptop running feature update 20H2. This device does not have any issues showing up in the Event Viewer and can see/browse all other resources in the network EXCEPT DC2. Attempts to access this device via RDP fail immediately with the error "An Internal Error Occurred" This machine has a static IP address and an entry in DNS
This machine is no longer available to browse DC2 from the "Network" icon (double-clicking DC2). If I try \\dc2 that also fails with a diagnostic error 0x80070035. I've followed all the solutions I could find that make sense for my environment and everything checks out. I'm also allowing SMB1 on this laptop. Again, even with the RDP error there's nothing in the Event Log.
I CAN browse it by using the IP address i.e. \\192.168.1.9 but CANNOT connect to it using RDP with the IP address.
Workstation 2 Windows 10 desktop running update 20H2. This machine CAN browse DC2 from both the "Network" icon AND IP address, however, it has recently started throwing a dialog at login that says "The security database on the server does not have a record for this computer". If I remove the ethernet cable and log in with cached credentials, then reconnect the cable, everything is fine until the next login.
DC1 This server has no problems browsing DC2 and I can RDP to DC2 from this box without problems. There are no issues in the Event Viewer and DNS appears to be replicating.
DC2 This server can browse all network resources and can RDP to DC1 without issue. I have made sure all necessary services are running and that it is replicating with DC1. No issues in the Event Viewer.
I ran an sfc/scannow on DC2 but this did not reveal any integrity problems
To me, this still sounds like DNS and I'm tempted to flatten and rebuild DC2 but that's a pain I just don't need in my life right now, so I'm wondering if anyone else has some suggestions?
Thanks in advance
Continue reading...