Request to test against another Smoothwall + Server2012R2

[pete]

Bit of an odd one here.

 

Does someone with a Server 2012R2 server (that's supposed/allowed to access the Internet) and a Smoothwall running Leeds 48 (current latest) mind visiting

 

https://api.roombookingsystem.co.uk/PESMis.svc?

 

in Internet explorer and posting success / failure as a comment?

 

Background:

 

We have a bit of middleware (SIMS > Roombooking System) running on a Server 2012R2 VM that's no longer talking to the API URL above. Nor does Internet Explorer on 2012R2.

 

However, on Server 2019 (same proxy settings & filtering), Internet Explorer has no issues opening the API URL.

 

This was definitely working on 22/03/21 (it's a manual sync done once a term, so pinning down the "it stopped working on" date is tricky). I've pretty much narrowed it down to "move the sync tool to a 2019 VM", but I'd be intrigued to see if it's just our site or a "doesn't work on 2012R2 at all now".

 

cheers

[ifarmery]

Success for me, server will be set as an exception on the Smoothwall though so no filtering applied to it.

[pete]

Yeah, the server is set as exception in SW here too. Checking available ciphers it's the same across 2012R2 and 2019 so it shouldn't be a connection negotiation problem.

 

Flipping it to no exception in an attempt to get better logs (in case the vendor has an undocumented dependency on different domain) doesn't reveal a lot and the sync tool's logs are rather terse.

 

Other MIS > third party sync tools (Wonde, Groupcall, ParentPay, SIMS Options) on the same server connect without issue, whether using the default proxy pulled from IE or explictly configured.

Edited July 14, 2021 by pete

[slugshead]

The IP range for our servers is allowed to bypass the smoothy as above

 

[pete]

The IP range for our servers is allowed to bypass the smoothy as above

 

[ATTACH=CONFIG]62600[/ATTACH]

 

Same here. Our SW still chokes if you're trying from IE on a 2012R2 VM. Works fine on everything else.

Edited July 14, 2021 by pete

[ibpalle]

Using port 801 is still going through the proxy so while filtering isn't applied the issue may be the just the proxy. Try removing proxy settings - you should have firewall rules that allow outgoing https for the IP address of the server too.

[Jcx500]

Just an idea is the proxy set in netsh?