Resolved.    Thanks, Paul. My IT guys understood your instructions.  What we had to do was to forward three ports: 8561 (inbound/outbound), 8581, 8591   Then add this line to the "hosts" file on my local machine C:\Windows\System32\Drivers\etc\ 127.0.0.1       MYSASSERVER MYSASSERVER.MYDOMAIN.COM   EG access works fine now! ... View more

Forwarded 8581 as well - still, the same error.  ... View more

Chris,  I have both ports forwarded now - 8561 and 8591.  Tested by SAS Integration Technologies Configuration and shows success:   Congratulations! You have successfully established a connection with the SAS server. The details of the SAS server are below. SAS Server Definition Information: Machine DNS Name: localhost Prog ID: SAS.Workspace.1.0 Class Identifier: 440196D4-90F0-11D0-9F41-00A024BB830C Protocol: IOM Bridge Encryption Level: Credentials Encryption Algorithm(s): SASProprietary Port: 8591 Service: sasobjspawn But when I open EG it seems to connect but when I click on the SASapp to see the directory of files on the server, I get these errors:   Exception Details: ---------------------------------------- Exception type: SAS.EG.SDS.SDSException Message: Could not establish a connection to the server on the requested machine. Verify that the server has been started and that the host and port of the server match the client's connection information. Source: SAS.EG.SDS.Model Target Site: SASWorkspace Stack Trace: at SAS.EG.SDS.Model.Server.SASWorkspace() at SAS.EG.SDS.Views.View.DoPopulate(DisplayOperation& op) Inner Exception Details: ---------------------------------------- Exception type: SAS.EC.Directory.Model.SDSException Message: Could not establish a connection to the server on the requested machine. Verify that the server has been started and that the host and port of the server match the client's connection information. Source: EC.Directory Target Site: Connect Inner Exception Details: ---------------------------------------- Exception type: System.Runtime.InteropServices.COMException Message: Could not establish a connection to the server on the requested machine. Verify that the server has been started and that the host and port of the server match the client's connection information. Source: SASObjectManager Target Site: CreateObjectByLogicalNameAndLogins Stack Trace: at SASObjectManager.ObjectFactoryMulti2Class.CreateObjectByLogicalNameAndLogins(String Name, Boolean synchronous, Object pIOMI, String LogicalName, LoginDef pOMRLoginDef, LoginDef pSASLoginDef, String nameValuePairs) at SAS.EC.Directory.Model.Server.Connect(ConnectionInfo connInfo)   What else does Enterprise Guide need to successfully connect? ... View more

MP Connect looks promising. I checked and SAS/Connect is not part of our order. Also it is not under the BI Server deployment plan. It shows up in the Appdev plan though. So, not gonna happen for us.  ... View more

Thank you, I'll review.  ... View more

OK, thanks, I'll look into this.  ... View more

Chris,  I am forwarding port 8561 on the SAS server to a port on my local machine via Bitvise SSH and then pointing EG to the local port.  However, it looks like I also need to forward 8591 as well, which I can do, but then how do I point EG to the local port? Does EG has a config file somewhere in C:\Program Files\SASHome\SASEnterpriseGuide\7.1 ?   Will it work if both ports are forwarded and pointed to? ... View more

Because this is the first time I hear about MP Connect and also we do not have SAS/Connect in our purchase order. What we have is SAS EG, SAS BI server and the SAS/Access modules.  ... View more