Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-05-04 : 08:34:58
|
warwick oke writes "I've got a tough question for you.
I configured sql server pull replication in a lab environment & it worked beautifully. The 2 server names have not been changed.
The question I have is really about SQL server communications:
(1) Does SQL server use TCPIP port 1433 for all server registration & replication communications?
(2) Does port 1433 need to be enabled for two-way communication? ( logic would say it would ).
(3) Are there limitations on which user accounts on the box are used for replication?
Our comms people swear black & blue that when I inititialise a replication manually ( by starting the job ) they dont see any traffic on port 1433. Do I have to start the job physically from the server or is using EM remotely OK?
I got to thinking that maybe SQL broadcasts on this port & if it cant "see" a broadcast from the server it replicates to/from, it wont try any further. Likewise, like WINS & DNS, are there any quirks about SQL communications that I should be aware of? Do I need to use LMHOSTS to point the SQL server to the other server? Do I need to use a full domain name for the SQL server instead of just the SQL server name?
Told you it was tough.
Any help appreciated....
Thanks, Warwick." |
|
|
|
|
|
Replication through firewalls