Can’t register remote SQL 2000 server

0 pts.
Tags:
Security
Servers
SQL Server
SQL Server 2000
We have fresh installs of XP Pro SP2 on several workstations in the same site and the same subnet done not from the image. We want to use TCP/IP to register the default instance of SQL 2000 server located behind the firewall, not in our site. Some of workstations have no problems registering the SQL box in the Enterprise Manager, but some can't, receiving an error message ".. server doesn't exist or access is denied". We've already followed all MS KB advices, disabling Windows firewall or, on contrary, enabling it with exceptions for ports 135, 445, 1433, 1434. All workstations have all available patches/SPs. We can't figure our what's the difference between the WS, what port is blocked and why does it happen not everywhere. I know that WS uses a randomly choosen port greater than 1024 for communication. What is strange however is that the port 1433 is FILTERED according to MS portqry report on WS with problems and is LISTENING on the successfull PC's. Any help will be appreciated.
ASKED: December 28, 2004  5:36 PM
UPDATED: January 3, 2005  10:15 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

First of all make sure that you don’t have any other firewall in place especially McAfee.

Try the following, from any client open a command prompt windows and type “telnet sqlserverip 1433″, if you got a blank screen, then your clients should be able to access the sql server, and probably their is a problem with authentication, try switching between SQL Authentication and Windows Authentication”, however if you got an error that telnet is unable to connect to port 1433, then there is a connection problem, it might be firewall or tcp/ip configuration problem

Discuss This Question: 7  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • BeerMaker
    Are you using named pipes or tcp/ip as the network protocol? If its IP, can you ping the machine. If so, and you cant connect its a blocked port. On one of the working machines with SQL Enterprise manager, look at the registry key: [HKLMSoftwareMicrosoftMSSQLServerClientSupersocketnetlib] and find the server name entry. Your entries will look like this: -134086648:tcp:Server1,2510 -33423352:np:Server2pipesqlquery Server1 uses tcp, Server 2 is using named pipes. Try to map a drive to the server and see if you can connect. Id recommed using TCP and making sure the client computers use TCP as the client network protocol for sending SQL requests. Please, post a reply when you fix the problem. HTH
    0 pointsBadges:
    report
  • Findit
    Hi, all! We use only TCPIP everywhere. We can ping the server from any workstations and we can't telnet the server from all workstations. However, it doesn't prevent me from successfully registering the server from some of them. There is no record for this server in the registry on WS, which are failing and its quite natural, because the name of the key is LastConnect. Thanks
    0 pointsBadges:
    report
  • Mraslan
    i just want to confirm the following with you. You *can* ping the SQL server from all workstations You *can not* telnet to port 1433 from all workstations i have some questions, do you have machines that sometimes connect and other times unable to connect to the SQL server? on the SQL server, open start menu > programs > SQL server > Server Network Utility, in there do you have the following checkbox checked? "Force protocol encryption" and "Enable Winsock proxy" open Enterprise Manager, right click on the server name node and get its properties, click on the connections tab, and check "Max concurrent user connections" make sure its set to "0" try this, try to install a test sql server on the same subnet as the clients and another one in the remote site, and try to telnet to them from the clients, and tell me the results.
    0 pointsBadges:
    report
  • Findit
    I'm sorry, I've checked again and want to correct my statement: telnet fails only on workstation which can't register remote SQL server. There are no problems registering any local SQL on this WS.
    0 pointsBadges:
    report
  • Mraslan
    No problem, just try the things i mentioned in my previous post and tell me about them
    0 pointsBadges:
    report
  • 0ct0pus
    The fact that on some machines port 1433 appears as LISTENING and to some appears FILTERED might indicate that the firewall only allows the connection from certain IP range. You might wanna check the firewall rule to allow the connection from all IP in the subnet since all clients are in one subnet. We try to sort this out from network layer first.
    0 pointsBadges:
    report
  • Findit
    I've found the difference which PC's have. When I click on Component services ==> Computers ==> My Computer ==> Default Protocols ==> Connection-oriented TCP/IP ==> Properties, successfull computers have nothing in the Port Range area and Port range assignment set to Internet range. However, unsuccessfull PC's have the Port range assignment set to Intranet range. What's strange is that I can't simply change the settings type without a manual addition of ports, like 111-40000.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following