" 00ScarlettJohnson" <E*@yahoo.com> wrote in message
news:uVGoFOxgHHA.588@TK2MSFTNGP06.phx.gbl...
>I am running trigger with update on a linked server in SQL 2005 SP2. It is
>running very smooth and when I turn on the firewall, the trigger action is
>giving error and failed to take action. Is this a Big NO between firewall
>and Linked server? Is there a way to solve this problem? Thanks.
>

"TheSQLGuru" <kgbo***@earthlink.net> wrote in message
news:ec5p9z1gHHA.1220@TK2MSFTNGP03.phx.gbl...
> You simply need to ensure the appropriate ports are open on the firewall,
> at least between the two servers of concern.  A simple packet capture
> while the trigger is firing should inform you as to what needs to be
> opened up.  At a minimum it should be TCP 1433 and probably 1434.  I don't
> know if other's are involved in remote proc executions or not.
>
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
>
> " 00ScarlettJohnson" <E*@yahoo.com> wrote in message
> news:uVGoFOxgHHA.588@TK2MSFTNGP06.phx.gbl...
>>I am running trigger with update on a linked server in SQL 2005 SP2. It is
>>running very smooth and when I turn on the firewall, the trigger action is
>>giving error and failed to take action. Is this a Big NO between firewall
>>and Linked server? Is there a way to solve this problem? Thanks.
>>
>
>