Wednesday, February 15, 2012

Error: Server doesnot exist or Access denied

We are host with windows 2003 server and SQL 2000 DB server. Our clients are
trying to connect to their individual databases using SQL webadmin or
Enterprise manager tool and they get the following message:
"SQL server doesnot exist or access denied.
ConnectionOpen(Connect())"
This is the message from SQL enterprise manager. The workstation is XP SP1.
Any suggestions
>> Any suggestions
Oh the usual:
1. Check to make sure that they are using the right username/password
combination.
2. Make sure the client is not behind a firewall that prevents comm
over the SQL Server port.
3. Make sure the same applies for the server.
4. Make sure that they are using the right authentication type (sql or
win).
5. Make sure that the server is configured to use the right auth mode.
6. Make sure that the server's host name appears in the list of
available server to connect to (see 2 & 3).
HTH
AM
|||Actually we found out that the SQL is not listening on any TCP/IP port but
only listening to named pipes. Any idea of how to make SQL Server listen to
any tcp/ip ports?
"AM" wrote:

> Oh the usual:
> 1. Check to make sure that they are using the right username/password
> combination.
> 2. Make sure the client is not behind a firewall that prevents comm
> over the SQL Server port.
> 3. Make sure the same applies for the server.
> 4. Make sure that they are using the right authentication type (sql or
> win).
> 5. Make sure that the server is configured to use the right auth mode.
> 6. Make sure that the server's host name appears in the list of
> available server to connect to (see 2 & 3).
> HTH
> AM
>
|||In Enterprise Manager, right click on the DB, select properties. In
ther dialog box, int he General tab, on the bottom click on Network
configuration. In the dialog box that pops up, in the general tab,
check to see if TCP/IP is listed on the box on the right. If not select
it from the box on the left and click on enable. YOu can edit the
properties to set up the port to listen on.
HTH
AM
|||You can use Server Network Utility to set the tcp port for the sql instance.
-oj
"Snehal Rana" <SnehalRana@.discussions.microsoft.com> wrote in message
news:E263310C-BB72-483D-BE16-DA854F38CB40@.microsoft.com...[vbcol=seagreen]
> Actually we found out that the SQL is not listening on any TCP/IP port but
> only listening to named pipes. Any idea of how to make SQL Server listen
> to
> any tcp/ip ports?
>
> "AM" wrote:

No comments:

Post a Comment