topic Re: SAS EG behind Firewall in SAS Enterprise Guide

SAS EG behind Firewall

HATEM — Tue, 17 Nov 2009 17:07:12 GMT

Hi,

in my last configuration, SAS EG clients and SAS server was in the same subnet. After a migration, SAS server is now in a different subent behind a firewall. That firewall is configured to open port 8561 from A to B (A : is SAS EG client, B : is SAS server). I've changed hots file of the client and everything seems to work.
When I start SAS EG, I find the active connection on the metadata repisotory. The problem is when I try to run a local project (saved on A) I have always an error of connection to (SasMain). can you help me, should I open the port 8561 on both sides (A to B and B to A) ?

Re: SAS EG behind Firewall

Patrick — Wed, 18 Nov 2009 01:02:49 GMT

The server "local" only works if you have PC SAS installed on the same machine where SAS EG is running. Is this the case?

Re: SAS EG behind Firewall

twocanbazza — Wed, 18 Nov 2009 01:36:38 GMT

The port 8561 is the port that the metadata server is using, that will define all the metadata information, it appears that this is working?

However to actually run the project EG will require access to a workspace server (sasmain).
You need to determine, where sasmain is located (ie what server) and what port is being used to comunicate to sasmain, it wont be 8561 on the metadata server :).

You will need to open up a number of ports (Can view in SMC) to enable the entire solution to work.

I could be wrong but my first thought.

Barry

Re: SAS EG behind Firewall

HATEM — Wed, 18 Nov 2009 09:18:39 GMT

ok thank you, I think that I should open port 8591 to let access to workspace. I'll try it. thanks

Re: SAS EG behind Firewall

HATEM — Wed, 18 Nov 2009 11:10:44 GMT

I opened port 8591 and every think is working now, as you told me, a connection to workspace is needed when a request is run. thank you.