Jump to content

Recommended Posts

Posted (edited)

Hi,

Hoping for some assistance from other users based in Scotland.

In the past week we have seen large numbers of Windows 10 clients unable to connect to Seemis (our MIS). When we enable verbose logging, we can see 403 errors, but have been unable to ascertain the reason behind this, and we are also awaiting feedback from Seemis themselves. Our Windows 10 PC's are all 22H2 with the latest patches, with a mix of kit built in the latter half of 2023 and the others recent builds done in the past few months. As a general rule we can see that the 2023 machines are the ones that fail to connect to Seemis, whereby newer builds (and some we have rebuilt in the past few days) can connect without issue.

Seemis uses it's own compartmentalised java version, and we've checked the comms and can find no issues. We've had an entire suite of 21x PC's (on the 2023 build) that haven't been able to connect, yet when we rebuild one of them with the latest image it suddenly starts working, while the others on the 2023 build remain unable to connect. We've updated NIC drivers, BIOS and chipset drivers, but still no joy. From what we can tell we are getting an SSL handshake, but we are then having authentication knocked back by one of the Seemis edge servers, but trying to fathom what the difference is between the 2023 build and the newer builds in terms of this issue has proven to be a real challenge.

Has anyone else seen this type of error with Seemis in their environment - any assistance would be greatly appreciated.

Many Thanks



 

Edited by kooperthedog

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...