Sorry to crosspost, but no answer in SSIS forum.

I have binged and googled this issue.

We have SQL 2005 Enterprise behind a firewall on Server 2003.

We are not running Windows firewall, SSIS is installed on the Server. We
cannot connect remotely. There is a hardware firewall. 135 and 3882 are open.
RPC and RPC Locator are both set to start automatically on the server and the
client.

We are able to connect via any machine on the same subnet. We cannot
connect from a different subnet.

Please help. All the pages out there suggest stuff we have already tried
except for manually editting the registry to set the ports it uses. It seems
to use random ports after you connect with 135 - is that the issue?

If the random port is the issue, how does everyone else solve that with
hardware firewalls?

Hi Jim

Just out of curiosity, when you said that you can not connect to SSIS, are
you trying to connect using SQL Server Management Studio (SSMS)? And use SSMS
to execute the SSIS package?

In that case, you would also need port 1433 to be open. Although I am not
sure that's a good idea if it means opening up to the outside world. But I
remember reading something along this line with a bit of explanation from the
following posting:
http://social.msdn.microsoft.com/for...f-b0de4de8d0fb

Thank you
Lucas

"Jim Craddock" wrote:

No, that isn't the problem. We can't connected at all using Mgmt Studio, at
least not from outside the firewall.

There has to be something besides 135 that needs opened. I can telnet to
135 and get a blank screen which evidently is a positive indication the port
really is open, and you can connect from the same side of the firewall as the
server using SSIS in management studio. However, if you try to connect from
outside the firewall, SSIS won't connect. You can connect from outside the
firewall just fine using the database portion of Mgmnt Studio (this is IP
restricted so not a security concern, just not SSIS).

"Lucas Kartawidjaja" wrote:

I should have probably ask you this first, but what error are you getting
when trying to connect? Integration Service needs to use Windows
authentication method. In your setup, when the user is on the other side of
the firewall, what user account does the user use and can they authenticate
on your domain?

As for ports

"Jim Craddock" wrote: