Configuring new Subscriber. Publisher can't connect to Subscriber

Hi,
Both the publisher and subscriber are SQL 2005 SP2. I am trying to set up a
new subscriber to a push replication. I have other subscribers that are
working fine. When I try to add a new subscriber I am specifying the
computers name as the 'Server Name'. When the wizzard attempts to connect I
receive an error specifying that 'Cannot connect to XXXXX'. 'Timout expired.
The timeout period elapsed prior to completion of hte operation or the
server is not responding. (Microsoft SQL Server). Is these something that I
need configured on the subscriber machine? I'm sure I am missing something
obvious.
Thanks for your help,
Terry
its hard to say what is the problem here. Set the login timeout to something
large, perhaps 300. Enable logging to see if you can see where it is getting
stuck.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Terry Wahl" <TerryWahl@.discussions.microsoft.com> wrote in message
news:78D0CB4F-5EFA-4D15-B13B-8F54F8D1BF2C@.microsoft.com...
> Hi,
> Both the publisher and subscriber are SQL 2005 SP2. I am trying to set up
> a
> new subscriber to a push replication. I have other subscribers that are
> working fine. When I try to add a new subscriber I am specifying the
> computers name as the 'Server Name'. When the wizzard attempts to connect
> I
> receive an error specifying that 'Cannot connect to XXXXX'. 'Timout
> expired.
> The timeout period elapsed prior to completion of hte operation or the
> server is not responding. (Microsoft SQL Server). Is these something
> that I
> need configured on the subscriber machine? I'm sure I am missing
> something
> obvious.
> Thanks for your help,
> Terry
|||Hi Hilary,
Thanks for the reply. It turns out that the firewall was the issue. Here
is the document that I used to configure the firewall:
http://msdn2.microsoft.com/en-us/library/ms175043(SQL.90).aspx
Thanks again,
Terry
"Hilary Cotter" wrote:

> its hard to say what is the problem here. Set the login timeout to something
> large, perhaps 300. Enable logging to see if you can see where it is getting
> stuck.
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Terry Wahl" <TerryWahl@.discussions.microsoft.com> wrote in message
> news:78D0CB4F-5EFA-4D15-B13B-8F54F8D1BF2C@.microsoft.com...
>
>