December 3, 2007 at 12:46 pm
Hello Rooms,
Transaction Replication.
I am having trouble to convince our CISCO Engineer to open the firewall on TCT/IP port 1433 for replicating two sql servers.
So far, only B location firewall TCP/IP port 1433 is opened.
SQL Server 2005 is located in A location with firewall protected.
SQL Server 2000 is located in B location with firewall protected.
Can anyone help and advise.?
Any articles that I can convince him.?
Thank you for your help.
TJ
December 3, 2007 at 12:55 pm
I'm not sure what you mean. He doesn't want to open the port between the servers so they can communicate? This is a business case. If you need replication, you need the ports opened so the servers can communicate. If you don't necessarily need replication, you might not need the ports opened.
December 3, 2007 at 1:11 pm
Hi Steve,
Before setup the database push or pull replication. I tested the TCP/IP port 1433 on dos prompt.
In sql server 2005, I ping the sql server 2000 ip address.
Ping 192.168.xx.xxx
OR telnet 192.168.xx.xxx 1433.
In sql server 2000, I ping the sql server 2005 ip address.
Ping 192.169.xx.xxx
OR Telnet 192.169.xx.xxx 1433.
Both indicated telnet 192.xxx.xx.xxx 1433. “Could not open connection on the host, on port 1433: Connect failed”
December 3, 2007 at 1:27 pm
I agree with Steve. If you need replication then the firewall ports must be opened.
If merge replication is an option for you you can replicate via http using either port 80 or 443.
About your telnet results, you said that on one location port 1433 is open but for telent to be succesful both sides need to be open. Also make sure that both instances use the default port. If either one is a amed instance it would use dynamic ports by default.
[font="Verdana"]Markus Bohse[/font]
December 3, 2007 at 3:54 pm
I am not sure what kind of hardware are you using but In the past My network admins have "tunneled" SQL server trafic for me bewtween the two offices making completly transparent the connection for SQL Server.
* Noel
December 3, 2007 at 4:41 pm
You can use ODBCPing or just connect with QA, SSMS, whatever, They'll run 1434 by default. Or you can specifically connect on that port to SalesDBServer with "SalesDBServer,1433" in the connection box.
The ports should not be open for anyone. They should be open only for specific IPs if you need the servers to communicate. A good Cisco person can set up a tunnel or even redirect the traffic to a higher port. I'd say that you need to be able to get from one server to the other on 1433 FROM THAT server and let the network guys decide how the traffic is to move securely.
December 14, 2007 at 5:03 am
1433 must be open for communcation.
On a different note, I'm trying to replicate between a SQL 2000 server and a SQL 2005 server. However, I get a message on the SQL 2000 server when I try to register the SQL 2005 server that says "To connect to this server you must use SQL Server Management Studio or SQL Server Management Objects." Is there a way around this without upgrading the SQL 2000 server? I have seen where I can download SQL Server Management Studio Express, but I don't think it will let me control replication from the SQL 2000. I'm trying to do a push merge replication from the SQL 2005 server to the SQL 2000 server. Do I really even need to do anything on the SQL 2000 server or can it all be done on the SQL 2005?
Thanks,
Steve
December 15, 2007 at 4:37 am
One short note:
If you need to setup transactional replication through firewall, push is a bit easier than pull, because push is happy with a TCP 1433 from distributor to subscriber, while pull requires access to the network share so you need to open a bunch of ports for it.
-- Erik http://blog.rollback.hu
December 15, 2007 at 8:38 am
Unless I skip that part in BOL, 1433 is not a telnet port, so telnet is going to fail....telnet is a specific application - so trying to get SQLserver to talk telnet isn't the way to go.
Don't tate that particular error as a sign that the port is not opened.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
December 16, 2007 at 4:50 am
As I experienced, you can telnet to a SQL server via its TCP port. In case there's a server waiting for connections, you'll get a blinking cursor so the server lets you in, however, there's a slight cance that you'll be able to type well-formed requests... 🙂
-- Erik http://blog.rollback.hu
December 17, 2007 at 7:49 am
Matt Miller (12/15/2007)
Unless I skip that part in BOL, 1433 is not a telnet port, so telnet is going to fail....telnet is a specific application - so trying to get SQLserver to talk telnet isn't the way to go.Don't tate that particular error as a sign that the port is not opened.
you can force telnet to use any port to test communication on that port
back in my exchange admin days i used to telnet on port 25 to test mail flow
December 17, 2007 at 7:50 am
if you are running windows 2003 you can check out the new http based replication. i forgot the exact name of it and you might need to set up IIS on both ends first to make it work
December 17, 2007 at 8:10 am
SQL Noob (12/17/2007)
Matt Miller (12/15/2007)
Unless I skip that part in BOL, 1433 is not a telnet port, so telnet is going to fail....telnet is a specific application - so trying to get SQLserver to talk telnet isn't the way to go.Don't tate that particular error as a sign that the port is not opened.
you can force telnet to use any port to test communication on that port
back in my exchange admin days i used to telnet on port 25 to test mail flow
I understand that, but you need something on ther other side to ANSWER, otherwise you get errors. I knew about the SMTP port, since I've used that before. I had not tried that with SQL before, so I got to learn something.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
December 17, 2007 at 8:19 am
We used to test HTTP at times with it to be sure it was working.
If you telnet to some port and it hangs, blinking cursor, then it's likely open and running. It's waiting for some reponse. If you get that, then try the ODBCPing utility to that port.
May 11, 2009 at 8:59 am
I am using two SQL 2005.in that using the transactional replication . I have changed the SQL 2005 communication port from 1433 to some other port. Now the replication is happening but the replication is happening using dynamic ports. Can i configure in some place to use static port for the replication.
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply