jlexer
asked on
Problems enabling Sql Server 2000 for remote access
I cannot get an instance of SQL Server 2000 to be enabled outside of my firewall. I am only trying to connect using SSMS 2008 and telnet. I am only trying to connect with the static ip address to eliminate any potential DNS issues.
When I try to telnet:
When I attempt with SSMS, I get
I've fairly certain that it is not my firewall, as I have enabled FTP services on the same machine and have applied all the same policies for port 21 vs 1433 and 1434 (tcp and udp). I have no problems accessing the ftp server remotely, but I am still unable to connect to SQL Server. Just in case it matters, the firewall is a Watchguard XTM 510.
I have disabled all software firewalls on the server.
I have enabled remote access for SQL Server. Below is my snippet of sp_configure:
I am running 2000 SP4 EE. Below are my SERVERPROPERTY-ies:
productversion = 8.00.2151
productlevel = SP4
edition = Enterprise Edition
In Sql Server Network Utility, I have confirmed that Named Pipes, TCP/IP, and Multiprotocol are enabled. TCP/IP properties are set to 1433. Hide Server is not checked.
In Sql Server Client Network Utility, I have confirmed the same protocols are enabled and TCP/IP is at the top of the list and is also set to port 1433 in its properties.
I have run out of ideas of what to investigate next?
When I try to telnet:
telnet <ip address> 1433
it times out with a
Could not open connection to the host, on port 1433: Connect failed
When I attempt with SSMS, I get
Could not connect to <ip address>. A network-related or instance specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server Error: 10060)
I've fairly certain that it is not my firewall, as I have enabled FTP services on the same machine and have applied all the same policies for port 21 vs 1433 and 1434 (tcp and udp). I have no problems accessing the ftp server remotely, but I am still unable to connect to SQL Server. Just in case it matters, the firewall is a Watchguard XTM 510.
I have disabled all software firewalls on the server.
I have enabled remote access for SQL Server. Below is my snippet of sp_configure:
name minimum maximum config_value run_value
remote access 0 1 1 1
remote login timeout(s) 0 2147483647 20 20
remote proc trans 0 1 0 0
remote query timeout(s) 0 2147483647 600 600
I am running 2000 SP4 EE. Below are my SERVERPROPERTY-ies:
productversion = 8.00.2151
productlevel = SP4
edition = Enterprise Edition
In Sql Server Network Utility, I have confirmed that Named Pipes, TCP/IP, and Multiprotocol are enabled. TCP/IP properties are set to 1433. Hide Server is not checked.
In Sql Server Client Network Utility, I have confirmed the same protocols are enabled and TCP/IP is at the top of the list and is also set to port 1433 in its properties.
I have run out of ideas of what to investigate next?
Do you have the latest service pack for SQL 2000? I mean SP4.
Check if windows firewall is on. If so turn it off.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Why do you want close this question without resolving it...
We spent our time for possible solutions..
Regarding....."The alias name issue perhaps has provided a sufficient work-around. Before I received your responses, I found the following article on the Watchguard support pages..."
OFCOURSE YOU WILL FIND ALL ANSWERS IN THE INTERNET IF YOU SPEND SOME TIME.
We spent our time for possible solutions..
Regarding....."The alias name issue perhaps has provided a sufficient work-around. Before I received your responses, I found the following article on the Watchguard support pages..."
OFCOURSE YOU WILL FIND ALL ANSWERS IN THE INTERNET IF YOU SPEND SOME TIME.
More easy would be changing the SQL Server port to a number different that 1433 or 1434.
Are you able to ping that sql server in the command prompt?
Do you have multiple instances installed on that server?
Create an alias name for this ipaddress using Sql Server Client Network Utility. Use that name to connect to the sql server.