Sql Server 2000 connection problem

Sql Server 2000 connection problem

• Lynn Roth

  Im also behind a Firewall specifically WINGATE 6.1..i tried to add port to the firewall and have it redirect to my actual database server say 192.168.0.111 but nothing happens at all. any similar problem

  
  
  

• pnuruddin

  You have to run the surface area configuration wizard (Under SQL Server 2005->Configuration Tools on your start menu by default) and enable remote connections (by default they are turned off).
  
  

• Ron Linares

  Hi...

  Sorry for the late reply...

  Thanks for the advice... But still its not working...

  Yep am using SQL Server 2000 as for the version , I think its 8.0 but  I must check it... But it has been patched till SP4...

  The full error that it is displaying is :-

  "Can not access the server. Under this setting your server may not be configure to enable remote connetion ("Provider: SQL Network Interface, ,error: 26 - Error locating Server\Instatnce specified")...

   thkz......

  
  
  

• jbond100684

  Your Sql Server is Behind a Firewall, if yes add port 1433 in the exceptions. I faced this before and this solved the problem.last week happened again and i installed service pack 4.. all working fine and happy now...

  
  

• arungal

  I must have been asleep when I answered this question. I just realized you said Server 2000 (not 2005).

  Which version of 2000 are you using I believe the default for 2000 was to allow remote connections but that it is possible to disallow remote connections.

  Seeing that I don't have a SQL 2000 instance here, I can't give precise directions on how to re-enable remote connections. But that's where I would check first.

  
  
  

• Stijn Sanders

  The error indicates that the client was not able to resolve the server's TCP port.

  Beyond checking the protocols enabled on the server in the *Server* Network Utility (you want TCP or Named Pipes enabled for remote connectivity) a firewall may be another cause of the error you see.

  If firewall is blocking UDP port 1434 you have 2 options:

  (1) grant en exception to UDP port 1434 (if your security considerations allow this).

  (2) specify the SQL Server TCP port explicitly in the connection string:

  (a) Find the TCP port in the Server Network Utility. Let's say it is 1500.

  (b) specify the server in the connection string as <myServer>,<myPort>, e.g.

  targetServer,1500.

  
  
  

• jasin14

  By default, SQL Server is not configured to permit remote access (as you have seen). You can use the Client Network Utility to configure (enable) the protocols needed to expose your server instance on the LAN. Accessing it over the web is dangerous at best...

  Again, check out my blog for a comprehensive list of issues and solutions to get connected.

  hth

  
  
  

• Scuzball

  Hello

  I am facing same kind of problem....

  But no solution yet... :(

  
  
  

• Harsh_India

  What is the full error you are getting

  
  
  
• Sql Server 2000 connection problem