Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Adding Integration Services to clustered nodes Expand / Collapse
Author
Message
Posted Wednesday, February 6, 2013 12:21 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, April 29, 2014 12:29 PM
Points: 4, Visits: 188
joffwilliams (11/3/2011)
It turned out to be the result of Windows Server 2008 R2's firewall rules. After adjusting the firewall settings I am now able to connect using the cluster name.


What were the necessary changes to the firewall?
Post #1416683
Posted Wednesday, February 6, 2013 12:29 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Today @ 10:54 AM
Points: 97, Visits: 175
Oh dear... you're testing my memory with that one...

If I recall correctly, you'll need to allow an inbound rule for either the msdtssrvr.exe executable or the port SSIS listens for DCOM on: 135 I think? I'd avoid opening 135 and allow for the executable if I were you.
Post #1416685
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse