Re: Problem With Replication On Port 2433
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Tue, 30 Oct 2007 20:48:27 -0400
Is the distribution agent using the alias you configured for server2 in its
job properties? This should work if it is.
Another option would be to make it a pull, or anonymous pull subscription.
--
Hilary Cotter
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
<shgzs33@xxxxxxxxx> wrote in message
news:1193733892.823751.241050@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have 2 SQL 2005 Servers SERVER1 and SERVER2 and want to establish a
replication betwwen them: SERVER1 as Publisher and SERVER2 as
subscriber.
the problem is that SERVER2 is runnint on port 2433 and -I dont know
why- I cannot switch it to port 1433.
When trying to push a new subscription on SERVER1 to SERVER2, it tells
that:
"Cannot connect to SERVER2,2433.
SQL Server replication requires the actual server name to make a
connection to the server. Connections through a server alias, IP
address, or any other alternate name are not supported. Specify the
actual server name, 'SERVER2'. (Replication.Utilities)"
So, I'd set an alias on SERVER1 for SERVER2 and this part of problem
resolved. subscription was estableished and It appeared under "SERVER1
Replication > Local Publications > [publication name] " inmanagement studio.
But When trying to start synchronising, it fails with a mesage
indicating that it couldnot connect to SERVER2, and it seams that
SERVER1 trys to connect to SERVER2 on port 1433
also I tryed to publish SQL Server on Port 1433 using an ISA Server
Installed on SERVER2, but coud not configure it to work.
any solution on configuring either SQL Servers and/or ISA Server?
.
- References:
- Problem With Replication On Port 2433
- From: shgzs33
- Problem With Replication On Port 2433
- Prev by Date: Re: Distributor Agent
- Next by Date: Re: Log Shipping Performance
- Previous by thread: Problem With Replication On Port 2433
- Next by thread: Problem Applying Schema Changes to Existing Merge Publication
- Index(es):
Relevant Pages
|