08-27-2024, 03:00 AM
Once I had set up NishanF's native Echo setup, it has worked great until now.
Now it is failing while accepting security context. I will have to dig around the wayback machine to see if I can find some of the setup info NishanF wrote. It may be that AWS has changed something on their side to cause the error. I was using a secure port (non-standard) to send the info back to CQC, but apparently something has changed.
It could also be the CQC machine, but since I have updates turned off, I find it hard to believe something would change there.
Now it is failing while accepting security context. I will have to dig around the wayback machine to see if I can find some of the setup info NishanF wrote. It may be that AWS has changed something on their side to cause the error. I was using a secure port (non-standard) to send the info back to CQC, but apparently something has changed.
It could also be the CQC machine, but since I have updates turned off, I find it hard to believe something would change there.