SSIS Port
Hi: Just wanted to find out what port does SSIS utilizes when communicated with a remote SQL Server. Is it 1434, 1433 or something? I have a SSIS Package on Server 1, which which does inserts on SQL DB on Server 2. I think between Server 1 and Server 2, some ports are being blocked because the 2 servers are separated by a firewall. When SSIS makes connection to Server 2 (SQL), what ports does it use? Also, any other tips would also help. Here is the error I am getting: Cannot connect to 10.xx.xx.xx. =================================== An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
January 23rd, 2007 5:24pm

I believe it uses the same port as what Management Studio would use. Can you run a query in that tool against Server2 from Server1?1433 should be the default.
Free Windows Admin Tool Kit Click here and download it now
January 23rd, 2007 5:31pm

I am not able to connect at all, not even from the Management studio. What other ways I could possibly try. Besides 1433, what other port could be utilized by SSIS?
January 23rd, 2007 5:37pm

This isn't an SSIS issue. If you can't connect via Management Studio, then yes, the ports are probably blocked. Take it up with the network guys.
Free Windows Admin Tool Kit Click here and download it now
January 23rd, 2007 5:42pm

This is only applicable if you are connecting to a remote SSIS package: Here is more on this topic: Integration Services service always uses tcp port 135(RPC). You cannot specify a different port. I havent yet confirmed if a non-transactional package still utilizes DTC for communicating with remote servers. I am doing some testing right now, and will post back on this forum on the update. Refer to the following documentation on MSDN: http://msdn2.microsoft.com/en-us/library/ms141198.aspx
January 24th, 2007 5:36pm

MA2005 wrote: Here is more on this topic: Integration Services service always uses tcp port 135(RPC). You cannot specify a different port. I havent yet confirmed if a non-transactional package still utilizes DTC for communicating with remote servers. I am doing some testing right now, and will post back on this forum on the update. Refer to the following documentation on MSDN: http://msdn2.microsoft.com/en-us/library/ms141198.aspx I want you to understand that you are talking two VERY different things here... In order to communicate to a remote SSIS service, you need to have the RPC port open. What that means is if I want to connect to SSIS through Management Studio, I have to have RPC open.HOWEVER, when an SSIS package runs and it hooks into a SQL Server database, it uses port 1433. The execution of SSIS never uses port 135 (RPC).
Free Windows Admin Tool Kit Click here and download it now
January 24th, 2007 6:04pm

Thanks for the clarification, Phil. Your response really helped me, because I have been somewhat confused about this, and going back and forth with our Network Team. Thanks.
January 24th, 2007 6:14pm

Hello Phil, sorry for bringing up an old thread here, but I found your reply most useful of all I have searched for. I am about to do the same connection with an SSIS-package (SQL-2005) but I am struggling with the port for the execution of this package. I want to transfer a database from server_2 to server_1, where server_1 is the one that hosts and initiate the SSIS-package on a scheduled basis. Server_1 and server_2 sits on two separate subnets with a "closed" firewall in-between. You mention port 1433, but is this the only port needed to be opened for the traffic and data-transfer? I mean the traffic goes in both directions, so I just want to make sure there are no other ports for the actual data-transfer ( from server_2 to server_1 in my example). thx in advance.. Peter
Free Windows Admin Tool Kit Click here and download it now
February 1st, 2011 5:39am

You can register HERE to beat me in sports betting www.wsob.com
February 10th, 2011 5:27am

You can register HERE to beat me in sports betting www.wsob.com
Free Windows Admin Tool Kit Click here and download it now
February 10th, 2011 5:27am

You can register HERE to beat me in sports betting www.wsob.com
February 10th, 2011 5:27am

Do you think you can beat me in sports betting? It’s a free game with very nice prizes. This round it’s a free ticket to any Premier League soccer match of your choice. You can register HERE to beat me! www.wsob.com
Free Windows Admin Tool Kit Click here and download it now
February 10th, 2011 5:35am

Do you think you can beat me in sports betting? It’s a free game with very nice prizes. This round it’s a free ticket to any Premier League soccer match of your choice. You can register HERE to beat me! www.wsob.com
February 10th, 2011 5:35am

Do you think you can beat me in sports betting? It’s a free game with very nice prizes. This round it’s a free ticket to any Premier League soccer match of your choice. You can register HERE to beat me! www.wsob.com
Free Windows Admin Tool Kit Click here and download it now
February 10th, 2011 5:35am

Hi Guys, I need your help to figure it out what Port does my Execute Process Task uses when it is invoked in my SSIS ETL server. How it works is: We have ETL server name "xxxxETL01" and we have SFTP server name "yyyySFTP01". I have one task called Execute Process Task in SSIS package where ETL is excuted in my ETL server but it invoke the WINSCP.exe from SFTP server. My network team is asking what is the port or firewall we need to open for your SSIS to invoke that exe file. Because we gave the SFTP IP address to the 3rd party SFTP server/client to open their port for our SFTP server IP address. Could you please help if anyone have done the same thing... Thanks Ram..Rameshpgs
March 11th, 2011 8:00pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics