*update–
I noticed tonight while looking through the event viewer that starting on 08/04/2023–around the time I rebooted my machine for an ESET update that I’ve been getting these WorkflowAppControl that caught my attention. One of them shows  start server…, one of the others shows the IP for my machine that can’t connect to the server and another appears to be part of the computer connect host address. When I look up information on WorkflowAppControl, I’m not finding anything helpful.

*update 2 for the night
I’m not sure that last bit is useful anymore, but I’ll keep it there as I’m hoping someone can still help me out. I also found some other events that started happening on the night evening of 08/04/2023 when I did that update and maybe these will be better. I am seeing DNS client event errors. Specifically they state:
Name resolution policy table has been corrupted. DNS resolution will fail until it is fixed. Contact your network administrator. For more information: read policy table for rule {10F44700-A1E7-425B-ADC9-3D25C910242C} failed with error 0x57
and
Name resolution policy table has been corrupted. DNS resolution will fail until it is fixed. Contact your network administrator. For more information: read policy table for rule {5abe529b-675b-4486-8459-25a634dacc23} failed with error 0x57
However, I’m not sure how to fix it. Any ideas how to fix a corrupted name resolution policy table? Is it a file that I need to replace and I could possibly fix it by getting that file from a back-up?

I decided to ask this here because I can’t seem to get this working anymore. I’ve been using the WSEE on a Server2022 install for over two years and things have gone swimmingly until the last couple of days. I can no longer connect remotely via my old server address in RDP with my windows 10 machine; the only machine that is connected to the server. I can, however, access the server via the the IP address in RDP.

I used the domain skip regfile when I originally set this up. The server tray icon displays green and shows it is connected, but it doesn’t connect to the server. The server shows as available in explorer>network. But if I double-click my server, I can’t access it (Windows cannot access servername). I have to put the server’s IP in explorer to access the shared folders.

I can’t access https://<servername>/connect either. So, I’m hesitant to uninstall the connector software and try again. Although I can access the connector software on other machines and I can access the server through explorer without inputting the specific IP as well. I also tried to run a version of the connector software that I have saved, but it couldn’t find my server when I did that. I could also try and revert to a previous state via backups to where this was working, but I feel like I’m missing something that could solve this problem and I’d like to see if it can be solved without that.

I hope this makes sense.