September 14, 2011 at 9:56 am
Hi,
I trying to connect the sql server 2000 workgroup editon on a remote server to a sql server 2005 enterprise edition and it doesn't connect.
I wrote the i p address in ssms 2005 server name..
It showing this error:---
( attached)
I checked that the remote connections on that server are ON and
named pipes,TCP are also enabled.
I try to ping the server from my server and it is pinging successfully..
P.S.-- before few days i could connect to it ( so those servers are in same domain/network )
Regards,
Sushant
Regards
Sushant Kumar
MCTS,MCP
September 15, 2011 at 7:50 am
This is linked server, have you tried connecting directly without the linked server overhead?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
September 15, 2011 at 7:53 am
@ jack ....
I connected with/without linked server,
from both, I am getting same error.
Regards,
Sushant
Regards
Sushant Kumar
MCTS,MCP
September 15, 2011 at 8:04 am
Can you ping the remote server?
Can you connect using Telnet?
If you could connect before, what has changed since you successfully connected?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
September 15, 2011 at 8:12 am
@ jack
I can ping through remote server.
Didn't try telnet though (Don't know how to execute it )
Nothing has changed from last time i connected, but yes, always it took around 10 secs to connect , i mean connection was always very slow..and now, it wait for like 40-50 secs and then throws up that error message.
Regards,
Sushant
Regards
Sushant Kumar
MCTS,MCP
September 15, 2011 at 8:23 am
To telnet open a command prompt and type in telnet [fqdn or IP] [port #]. If you connect it is accepting connections and your issue is elsewhere.
Something must have changes somewhere if connectivity was possible before and now it is not. Have you checked firewall settings to be sure all the ports necessary are still open?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
September 15, 2011 at 8:33 am
telnet 127.0.0.1 [port #]
Should hte port number be 1443 or what else?
Regards,
Sushant
Regards
Sushant Kumar
MCTS,MCP
September 15, 2011 at 8:46 am
The default port is 1433. Otherwise if it is dynamic or changed to another port you'll need to look on the SQL Server for configuration.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
September 15, 2011 at 9:18 am
@ jack
I am not able to telnet it
it says no connection to host on the port 1433
I made sure that 1433 port is sql server on that machine.
What could be the reason for successful ping but not telnet.
Thanks.
Regards,
Sushant
Regards
Sushant Kumar
MCTS,MCP
September 15, 2011 at 9:41 am
Sounds like firewall to me, but I've exhausted my expertise.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
September 15, 2011 at 9:57 am
@ jack..
I checked the firewall settings,
on the exception tab i have many buttons checked , the relevant looks like these
1) SQL 1433 port ( TCP button green)
2) sql 1443 port . ( TCP button green)
Other than that
1) I confirmed SQL Server allows remote connections.
2) I confirmed TCP/IP and Named Pipes Protocols are enabled.
3) pinging successfully.
I am also exhausted, i guess I have to handover this case to networking team now .
Thanks for your replies
Regards,
Sushant
Regards
Sushant Kumar
MCTS,MCP
September 15, 2011 at 9:58 am
Jack Corbett (9/15/2011)
Sounds like firewall to me, but I've exhausted my expertise.
+1
Can't be a browser issue, since you're not connecting to a named instance.
It must be firewall.
-- Gianluca Sartori
September 15, 2011 at 10:07 am
have you checked the SQL Server log on the remote machine. Is it listening on 1433? When SQL starts up, it will let you know where it is listening.
September 15, 2011 at 10:14 am
You could also issue this statement on the remote SQL Server (given that you connect via TCP/IP)
SELECT local_tcp_port
FROM sys.dm_exec_connections
WHERE session_id = @@SPID
-- Gianluca Sartori
September 15, 2011 at 10:21 am
Gianluca Sartori (9/15/2011)
You could also issue this statement on the remote SQL Server (given that you connect via TCP/IP)
SELECT local_tcp_port
FROM sys.dm_exec_connections
WHERE session_id = @@SPID
I ran through QA on the remote machine
Server: Msg 208, Level 16, State 1, Line 1
Invalid object name 'sys.dm_exec_connections'.
Regards,
Sushant
Regards
Sushant Kumar
MCTS,MCP
Viewing 15 posts - 1 through 15 (of 18 total)
You must be logged in to reply to this topic. Login to reply