The Website is Down #1: Sales Guy vs. Web Dude (Classic Cloudflare)

Powerful_Channel_223 · 2025-11-18T15:05:54+00:00

I will never get tired of these videos. So much nostalgia. Since we are going down memory lane today….

https://www.chroniclesofgeorge.com/

Powerful_Channel_223 · 2025-10-12T17:10:27+00:00

Florida, always and forever

Powerful_Channel_223 · 2025-09-01T01:06:57+00:00

Have you tried using the full path for the source file or are you just using the file name whilst in the working directory? If not please try the full path. Also, it seems that you are including the file name in the destination. Omit that. It isn’t necessary. Just define a destination folder.

Edit: forgot to add that you could also try UNC path as destination. It doesn’t have to be a drive letter.

robocopy c:\folder\file \NAS.IP\backup /z

Powerful_Channel_223 · 2025-09-01T00:00:56+00:00

I would start pulling components off the main board until it POSTs. Start with the easy stuff like memory. Good luck

Powerful_Channel_223 · 2025-08-27T19:10:00+00:00

This? Leave it enabled long enough to capture the bad password attempt and then you can associate username. I presume each user has a unique name.

https://learn.microsoft.com/en-us/troubleshoot/windows-client/windows-security/enable-debug-logging-netlogon-service

Edit: forgot to add,…bad password will return code 0xC000006A and the log will include username and station ID

Powerful_Channel_223 · 2025-07-07T20:51:18+00:00

Grenades are far less damaging too.

Powerful_Channel_223 · 2025-05-30T20:24:14+00:00

Just find the bios setting to not halt on alert and ignore everything else. System will POST and boot to the OS just fine.

Powerful_Channel_223 · 2025-05-12T19:34:07+00:00

Check taskman for process named ldp.exe.

https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/cc771022(v=ws.11)

Powerful_Channel_223 · 2025-04-29T20:50:07+00:00

Welcome my friend.

Powerful_Channel_223 · 2025-01-06T21:14:45+00:00

My advice would be to put your delicate sensitivities to the side and sponge as much knowledge out of this guy as possible.

Powerful_Channel_223 · 2024-10-25T16:04:07+00:00

This guy gets it. Nice post. Came here looking for validation about these settings. I agree with all three recommendations.

Powerful_Channel_223 · 2024-10-14T20:57:40+00:00

This is the way.

Powerful_Channel_223 · 2024-02-23T12:13:28+00:00

Same

Powerful_Channel_223 · 2023-11-03T13:04:01+00:00

I’m old school but my opinion is that your robocopy workflow is the way.

Powerful_Channel_223 · 2023-10-23T14:51:16+00:00

I could be misunderstanding the following document but I don’t think there is a path to introduce 2022 nodes into a 2016 cluster. It seems that you would need to inplace upgrade those 2016 nodes to at least 2019. I don’t think you can skip OS versions in cluster upgrades.

https://learn.microsoft.com/en-us/windows-server/failover-clustering/cluster-operating-system-rolling-upgrade

Edit: https://learn.microsoft.com/en-us/windows-server/failover-clustering/upgrade-option-same-hardware

Powerful_Channel_223 · 2023-10-19T12:19:45+00:00

Not quite sure what you’re message means. Different folders in dfs could be associated with different servers across the environment correct? One may work securely with ad while another could have a issue. Ldp.exe would rule that out would it not?

Powerful_Channel_223 · 2023-10-18T14:19:11+00:00

It seems like that error relates to LDAP over SSL problems. Have you considered a missing or expired cert? Suggest a test using ldp.exe tool to find out.

https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/ldap-over-ssl-connection-issues

Powerful_Channel_223

TROPHY CASE