June 1, 2011 at 11:24 pm
Comments posted to this topic are about the item Can't Connect Remotely to Integration Services
June 2, 2011 at 2:47 am
Thanks Mohammad, Good one.
M&M
June 2, 2011 at 8:41 am
Thanks, I've attempted to connect to SSIS remotely in the past but was unsuccessful. If I ever have the need to do it again, this will be very helpful.
In your steps you have:
5.Value = ncacn_ip_tcp,0,# where # is the new static SSIS port.
But in your screenshot the middle value is 1. Which is the correct middle value, 0 or 1, or does it not matter? Thanks.
June 2, 2011 at 9:01 am
Sorry for this screenshot . It should be 0.
January 27, 2012 at 11:09 am
Its a great post and fix for the issue Mr.Hoque.
But I am kind of confused how did you happen to find the Port on which SSIS Service was running to be other than 135, as we know as per MSDN, the port cannot be changed.
http://msdn.microsoft.com/en-us/library/ms141198(v=sql.105).aspx
And Just to have any Static Port Opened to connect this Server, would it not jeopardize the security of the company's environment and make it vulnerable to Intrusion attacks.
Please let me know.
Thanks in Advance.
July 17, 2013 at 9:41 am
Why don't you use the GUI for setting this value?
In the Tab(your screenshot) "Endpoints" you can configure exactly the same you did via registry.
Regards
Ralf
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply