Share via

3389 not listening on 1 server 2019

Prezidentj33 121 Reputation points
2023-01-06T15:06:38.273+00:00

Have 1 server 2019 that is not listening to port 3389 when doing netstat -ano I do not see UPD or TCP for 3389.
I do see Remote Desktop Services services running along with
Remote Desktop Configuration
Remote Desktop Services User Mode Port Redirector

I have 2 other 2019 servers that are working with this same Template with no issues so I know this isn't the image that was used. Nothing was different about the setup other than the IP's.

Remote desktop is allowed in FW inbound. Again, same as the other 2 machines.

The only odd thing I see is that in event viewer for this is in Microsoft->Windows->TerminalServices-LocalSessionManager is that informational events show
Event ID 34 "Remote Desktop Services is not accepting logons because setup is running"
Server has been rebooted but this doesn't seem to fix this issue.

I have scoured around on the web for this one and do not find much outside of redoing the system which, I don't understand why that would be the only solution here.
I don't see any missing drivers either in Device Manager "show hidden devices", everything looks the same as the other machines that work (2019 servers)

I can get to the VM by Vcenter so I have access to get into it but would like RDP working incase VMware someday won't come up and then I have no way of getting into it.

Anyone have this issue? And if so what was the solution?

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
Windows for business | Windows Server | User experience | Other
0 comments
Accepted answer
  1. Anonymous
    2023-01-06T22:45:59.7+00:00

    This is a DC

    Then standing up a new one for replacement is by far the simplest / safest and cleanest method.

    I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2019 or 2022, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    1 person found this answer helpful.

4 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-01-06T15:16:16.397+00:00

    I'm guessing you found the same search results that I did. Nothing really conclusive. These one-offs are not really worth spending much time with. I'd clean install it, patch fully, migrate roles over and move on.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    1 person found this answer helpful.
    0 comments
  2. Prezidentj33 121 Reputation points
    2023-01-06T22:33:12.32+00:00

    @Anonymous I may do that down the road as I can still access for now so may just do that after I get some of the other upgrades done. This is a DC so I'd prefer not to have to stand up a new one.

    0 comments
  3. Anonymous
    2023-01-06T22:59:08.95+00:00

    I will want to reuse name and IP for it

    The only method here is to have at least two domain controllers which is always recommended to maintain high availability and for disaster mitigation. I'd also recommend trying to reduce the hard coding issues that are limiting names and addresses of your domain controllers.

    I know there are those issues with security/kerberos sync with DC's

    Patch them fully and you should have no problems. You can check here for both current and resolved windows health issues.
    https://learn.microsoft.com/en-us/windows/release-health/

    --please don't forget to upvote and Accept as answer if the reply is helpful--

  4. Anonymous
    2023-01-09T16:30:25.493+00:00

    I have 2 DCs at the root level plus 4 more as sub domain DC's. I presume moving FSMO roles and then demoting and standing up new one should be no issue as I still have the 1 DC that is up in that root level.

    Yes, that's the simplest solution following the steps I posted above.

    or is this just recommended to prevent issues?

    Yes to reduce / eliminate issues best to patch them all fully.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.