AI is incredibly useful for troubleshooting.

I know the knee-jerk reaction to this comment is “AI makes mistakes, it can’t be trusted”.. but with that in mind and for certain applications, wow. I’m not an expert in active directory, but it drilled down my problem, in the course of about an hour to a missing PDC dns record. This is a situation where I would have had to pay $500 for an incident with MS support in the past, which has only been 3 times over 25 years. I used the paid, $20/month ChatGPT, . And again, I took all the precautions with backups and such before making any changes, I know what some of you might say ;)

reddit.com
u/candyman420 — 11 days ago

Trying to update network to 10.5.6.7, cloud gateway ultra, progress bar doesn't move at all

What could be causing this? (It's not the fiber)

reddit.com
u/candyman420 — 18 days ago

Would anything cause a cloud gateway ultra to drop all connections for 5 minutes?

I'm looking at the connections graph, and they all fall to 0 for several 5 minute periods during the day, as does the bandwidth. This matches the time when users are reporting that they are getting dropped. Is there a more detailed log I can look at via ssh?

reddit.com
u/candyman420 — 22 days ago
▲ 33 r/WindowsServer+1 crossposts

Strange interoperability problem between AD 2019 and 2022/2025

I am getting

Starting test: LocatorCheck Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355 A Primary Domain Controller could not be located. The server holding the PDC role is down.

But only on 2022 AD servers. I brought up another 2025 server thinking this would be faster and easier than to troubleshoot, but it's doing exactly the same thing. FSMO roles were lost? Have to re-seize? Some kind of quirk with the newer editions of windows? The only working AD server I have right now with no errors is 2019, that's what I replicated from. Thanks in advance

reddit.com
u/NotYourOrac1e — 24 days ago

port forwarding doesn't work, what am I missing?

main public (fake) IP: 192.168.0.1

additional public IPs on the same interface, 192.168.0.2, 3, and 4

I've set up port forwarding for 443 (https) onto the extra public IPs, to let's say 10.0.0.5. I've done this in the past with Cisco products and no issue. What am I missing? "It just doesn't work". I've also tried poking holes in the firewall to no avail, but don't think that is even necessary. Thanks!

reddit.com
u/candyman420 — 2 months ago

The latest Exchange SE security updates, anything of concern?

My last client is about to retire exchange for M365, are the latest fixes in exchange SE something to be concerned about, or are they difficult/impossible to exploit? We don't have SE on this one, only 2019, so no updates

reddit.com
u/candyman420 — 2 months ago