November 25, 2002 at 2:21 pm
I'm trying to see about connecting an instance of Enterprise Manager to a remote SQL Server. I am unable to with the current setup even though the firewall on the far end has port 1433 open.
My initial thought is that EM is using RPC calls to access SQL server and they aren't going through port 1433. So do I need another port open or do I need to setup a VPN connection or...?
Any and all help appreciated. 🙂
-Brandon
Edited by - brandonh6k on 11/25/2002 2:22:45 PM
-Brandon
November 25, 2002 at 4:34 pm
I think that is it, need 1434 if you dont know the server name. Can you ping the server? Is it a named instance? Connect via Query Analyzer?
Andy
November 25, 2002 at 6:40 pm
You'll need to verify the port the remote SQL Server is listening on and makes sure it matches. Also verify both server and client are using TCP/IP as a network protocol (they should be by default). Given all that, one simple thing to check before really investigating the connection path is to make sure the SQL Server is indeed listening on 1433 (someone would need to run a netstat -an on the server locally). Every once in a while I'll see an error where SQL Server doesn't bind properly on that port and stopping and restarting the SQL Server service usually fixes that problem. These are the simple things to check out before going in-depth.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
December 3, 2002 at 9:51 am
Andy got it. Opening up 1434 on the firewall did the trick.
Thanks!
-Brandon
-Brandon
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply