Sage 200C

[Sheridan]

We've made the mistake of moving to Sage's new 'cloud' based 200C, cloud based in the sense it uses a click once application on the client and various other executables dumped in the users local profile! I think Sage need to read the definition of cloud based!

 

Anyway - we're struggling to get it working as it seems to try and connect through to their servers on port 2053, which we're trying to get working through our smoothwall.

 

Has anyone done this and got any pointers that would save us some time?

[pete]

When we looked into it (didn't go with it in the end), it needed:

 

TCP ports: 2053, 3789, and 443.

 

We're already a Sage customer and (IIRC) I found that either on the support portal or a sales presentation.

[Sheridan]

It seems it goes through the proxy for some bits, yet bypasses it for others (on port 2053!)

[karldenton]

Remind me in the morning I’ll dig out my notes. We have this installed and had to put exceptions in on our Sophos Utm to get it working.

[SpaceInvader83]

Hi, we use Sage 200 and i had to put quite a few url's in do not authenticate on Smoothwall for it to play nicely. I just looked at the IP of the workstation on the realtime logs and looked out for 407's.

[Sheridan]

Thanks for all the ideas, we found we had to open the port 2053 on our smoothwall proxy as well. Nasty bitty little program this is!