Connection problem

I have 2 sql servers running on different machines. I want to manage both
servers from one machine. When I try to add the other server in the
enterprise manager it gives me the error "sql server does not exist or access
denied". I am using a valid log on user name that is set up on the server, I
have even tried using a windows username. I know that the problem has to lie
in authentication because I know the server exist. Anyone know of anything I
may be doing wrong?"Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> I have 2 sql servers running on different machines. I want to manage both
> servers from one machine. When I try to add the other server in the
> enterprise manager it gives me the error "sql server does not exist or
access
> denied". I am using a valid log on user name that is set up on the
server, I
> have even tried using a windows username. I know that the problem has to
lie
> in authentication because I know the server exist. Anyone know of
anything I
> may be doing wrong?
To rule out the server permissions issue, in other words your account has
permissions on the server itself -- try using an account that has
administrative rights on the target server and sysadmin permissions on SQL
Server.
Steve|||Ok here is what I tried. I went to the remote sql server and created a
windows user that is part of the admin group. I then went to the enterprise
manager on the remote sql server and created a user which I browsed for and
got from the windows users list. I gave that login SA rights on the sql
server. I then went back to the other server and tried to register the
remote sql server using sql authentication. I used the username and password
that I had created and I still get the same error message. Any ideas?
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Another thing I forgot to mention. I also tried to register the other server
on the remote server (the reverse of what I have been trying). When I go to
register the server I see seven or so other servers that we have here at
work; however when I have been doing it on the other computer I only see one
server (that being the remote sql server). I am wondering what may cause
this and if it might have something to do with the login issue.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Other things I have tried:
Pinging the remote sql server - works fine
telnet to port 1433 on the remote server - does NOT work
there is not a firewall between the two machines.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Problem Solved: I was really simple actually, all I had to do was go to the
properties of the remote sql server and configure the network configuration
to enable tcp/ip using port 1433
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>sqlsql

connection problem

I am a newbie to SQL server. I have installed SQL server on my PC. I have created a local server on my machine. When i go to the SQL server wizard to register my server and it gives me the option to connect i am getting the message: SQL server does not exist or access denied. Now i was told that this may be due to my firewall. I have turned these off..and am still getting the message.
Please help
JohnHi John,
What was the authentication mode that you selected while installing the SQL
Server ?
If you have created in Mixed mode, What is the SA Password ?
Is it blank ?
Did you create a named instance or is it the default instance ?
If you have created a named instance, what is the name that you
have assigned to this new instance ?
Just a step by step info, in case you have missed one.
1. "Select a Server" Step
If your instllation is the default installation, then
type your computer name for the "Available Servers" and click on
Add.
If your installation is the Named instance, then
type the server name as "Computername\InstanceName" for the
"Available Servers" and click on ADD.
2. "Select an Authentication Mode" step
If you have selected Mixed Mode authentication, then select
"The SQL Server Login information that was assigned to me by
the system administrator"
3. If you select SQL Server login, you get this additional step "Select
Connection Option"
select first option "Login Automatically using my SQL Server account
information"
Login Name : SA
Password : <The password that you have set> or leave it
blank, if you had set it blank.
4. "Select SQL Server Group" step
select "Add the SQL Server(s) to an existing SQL Server Group".
5. Click on Finish, to get connected to the SQL Server.
With this simple steps you should be able to register the SQL Server in
Enterprise Manager.
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.

connection problem

I am a newbie to SQL server. I have installed SQL server on my PC. I have created a local server on my machine. When i go to the SQL server wizard to register my server and it gives me the option to connect i am getting the message: SQL server does not ex
ist or access denied. Now i was told that this may be due to my firewall. I have turned these off..and am still getting the message.
Please help?
John
Hi John,
What was the authentication mode that you selected while installing the SQL
Server ?
If you have created in Mixed mode, What is the SA Password ?
Is it blank ?
Did you create a named instance or is it the default instance ?
If you have created a named instance, what is the name that you
have assigned to this new instance ?
Just a step by step info, in case you have missed one.
1. "Select a Server" Step
If your instllation is the default installation, then
type your computer name for the "Available Servers" and click on
Add.
If your installation is the Named instance, then
type the server name as "Computername\InstanceName" for the
"Available Servers" and click on ADD.
2. "Select an Authentication Mode" step
If you have selected Mixed Mode authentication, then select
"The SQL Server Login information that was assigned to me by
the system administrator"
3. If you select SQL Server login, you get this additional step "Select
Connection Option"
select first option "Login Automatically using my SQL Server account
information"
Login Name : SA
Password : <The password that you have set> or leave it
blank, if you had set it blank.
4. "Select SQL Server Group" step
select "Add the SQL Server(s) to an existing SQL Server Group".
5. Click on Finish, to get connected to the SQL Server.
With this simple steps you should be able to register the SQL Server in
Enterprise Manager.
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.

Connection problem

I have 2 sql servers running on different machines. I want to manage both
servers from one machine. When I try to add the other server in the
enterprise manager it gives me the error "sql server does not exist or access
denied". I am using a valid log on user name that is set up on the server, I
have even tried using a windows username. I know that the problem has to lie
in authentication because I know the server exist. Anyone know of anything I
may be doing wrong?
"Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> I have 2 sql servers running on different machines. I want to manage both
> servers from one machine. When I try to add the other server in the
> enterprise manager it gives me the error "sql server does not exist or
access
> denied". I am using a valid log on user name that is set up on the
server, I
> have even tried using a windows username. I know that the problem has to
lie
> in authentication because I know the server exist. Anyone know of
anything I
> may be doing wrong?
To rule out the server permissions issue, in other words your account has
permissions on the server itself -- try using an account that has
administrative rights on the target server and sysadmin permissions on SQL
Server.
Steve
|||Ok here is what I tried. I went to the remote sql server and created a
windows user that is part of the admin group. I then went to the enterprise
manager on the remote sql server and created a user which I browsed for and
got from the windows users list. I gave that login SA rights on the sql
server. I then went back to the other server and tried to register the
remote sql server using sql authentication. I used the username and password
that I had created and I still get the same error message. Any ideas?
"Steve Thompson" wrote:

> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Another thing I forgot to mention. I also tried to register the other server
on the remote server (the reverse of what I have been trying). When I go to
register the server I see seven or so other servers that we have here at
work; however when I have been doing it on the other computer I only see one
server (that being the remote sql server). I am wondering what may cause
this and if it might have something to do with the login issue.
"Steve Thompson" wrote:

> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Other things I have tried:
Pinging the remote sql server - works fine
telnet to port 1433 on the remote server - does NOT work
there is not a firewall between the two machines.
"Steve Thompson" wrote:

> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Problem Solved: I was really simple actually, all I had to do was go to the
properties of the remote sql server and configure the network configuration
to enable tcp/ip using port 1433
"Steve Thompson" wrote:

> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
sqlsql

connection problem

I am a newbie to SQL server. I have installed SQL server on my PC. I have cr
eated a local server on my machine. When i go to the SQL server wizard to re
gister my server and it gives me the option to connect i am getting the mess
age: SQL server does not ex
ist or access denied. Now i was told that this may be due to my firewall. I
have turned these off..and am still getting the message.
Please help?
JohnHi John,
What was the authentication mode that you selected while installing the SQL
Server ?
If you have created in Mixed mode, What is the SA Password ?
Is it blank ?
Did you create a named instance or is it the default instance ?
If you have created a named instance, what is the name that you
have assigned to this new instance ?
Just a step by step info, in case you have missed one.
1. "Select a Server" Step
If your instllation is the default installation, then
type your computer name for the "Available Servers" and click on
Add.
If your installation is the Named instance, then
type the server name as "Computername\InstanceName" for the
"Available Servers" and click on ADD.
2. "Select an Authentication Mode" step
If you have selected Mixed Mode authentication, then select
"The SQL Server Login information that was assigned to me by
the system administrator"
3. If you select SQL Server login, you get this additional step "Select
Connection Option"
select first option "Login Automatically using my SQL Server account
information"
Login Name : SA
Password : <The password that you have set> or leave it
blank, if you had set it blank.
4. "Select SQL Server Group" step
select "Add the SQL Server(s) to an existing SQL Server Group".
5. Click on Finish, to get connected to the SQL Server.
With this simple steps you should be able to register the SQL Server in
Enterprise Manager.
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.

Connection pool leak in production machine (in other machine it runs well)

Hi to everyone,

I'm facing a problem that drives me crazy. I've a web application that has the following problem. When I test the application on my developement machine all runs fine, but when I put into production server there is a problem in connection pooling. Look at the following image, the blue line is the number of connection in the pool and the violet line is the number of connection reclaimed. From the image it is clear that connection are returned on the pool only in block, maybe when the garbage collection pass and reclaim the object. The strange thing is that on my developement machine all is good, and also I'm using Enterprise Library and the connection are managed internally.-

Thanks to everyone for any help.

How do you access DB? If you use some IDataReader, though they will be GC sooner or later, still remember to close them as soon as they are not used~|||

My big mistake is to misunderstood the meaning of the numberOfReclaimedConnection counter, that indicates the number of connections that are reclaimed by a garbage collector and indicate a leak. For some reason in my developement machine garbage collector does a more aggressive job in reclaiming connection while in the production server, maybe due to the large amount of ram garbage collection happens less frequently.

You're right about the datareder, one of the function in Data Access Layer forget to close a datareader in some situation, and it's called from a webModule that runs at every request for the page. The result is awful, when a lot of user access to the site the pool often become empty. I enclose the datareader in using block and all goes well again. From now on I will use perfmon.exe at every run of the site.

Alk.

Connection over a router!

I am using SQL 2000 and I need to connect to it through an application
that uses ADO.
- The server is on a machine that is behind a router, the router is
configured to
map port 1433 to the same port number on the machine hosting SQL server.
- And the actual network configuration shown only TCP/IP as the
communication
protocol used.
So far I did not have any luck with the connection although I am not a
network
specialist.
I was told that the router may have the DMZ configured and that may be the
reason
for connection failure.
Any ideas?
Cheers!"Enver Buzoku" <ebuzoku@.hotmail.com> wrote in message
news:uR3%23C9wwDHA.1736@.TK2MSFTNGP09.phx.gbl...
> I am using SQL 2000 and I need to connect to it through an application
> that uses ADO.
> - The server is on a machine that is behind a router, the router is
> configured to
> map port 1433 to the same port number on the machine hosting SQL server.
> - And the actual network configuration shown only TCP/IP as the
> communication
> protocol used.
> So far I did not have any luck with the connection although I am not a
> network
> specialist.
> I was told that the router may have the DMZ configured and that may be the
> reason
> for connection failure.
> Any ideas?
1) Test TCP/IP connectivity.
Use a port sniffer to determine if you can connect over TCP/IP to port 1433
on the computer.
Telnet is a poor-man's port sniffer. Open a command prompt and type
telnet 123.123.123.123 1433
Use a numeric IP address to defer name resolution issues.
If you get a blank black screen, then you have succeeded in connecting over
TCP/IP to the target machine (then just close the window, there's nothing
you can do with this connection).
If you get an error message, then you've got a problem.
2) Test SQL connectivity over TCP/IP.
Make sure you are using the TCP/IP net library to connect. Methods for this
depends a little on your environemnt and whether you have the SQL tools
installed, but you can always create a new ODBC connection from the control
panel to test this. Just be sure to specify TCP/IP in the "Client
Configuration" section.
Davidsqlsql

Connection Manager - variables

hello all,

I have a scenario where I like to reuse one project from one machine to another machine.

- Server name is variable.

- database name is variable

- table name is fixed.

How do I specify a variable name for "server name" and "database name" ?

Are you taking about Server/Database name of your Data Sources?

For that you can use package configurations storing those names in a table, xml file, etc

Rafael Salas

|||

You can select the connection manager then go to the properties pane to set the expression for these properties. In your case, you'd want to change the server name and initialcatalog properties, which are very common. You could set these to a variable of course like in your requirement and then additionally later use a configuration file to externalize this all.

Also, the same type of concepts in this video would help you as well: http://www.jumpstarttv.com/Media.aspx?vid=34

-- Brian Knight

Connection issue with Management Console

When i try to connect to Integration Services on a SQL 2005 Machine, it Gives me a Class not registeed.

But i can connect to SQL 2008 Integration Services without a issue.

I tried Restarting the 2008 machine and Also Reinstalling the SSIS Piece and also Reinstalled SQL 2008, but nothing seems to Help.

Could you provide more details? Do you have SQL 2005 and SQL 2008 installed on the same machine?

Thanks,

Bob

|||

No, I dont

I Just Have SQL 2008 July CTP installed on a Windows Xp SP2 MAchine and I try to connect to another SQL Server 2005 Server (Integration Services)

I am Even Having Trouble opening the Maintenance Plan in SQL 2008.

|||

Hi there,

In the July CTP you can not connect to a 2005 SSIS service through 2008 Management Studio. To manage a 2005 SSIS service, you'll need to use the 2005 version of SSMS.

We're currently investigating ways to resolve this issue, but it's unclear whether we'll be able to solve this for the 2008 release.

~Matt

connection issue from our developer

Hi,
SQL 2005 EE is installed on W2k3 box and firewall is off in this server.
From my client machine, my window account and that developer window account
all can login into this server with ODBC, sql client, telent to 1433 or VS
connection. But, this developer can't login to SQL server from him machine
with any appliction. He is in the same domain as server and my machine. I
don't know what's the reason to cause this issue now.
Please advise. Thank you.
Lynn
Best Regards,
Lynn
What is the exact error message and error number he gets
when he tries to log into SQL Server?
-Sue
On Thu, 22 Mar 2007 10:33:45 -0700, Lynn
<Lynn@.discussions.microsoft.com> wrote:

>Hi,
>SQL 2005 EE is installed on W2k3 box and firewall is off in this server.
>From my client machine, my window account and that developer window account
>all can login into this server with ODBC, sql client, telent to 1433 or VS
>connection. But, this developer can't login to SQL server from him machine
>with any appliction. He is in the same domain as server and my machine. I
>don't know what's the reason to cause this issue now.
>Please advise. Thank you.
>Lynn
|||We only enable Shared Memory and TCP/IP protocal in server side. And, those
are the error they are getting.
osql -- SQL server doesn't exist or access denied
Query Analyzer -- General network error. Check your network documentation
VS 2005 -- (without specifing TCP protocal in connection) A connection was
succssfully established with the server, but then an error occured during the
pre-login handshake. When connecting ....(provider: Named Pipes provider,
error: 0 - No process is on the ther end of the pipe)
VS 2005 -- (specify TCP protocal in connection) An error has occurred while
establishing a connection to the server. When connecting to SQL server 2005,
this failure may be caused by the fact that under the default settings ...
(provider: TCP provider: 0 -- A connection attempt failed because the
connected party didn't not properly respond after a period of tiem, or
established connection failed because connected host has failed to respond.)
Again, this developer is able to login by using my machine with his WIN
account.
After I enable Named Pipes in server. This developer is able to connect to
server on his machine by using Named Pipe.
Firewall is off in the server, so I can't think of the issue for TCP
connection on developer's machine.
Please advise. Thank you.
Best Regards,
Lynn
"Sue Hoegemeier" wrote:

> What is the exact error message and error number he gets
> when he tries to log into SQL Server?
> -Sue
> On Thu, 22 Mar 2007 10:33:45 -0700, Lynn
> <Lynn@.discussions.microsoft.com> wrote:
>
>
|||Check the following article in Books Online:
http://msdn2.microsoft.com/en-us/library/ms175496.aspx
-Sue
On Fri, 23 Mar 2007 09:15:08 -0700, Lynn
<Lynn@.discussions.microsoft.com> wrote:

>We only enable Shared Memory and TCP/IP protocal in server side. And, those
>are the error they are getting.
>osql -- SQL server doesn't exist or access denied
>Query Analyzer -- General network error. Check your network documentation
>VS 2005 -- (without specifing TCP protocal in connection) A connection was
>succssfully established with the server, but then an error occured during the
>pre-login handshake. When connecting ....(provider: Named Pipes provider,
>error: 0 - No process is on the ther end of the pipe)
>VS 2005 -- (specify TCP protocal in connection) An error has occurred while
>establishing a connection to the server. When connecting to SQL server 2005,
>this failure may be caused by the fact that under the default settings ...
>(provider: TCP provider: 0 -- A connection attempt failed because the
>connected party didn't not properly respond after a period of tiem, or
>established connection failed because connected host has failed to respond.)
>Again, this developer is able to login by using my machine with his WIN
>account.
>After I enable Named Pipes in server. This developer is able to connect to
>server on his machine by using Named Pipe.
>Firewall is off in the server, so I can't think of the issue for TCP
>connection on developer's machine.
>Please advise. Thank you.
|||Sue,
The developer's client protocol order is TCP and NP. We didn't enable Named
Pipe in server at the beginning, that's why the first message is NP message
due to client will try to connect in the protocol order in the client. As I
menetioned, after I turn on Named Pipes in server, user's machine is able to
connect to server. But, the issue our developers had is that they couldn't
connect with TCP protocol from their machine. (I can connect by TCP protocol
from my machine. The developer login to my machine and his win account can
connect to the server as well). His machine is able to connect to our SQL
2000 with TCP protocol, but just can't connect to 2005 with TCP protocol. I
was thinging is firewall in server to caused this issue, but firewall didn't
enable in the server at all. So, I don't know what cause the issue.
Please advise.
Best Regards,
Lynn
"Sue Hoegemeier" wrote:

> Check the following article in Books Online:
> http://msdn2.microsoft.com/en-us/library/ms175496.aspx
> -Sue
> On Fri, 23 Mar 2007 09:15:08 -0700, Lynn
> <Lynn@.discussions.microsoft.com> wrote:
>
>
|||When you get symptoms like this where it only affects the
user on a particular PC then you need to look at that PC.
You'd probably start by testing basic connectivity to the
server from the PC: Can the user ping the server by name,
can the user ping the server by IP, what network related
issues are found in the Event logs on the PC, can the user
connect to the server using sqlcmd, etc. Also, have you
tried logging in from that users PC?
If you find that the issue is comes up only with Management
Studio, have the user increase the connect timeout in SSMS:
When logging on, click on the options button in the Connect
to Server window and increase the connection timeout to
something greater than the 15 second default.
It would also be worth checking the users MDAC installation
using the component checker. You can download this from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
You may also want to look at applying the latest SQL Server
service pack to the client on that PC having problems.
-Sue
On Thu, 29 Mar 2007 15:38:05 -0700, Lynn
<Lynn@.discussions.microsoft.com> wrote:

>Sue,
>The developer's client protocol order is TCP and NP. We didn't enable Named
>Pipe in server at the beginning, that's why the first message is NP message
>due to client will try to connect in the protocol order in the client. As I
>menetioned, after I turn on Named Pipes in server, user's machine is able to
>connect to server. But, the issue our developers had is that they couldn't
>connect with TCP protocol from their machine. (I can connect by TCP protocol
>from my machine. The developer login to my machine and his win account can
>connect to the server as well). His machine is able to connect to our SQL
>2000 with TCP protocol, but just can't connect to 2005 with TCP protocol. I
>was thinging is firewall in server to caused this issue, but firewall didn't
>enable in the server at all. So, I don't know what cause the issue.
>Please advise.
|||Sue,
Thank you again. Definitely, we already checked the network connect from
those developers machine. The connection issue happens to all related
developers. The developers were able to ping the server by name and IP from
their machine. But, the issue only happened on connecting to SQL 2005 with
TCP protocol. We tested through ODBC (with TCP/IP), osql, telnet to 1433
port, VS, but all connection were failed.
One developer already reinstall SQL 2005 client, but the problem is still
resisted. Will ask them to update to sp2 and go from there.
Best Regards,
Lynn
"Sue Hoegemeier" wrote:

> When you get symptoms like this where it only affects the
> user on a particular PC then you need to look at that PC.
> You'd probably start by testing basic connectivity to the
> server from the PC: Can the user ping the server by name,
> can the user ping the server by IP, what network related
> issues are found in the Event logs on the PC, can the user
> connect to the server using sqlcmd, etc. Also, have you
> tried logging in from that users PC?
> If you find that the issue is comes up only with Management
> Studio, have the user increase the connect timeout in SSMS:
> When logging on, click on the options button in the Connect
> to Server window and increase the connection timeout to
> something greater than the 15 second default.
> It would also be worth checking the users MDAC installation
> using the component checker. You can download this from:
> http://msdn2.microsoft.com/en-us/data/aa937730.aspx
> You may also want to look at applying the latest SQL Server
> service pack to the client on that PC having problems.
> -Sue

Connection issue across network

I have about 30 machines that I currently manage. I should also say, I just
took over this position as Senior DBA. One machine is a Windows 2003 Quad
Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
is the problem, I can not connect to this box from Enterprise Manager from my
desktop. If I Remote Admin into the box everything works fine. If I try to
register the server with any authenication method it doesnt work. I have
tried my personal account, domain accounts, SA, other admin accounts and
they all come back with Server does not exist or access denied. If I log in
locally or via RA everything is fine. Other admins can access this box
remotely and we all have the same security settings. All of the other
servers register fine.
I reviewed the Windows event log and auditing show that SQL has accepted my
authenication as trusted. SQL is using the standard TCP port 1433.
Any ideas?
Thanks,
Raymond S Laubert
MCITP:Adminstration, MCDBA, MCSE, MCT
Raymond Laubert
MCSE, MCDBA, MCT
So you can connect on the server (via TA session) but not from a client.
Consider that the client needs to be permitted to see the server ports and the server ports must be visible outside of the box. Here are a few things to check:
a.. Is the SQL Server Browser service running on the server?
b.. Are the external protocols enabled? (use SQL Server Surface Area Config tool)
c.. On the client, is the firewall configured to permit access to the ports?
d.. Are you trying to connect to the ports or are you letting the DNS server resolve the server instance?
e.. How are you trying to connect to the instance? In code? (Let's see the ConnectionString)
f.. Does the server show up in the list of visible servers in Server Explorer (Visual Studio)?
g.. Is the little yellow wire connected to the back of the server and does it lead (eventually) to the client? ;)
Check out Chapter 9 of my book... it's written for you (personally)... ;)
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4562BC@.microsoft.com...
>I have about 30 machines that I currently manage. I should also say, I just
> took over this position as Senior DBA. One machine is a Windows 2003 Quad
> Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
> SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
> is the problem, I can not connect to this box from Enterprise Manager from my
> desktop. If I Remote Admin into the box everything works fine. If I try to
> register the server with any authenication method it doesnt work. I have
> tried my personal account, domain accounts, SA, other admin accounts and
> they all come back with Server does not exist or access denied. If I log in
> locally or via RA everything is fine. Other admins can access this box
> remotely and we all have the same security settings. All of the other
> servers register fine.
> I reviewed the Windows event log and auditing show that SQL has accepted my
> authenication as trusted. SQL is using the standard TCP port 1433.
> Any ideas?
> Thanks,
> Raymond S Laubert
> MCITP:Adminstration, MCDBA, MCSE, MCT
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
|||Well, lets see...
I can connect to all the other servers via Enterprise Manager, so network
issues are taken care of.
I can connect to this server via Remote Admin and Terminal Server so
Security issues are taken care of.
Other DBAs and support personnel can connect to the server via Enterprise
Manager so configuration issues are taken care of.
Hmmm... I don't have a yellow wire... maybe that is the issue... oh
wait... mine is blue... yep it's connected as well.
Remember, I can connect to the other 29 servers via Enterprise Manager, this
is the only one I can not connect to. Other DBAs can connect to this server
as well as the other 29. We are all in the same security groups. I can ping
the server by address and name, so network is good.
I try not to put easy stuff on the board, but this one has me stumped.
Oh send me a copy of your book and I will proof read it for you, free of
charge of course. Maybe even promote it in the SQL Classes I teach.
Raymond Laubert
MCSE, MCDBA, MCT
"William (Bill) Vaughn" wrote:
[vbcol=seagreen]
> So you can connect on the server (via TA session) but not from a client.
> Consider that the client needs to be permitted to see the server ports and the server ports must be visible outside of the box. Here are a few things to check:
> a.. Is the SQL Server Browser service running on the server?
> b.. Are the external protocols enabled? (use SQL Server Surface Area Config tool)
> c.. On the client, is the firewall configured to permit access to the ports?
> d.. Are you trying to connect to the ports or are you letting the DNS server resolve the server instance?
> e.. How are you trying to connect to the instance? In code? (Let's see the ConnectionString)
> f.. Does the server show up in the list of visible servers in Server Explorer (Visual Studio)?
> g.. Is the little yellow wire connected to the back of the server and does it lead (eventually) to the client? ;)
> Check out Chapter 9 of my book... it's written for you (personally)... ;)
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4562BC@.microsoft.com...
|||Send me your snail-mail address and I will...
Have you tried ODBC Ping?
Is the SqlBrowser service started?
Has the SQL Server been configured to expose the external protocols? It
sounds like it, but I would double-check. Are you addressing it via DNS
address or by IP? Again, seeing the connectstring would help.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message
news:46BC5BDF-6A4F-4817-88E1-29A8F83E4FB8@.microsoft.com...[vbcol=seagreen]
> Well, lets see...
> I can connect to all the other servers via Enterprise Manager, so network
> issues are taken care of.
> I can connect to this server via Remote Admin and Terminal Server so
> Security issues are taken care of.
> Other DBAs and support personnel can connect to the server via Enterprise
> Manager so configuration issues are taken care of.
> Hmmm... I don't have a yellow wire... maybe that is the issue... oh
> wait... mine is blue... yep it's connected as well.
> Remember, I can connect to the other 29 servers via Enterprise Manager,
> this
> is the only one I can not connect to. Other DBAs can connect to this
> server
> as well as the other 29. We are all in the same security groups. I can
> ping
> the server by address and name, so network is good.
> I try not to put easy stuff on the board, but this one has me stumped.
> Oh send me a copy of your book and I will proof read it for you, free of
> charge of course. Maybe even promote it in the SQL Classes I teach.
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
>
> "William (Bill) Vaughn" wrote:

Connection issue across network

I have about 30 machines that I currently manage. I should also say, I just
took over this position as Senior DBA. One machine is a Windows 2003 Quad
Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
is the problem, I can not connect to this box from Enterprise Manager from m
y
desktop. If I Remote Admin into the box everything works fine. If I try to
register the server with any authenication method it doesnt work. I have
tried my personal account, domain accounts, SA, other admin accounts and
they all come back with Server does not exist or access denied. If I log in
locally or via RA everything is fine. Other admins can access this box
remotely and we all have the same security settings. All of the other
servers register fine.
I reviewed the Windows event log and auditing show that SQL has accepted my
authenication as trusted. SQL is using the standard TCP port 1433.
Any ideas?
Thanks,
Raymond S Laubert
MCITP:Adminstration, MCDBA, MCSE, MCT
--
Raymond Laubert
MCSE, MCDBA, MCTSo you can connect on the server (via TA session) but not from a client.
Consider that the client needs to be permitted to see the server ports and t
he server ports must be visible outside of the box. Here are a few things to
check:
a.. Is the SQL Server Browser service running on the server?
b.. Are the external protocols enabled? (use SQL Server Surface Area Config
tool)
c.. On the client, is the firewall configured to permit access to the ports?
d.. Are you trying to connect to the ports or are you letting the DNS server
resolve the server instance?
e.. How are you trying to connect to the instance? In code? (Let's see the C
onnectionString)
f.. Does the server show up in the list of visible servers in Server Explore
r (Visual Studio)?
g.. Is the little yellow wire connected to the back of the server and does i
t lead (eventually) to the client? ;)
Check out Chapter 9 of my book... it's written for you (personally)... ;)
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4
562BC@.microsoft.com...
>I have about 30 machines that I currently manage. I should also say, I jus
t
> took over this position as Senior DBA. One machine is a Windows 2003 Quad
> Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in t
he
> SQL Admin group and SQL is set for both SQL and WIndows authenication. Her
e
> is the problem, I can not connect to this box from Enterprise Manager from
my
> desktop. If I Remote Admin into the box everything works fine. If I try
to
> register the server with any authenication method it doesnt work. I have
> tried my personal account, domain accounts, SA, other admin accounts and
> they all come back with Server does not exist or access denied. If I log
in
> locally or via RA everything is fine. Other admins can access this box
> remotely and we all have the same security settings. All of the other
> servers register fine.
> I reviewed the Windows event log and auditing show that SQL has accepted m
y
> authenication as trusted. SQL is using the standard TCP port 1433.
>
> Any ideas?
>
> Thanks,
>
> Raymond S Laubert
> MCITP:Adminstration, MCDBA, MCSE, MCT
> --
> Raymond Laubert
> MCSE, MCDBA, MCT|||Well, lets see...
I can connect to all the other servers via Enterprise Manager, so network
issues are taken care of.
I can connect to this server via Remote Admin and Terminal Server so
Security issues are taken care of.
Other DBAs and support personnel can connect to the server via Enterprise
Manager so configuration issues are taken care of.
Hmmm... I don't have a yellow wire... maybe that is the issue... oh
wait... mine is blue... yep it's connected as well.
Remember, I can connect to the other 29 servers via Enterprise Manager, this
is the only one I can not connect to. Other DBAs can connect to this server
as well as the other 29. We are all in the same security groups. I can pin
g
the server by address and name, so network is good.
I try not to put easy stuff on the board, but this one has me stumped.
Oh send me a copy of your book and I will proof read it for you, free of
charge of course. Maybe even promote it in the SQL Classes I teach.
--
Raymond Laubert
MCSE, MCDBA, MCT
"William (Bill) Vaughn" wrote:
[vbcol=seagreen]
> So you can connect on the server (via TA session) but not from a client.
> Consider that the client needs to be permitted to see the server ports and
the server ports must be visible outside of the box. Here are a few things
to check:
> a.. Is the SQL Server Browser service running on the server?
> b.. Are the external protocols enabled? (use SQL Server Surface Area Con
fig tool)
> c.. On the client, is the firewall configured to permit access to the po
rts?
> d.. Are you trying to connect to the ports or are you letting the DNS se
rver resolve the server instance?
> e.. How are you trying to connect to the instance? In code? (Let's see t
he ConnectionString)
> f.. Does the server show up in the list of visible servers in Server Exp
lorer (Visual Studio)?
> g.. Is the little yellow wire connected to the back of the server and do
es it lead (eventually) to the client? ;)
> Check out Chapter 9 of my book... it's written for you (personally)... ;)
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89
-488A-9AFB-B44A6B4562BC@.microsoft.com...|||Send me your snail-mail address and I will...
Have you tried ODBC Ping?
Is the SqlBrowser service started?
Has the SQL Server been configured to expose the external protocols? It
sounds like it, but I would double-check. Are you addressing it via DNS
address or by IP? Again, seeing the connectstring would help.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message
news:46BC5BDF-6A4F-4817-88E1-29A8F83E4FB8@.microsoft.com...[vbcol=seagreen]
> Well, lets see...
> I can connect to all the other servers via Enterprise Manager, so network
> issues are taken care of.
> I can connect to this server via Remote Admin and Terminal Server so
> Security issues are taken care of.
> Other DBAs and support personnel can connect to the server via Enterprise
> Manager so configuration issues are taken care of.
> Hmmm... I don't have a yellow wire... maybe that is the issue... oh
> wait... mine is blue... yep it's connected as well.
> Remember, I can connect to the other 29 servers via Enterprise Manager,
> this
> is the only one I can not connect to. Other DBAs can connect to this
> server
> as well as the other 29. We are all in the same security groups. I can
> ping
> the server by address and name, so network is good.
> I try not to put easy stuff on the board, but this one has me stumped.
> Oh send me a copy of your book and I will proof read it for you, free of
> charge of course. Maybe even promote it in the SQL Classes I teach.
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
>
> "William (Bill) Vaughn" wrote:
>

Connection issue - Even Admin in the Server Machine

I am having administrative previlages in the SQL Server Machine, but I am
not able to connect to the SQL Server instance. Can you please help. I am
using windows authendication.
Thanks...SafeerI tried telnet ipaddress 1433, its not connecting thru the port.
I am connected to the server directly and then checked the port using server
utility and its 1433.
"Safeer" <safeerm@.gmail.com> wrote in message
news:e1jmNjrVHHA.4028@.TK2MSFTNGP04.phx.gbl...
> I am having administrative previlages in the SQL Server Machine, but I am
> not able to connect to the SQL Server instance. Can you please help. I am
> using windows authendication.
> Thanks...Safeer
>|||I tried telnet ipaddress 1433, its not connecting thru the port.
I am connected to the server directly and then checked the port using server
utility and its 1433.
"Safeer" <safeerm@.gmail.com> wrote in message
news:e1jmNjrVHHA.4028@.TK2MSFTNGP04.phx.gbl...
> I am having administrative previlages in the SQL Server Machine, but I am
> not able to connect to the SQL Server instance. Can you please help. I am
> using windows authendication.
> Thanks...Safeer
>|||We need more info.
- What version and edition of SQL Server are you using?
- What version of the Windows are you using?
It sounds like you are connecting from a client on another computer. If you
are using SQL Server 2005, use the Surface Area Configuration tool to
confirm that your SQL Server instance is listening for remote connections.
Also, a firewall could be blocking 1433. This is common with Windows XP
service pack 2.
If SQL Server is running on Vista, you have other issues.
For SQL Server 2005, there is a short tutorial that will help. See
http://msdn2.microsoft.com/en-us/library/ms345318.aspx
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Safeer" <safeerm@.gmail.com> wrote in message
news:eu1sb1rVHHA.1016@.TK2MSFTNGP04.phx.gbl...
>I tried telnet ipaddress 1433, its not connecting thru the port.
> I am connected to the server directly and then checked the port using
> server
> utility and its 1433.
>
> "Safeer" <safeerm@.gmail.com> wrote in message
> news:e1jmNjrVHHA.4028@.TK2MSFTNGP04.phx.gbl...
>|||Hi,
Windows: - Windows NT 5.2 (Build 3790: Service Pack 1)
SQL:- Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Standard Edition
My workstation is Windows 2000. I am connecting to the server using MSTSC.
My sql server log shows the following.
"SQL server listening on Shared Memory, Named Pipes."
Actually TCP/IP/1433 is enabled in the server.
& I am not able to telnet the machine with port 1433 from the server itself.
NB: No one is using this machine now and I need to setup and install service
packs. Its a new box with installed SQL 2K and nobody know the SA password.
Thanks...Safeer
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:08EB12C9-D906-4977-A40E-0F050C837E1E@.microsoft.com...
> We need more info.
> - What version and edition of SQL Server are you using?
> - What version of the Windows are you using?
> It sounds like you are connecting from a client on another computer. If
you
> are using SQL Server 2005, use the Surface Area Configuration tool to
> confirm that your SQL Server instance is listening for remote connections.
> Also, a firewall could be blocking 1433. This is common with Windows XP
> service pack 2.
> If SQL Server is running on Vista, you have other issues.
> For SQL Server 2005, there is a short tutorial that will help. See
> http://msdn2.microsoft.com/en-us/library/ms345318.aspx
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Safeer" <safeerm@.gmail.com> wrote in message
> news:eu1sb1rVHHA.1016@.TK2MSFTNGP04.phx.gbl...
am[vbcol=seagreen]
am[vbcol=seagreen]
>|||It looks like your SQL Server is listening on shared memory (which is a
local pipe) and named pipes, but is not listening on TCP/IP. So if you want
to connect using TCP/IP and port 1433, you will have to enable TCP/IP and
restart SQL Server. You use the Server Network Utility for that.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Safeer" <safeerm@.gmail.com> wrote in message
news:uCxeUt5VHHA.868@.TK2MSFTNGP05.phx.gbl...
> Hi,
> Windows: - Windows NT 5.2 (Build 3790: Service Pack 1)
> SQL:- Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Standard Edition
> My workstation is Windows 2000. I am connecting to the server using MSTSC.
> My sql server log shows the following.
> "SQL server listening on Shared Memory, Named Pipes."
> Actually TCP/IP/1433 is enabled in the server.
> & I am not able to telnet the machine with port 1433 from the server
> itself.
> NB: No one is using this machine now and I need to setup and install
> service
> packs. Its a new box with installed SQL 2K and nobody know the SA
> password.
> Thanks...Safeer
>
> "Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
> news:08EB12C9-D906-4977-A40E-0F050C837E1E@.microsoft.com...
> you
> rights.
> am
> am
>|||Hi Rick,
I've already did that. Now I did it again and restarted the server. In the
Server Netwrok Utility, its showing tcp/ip. But the log is not showing
TCP/IP.
Thanks...Safeer
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:53642094-FE1C-4BFB-85BF-E114587DDB0F@.microsoft.com...
> It looks like your SQL Server is listening on shared memory (which is a
> local pipe) and named pipes, but is not listening on TCP/IP. So if you
want
> to connect using TCP/IP and port 1433, you will have to enable TCP/IP and
> restart SQL Server. You use the Server Network Utility for that.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Safeer" <safeerm@.gmail.com> wrote in message
> news:uCxeUt5VHHA.868@.TK2MSFTNGP05.phx.gbl...
Edition[vbcol=seagreen]
MSTSC.[vbcol=seagreen]
message[vbcol=seagreen]
I[vbcol=seagreen]
I[vbcol=seagreen]
>|||Is the SQL Server Browser service started?
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Safeer" <safeerm@.gmail.com> wrote in message
news:e%23n1O5eWHHA.4668@.TK2MSFTNGP04.phx.gbl...
> Hi Rick,
> I've already did that. Now I did it again and restarted the server. In the
> Server Netwrok Utility, its showing tcp/ip. But the log is not showing
> TCP/IP.
> Thanks...Safeer
>
> "Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
> news:53642094-FE1C-4BFB-85BF-E114587DDB0F@.microsoft.com...
> want
> rights.
> Edition
> MSTSC.
> message
> I
> I
>|||Its SQL Server 2000.
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:uPPE4YgWHHA.4384@.TK2MSFTNGP02.phx.gbl...
> Is the SQL Server Browser service started?
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Safeer" <safeerm@.gmail.com> wrote in message
> news:e%23n1O5eWHHA.4668@.TK2MSFTNGP04.phx.gbl...
the[vbcol=seagreen]
message[vbcol=seagreen]
and[vbcol=seagreen]
to[vbcol=seagreen]
>|||Okay, did you follow the checklist shown in:
http://betav.com/blog/billva/2006/0..._connected.html ?
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Safeer" <safeerm@.gmail.com> wrote in message
news:eR6kqFsWHHA.3332@.TK2MSFTNGP04.phx.gbl...
> Its SQL Server 2000.
>
> "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> news:uPPE4YgWHHA.4384@.TK2MSFTNGP02.phx.gbl...
> rights.
> ---
> the
> message
> and
> to
>

Connection issue - Even Admin in the Server Machine

I am having administrative previlages in the SQL Server Machine, but I am
not able to connect to the SQL Server instance. Can you please help. I am
using windows authendication.
Thanks...Safeer
I tried telnet ipaddress 1433, its not connecting thru the port.
I am connected to the server directly and then checked the port using server
utility and its 1433.
"Safeer" <safeerm@.gmail.com> wrote in message
news:e1jmNjrVHHA.4028@.TK2MSFTNGP04.phx.gbl...
> I am having administrative previlages in the SQL Server Machine, but I am
> not able to connect to the SQL Server instance. Can you please help. I am
> using windows authendication.
> Thanks...Safeer
>
|||I tried telnet ipaddress 1433, its not connecting thru the port.
I am connected to the server directly and then checked the port using server
utility and its 1433.
"Safeer" <safeerm@.gmail.com> wrote in message
news:e1jmNjrVHHA.4028@.TK2MSFTNGP04.phx.gbl...
> I am having administrative previlages in the SQL Server Machine, but I am
> not able to connect to the SQL Server instance. Can you please help. I am
> using windows authendication.
> Thanks...Safeer
>
|||We need more info.
- What version and edition of SQL Server are you using?
- What version of the Windows are you using?
It sounds like you are connecting from a client on another computer. If you
are using SQL Server 2005, use the Surface Area Configuration tool to
confirm that your SQL Server instance is listening for remote connections.
Also, a firewall could be blocking 1433. This is common with Windows XP
service pack 2.
If SQL Server is running on Vista, you have other issues.
For SQL Server 2005, there is a short tutorial that will help. See
http://msdn2.microsoft.com/en-us/library/ms345318.aspx
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Safeer" <safeerm@.gmail.com> wrote in message
news:eu1sb1rVHHA.1016@.TK2MSFTNGP04.phx.gbl...
>I tried telnet ipaddress 1433, its not connecting thru the port.
> I am connected to the server directly and then checked the port using
> server
> utility and its 1433.
>
> "Safeer" <safeerm@.gmail.com> wrote in message
> news:e1jmNjrVHHA.4028@.TK2MSFTNGP04.phx.gbl...
>
|||Hi,
Windows: - Windows NT 5.2 (Build 3790: Service Pack 1)
SQL:- Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Standard Edition
My workstation is Windows 2000. I am connecting to the server using MSTSC.
My sql server log shows the following.
"SQL server listening on Shared Memory, Named Pipes."
Actually TCP/IP/1433 is enabled in the server.
& I am not able to telnet the machine with port 1433 from the server itself.
NB: No one is using this machine now and I need to setup and install service
packs. Its a new box with installed SQL 2K and nobody know the SA password.
Thanks...Safeer
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:08EB12C9-D906-4977-A40E-0F050C837E1E@.microsoft.com...
> We need more info.
> - What version and edition of SQL Server are you using?
> - What version of the Windows are you using?
> It sounds like you are connecting from a client on another computer. If
you
> are using SQL Server 2005, use the Surface Area Configuration tool to
> confirm that your SQL Server instance is listening for remote connections.
> Also, a firewall could be blocking 1433. This is common with Windows XP
> service pack 2.
> If SQL Server is running on Vista, you have other issues.
> For SQL Server 2005, there is a short tutorial that will help. See
> http://msdn2.microsoft.com/en-us/library/ms345318.aspx
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
rights.[vbcol=seagreen]
> "Safeer" <safeerm@.gmail.com> wrote in message
> news:eu1sb1rVHHA.1016@.TK2MSFTNGP04.phx.gbl...
am[vbcol=seagreen]
am
>
|||It looks like your SQL Server is listening on shared memory (which is a
local pipe) and named pipes, but is not listening on TCP/IP. So if you want
to connect using TCP/IP and port 1433, you will have to enable TCP/IP and
restart SQL Server. You use the Server Network Utility for that.
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Safeer" <safeerm@.gmail.com> wrote in message
news:uCxeUt5VHHA.868@.TK2MSFTNGP05.phx.gbl...
> Hi,
> Windows: - Windows NT 5.2 (Build 3790: Service Pack 1)
> SQL:- Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Standard Edition
> My workstation is Windows 2000. I am connecting to the server using MSTSC.
> My sql server log shows the following.
> "SQL server listening on Shared Memory, Named Pipes."
> Actually TCP/IP/1433 is enabled in the server.
> & I am not able to telnet the machine with port 1433 from the server
> itself.
> NB: No one is using this machine now and I need to setup and install
> service
> packs. Its a new box with installed SQL 2K and nobody know the SA
> password.
> Thanks...Safeer
>
> "Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
> news:08EB12C9-D906-4977-A40E-0F050C837E1E@.microsoft.com...
> you
> rights.
> am
> am
>
|||Hi Rick,
I've already did that. Now I did it again and restarted the server. In the
Server Netwrok Utility, its showing tcp/ip. But the log is not showing
TCP/IP.
Thanks...Safeer
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:53642094-FE1C-4BFB-85BF-E114587DDB0F@.microsoft.com...
> It looks like your SQL Server is listening on shared memory (which is a
> local pipe) and named pipes, but is not listening on TCP/IP. So if you
want
> to connect using TCP/IP and port 1433, you will have to enable TCP/IP and
> restart SQL Server. You use the Server Network Utility for that.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
rights.[vbcol=seagreen]
> "Safeer" <safeerm@.gmail.com> wrote in message
> news:uCxeUt5VHHA.868@.TK2MSFTNGP05.phx.gbl...
Edition[vbcol=seagreen]
MSTSC.[vbcol=seagreen]
message[vbcol=seagreen]
I[vbcol=seagreen]
I
>
|||Is the SQL Server Browser service started?
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Safeer" <safeerm@.gmail.com> wrote in message
news:e%23n1O5eWHHA.4668@.TK2MSFTNGP04.phx.gbl...
> Hi Rick,
> I've already did that. Now I did it again and restarted the server. In the
> Server Netwrok Utility, its showing tcp/ip. But the log is not showing
> TCP/IP.
> Thanks...Safeer
>
> "Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
> news:53642094-FE1C-4BFB-85BF-E114587DDB0F@.microsoft.com...
> want
> rights.
> Edition
> MSTSC.
> message
> I
> I
>
|||Its SQL Server 2000.
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:uPPE4YgWHHA.4384@.TK2MSFTNGP02.phx.gbl...
> Is the SQL Server Browser service started?
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---[vbcol=seagreen]
> "Safeer" <safeerm@.gmail.com> wrote in message
> news:e%23n1O5eWHHA.4668@.TK2MSFTNGP04.phx.gbl...
the[vbcol=seagreen]
message[vbcol=seagreen]
and[vbcol=seagreen]
to
>
|||Okay, did you follow the checklist shown in:
http://betav.com/blog/billva/2006/06/getting_and_staying_connected.html ?
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Safeer" <safeerm@.gmail.com> wrote in message
news:eR6kqFsWHHA.3332@.TK2MSFTNGP04.phx.gbl...
> Its SQL Server 2000.
>
> "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> news:uPPE4YgWHHA.4384@.TK2MSFTNGP02.phx.gbl...
> rights.
> the
> message
> and
> to
>

Connection is busy with results for another hstmt

HI guys,

I'm using ODBC driver from WinXP SP2 with SQL Server 2005 Express (on my machine for test) and SQL Server 2005 Standard (on the production machine).

With SQL Server 2005 Express I've no problem, but with SQL Server 2005 Standard, in some query, I get "Connection is busy with results for another hstmt".

I'm working with VisualStudio 2003 with standard CDatabase and CRecordSet MFC classes.

I looked for an advice in the Microsoft KB but I found only Service Pack for SQL Server 2000 !

Everything could be useful !

Thanks a lot!

Bye, Domenico

You can avoid this error message by switching to the SQL Server 2005 ODBC driver, 'SQL Native Client' and enabling the MARS (Multiple Active Result Sets feature). There is more information in Books Online and also here http://blogs.msdn.com/dataaccess/archive/2005/08/02/446894.aspx

Connection handshake failed.

Hi.

I created two instances of SQL Server Dev Edition on the same machine.

The two instances acted as the sender / receiver.

However, when the message is transmitted from "Sender" to "Receiver", the following errors are
displayed in "SQL Profiler".

「Connection handshake failed. There is no compatible authentication protocol. State 21.」

How should be dealt with with this?
My best regards.

piknik

Seems like there is a problem with how you've setup your endpoints. Could you paste the script which you used for creating the endpoints? If you don't have that, could you paste the results from this query run on both instances?

select * from sys.service_broker_endpoints

|||

One machine is configured to use CERTIFICATE authentication, the other is configured to use WINDOWS. (or one is configured to use WINDOWS KERBEROS and the other WINDOWS NTLM).

Configure the endpoints to have at least one compatible authentication protocol and it will work.

HTH,
~ Remus

|||

Thank you for the reply.

I used following Script.

[Sender]

USE master
GO

-- Create master key in the master database
CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'password62374'

-- Create the certificate for transport security
CREATE CERTIFICATE TransportCert1
FROM FILE = 'C:\Documents and Settings\ryutai\Desktop\Demo\Certs\TransportCert1.cer'
WITH PRIVATE KEY (
FILE = 'C:\Documents and Settings\ryutai\Desktop\Demo\Certs\TransportCert1.pvk',
DECRYPTION BY PASSWORD = 'password62374'
)
ACTIVE FOR BEGIN_DIALOG = ON
GO

-- Create a user in the master db to be associated with
-- the public key from the remote certificate (TestCert2.cer)
CREATE LOGIN remcert WITH PASSWORD = 'password62374'
CREATE USER remcert FOR LOGIN remcert

-- remcert has to have connect priviliges
GRANT CONNECT TO remcert

-- Install the public key from the remote cert in master
CREATE CERTIFICATE TransportCert2
AUTHORIZATION remcert
FROM FILE = 'C:\Documents and Settings\ryutai\Desktop\Demo\Certs\TransportCert2.cer'
ACTIVE FOR BEGIN_DIALOG = ON
GO

-- Switch to the user database
USE SuperMarketServer
GO

-- Create a master key
CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'password62374'

-- Create a certificate for dialog security
CREATE CERTIFICATE DialogCert1
FROM FILE = 'C:\Documents and Settings\ryutai\Desktop\Demo\Certs\DialogCert1.cer'
WITH PRIVATE KEY (
FILE = 'C:\Documents and Settings\ryutai\Desktop\Demo\Certs\DialogCert1.pvk',
DECRYPTION BY PASSWORD = 'password62374'
)
ACTIVE FOR BEGIN_DIALOG = ON
GO

-- Create user that holds the remote public key for the dialog security certificate
CREATE USER remcert FOR LOGIN remcert

CREATE CERTIFICATE DialogCert2
AUTHORIZATION remcert
FROM FILE = 'C:\Documents and Settings\ryutai\Desktop\Demo\Certs\DialogCert2.cer'
ACTIVE FOR BEGIN_DIALOG = ON
GO

-- Create a remote service binding associating the remcert user
-- with the remote service
CREATE REMOTE SERVICE BINDING [SellItemBinding]
TO SERVICE 'SellItemService'
WITH USER = remcert,
ANONYMOUS = Off

-- The user has to have SEND permissions
GRANT SEND ON SERVICE::[SoldItemService] TO remcert
go

-- Enable communication between instances by creating an endpoint
CREATE ENDPOINT ServerEndpoint
STATE = STARTED
AS TCP
(
LISTENER_PORT = 5024
)
FOR SERVICE_BROKER (AUTHENTICATION = CERTIFICATE TransportCert1)

-- Finally grant connect permission to user used to secure the dialog
USE master
GO

GRANT CONNECT ON ENDPOINT::ServerEndpoint TO remcert
GO

SELECT * FROM sys.endpoints
--

It is set to "CERTIFICATE authentication" as which Sender and Reciver are the
same.

The sample of Script is put.
http://enterpriselibrary.jp/SampleDemo.zip

My Best Regards.

piknik.

Connection gets lost

Hi,
I have a DSN set-up to access a SQL Server database from another
machine and program.
It is basically an import manager (third party product from an
external company), when I import it loads in a few thousand records
and then after about 2 minutes I get the following error:
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not
exist or access denied.
It then reconnects within a few minutes but misses loading the record
where the error happens.
Can someone help me locate the problem and how to fix it.
The external company has no problems with loading so i can only
imagine it is our SQL Server set-up
Thanks
ArchanaHi
"archanapatelwhite@.googlemail.com" wrote:
> Hi,
> I have a DSN set-up to access a SQL Server database from another
> machine and program.
> It is basically an import manager (third party product from an
> external company), when I import it loads in a few thousand records
> and then after about 2 minutes I get the following error:
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not
> exist or access denied.
> It then reconnects within a few minutes but misses loading the record
> where the error happens.
> Can someone help me locate the problem and how to fix it.
> The external company has no problems with loading so i can only
> imagine it is our SQL Server set-up
> Thanks
> Archana
>
I would initially suspect something like your Anti-virus software,
anti-intusion software or firewall is breaking the connection e.g
http://support.microsoft.com/kb/170338/en-us
You may want to also check if you are on a recent SQL Server service pack
see
http://sqlserver2000.databases.aspfaq.com/how-do-i-know-which-version-of-sql-server-i-m-running.html
John

Connection fails during unit test

Hi
I am having trouble with a connection within our local network. A
development machine needs to connect to the main dev db server. Visual
Studio and Enterprise Manager on the dev machine connect fine. The
application under development connects fine when it is run with the
connection string
"Data Source=[servername]; Initial Catalog=[dbName];
Trusted_Connection=yes;"
The application also connects nicely using a named login and password.
My problem is, when we run unit tests with NUnit on a remote machine the
connection attempt returns 'Sql Server does not exist or access denied'
with the same connection string. We have completely turned off all
firewalls etc to no avail.
Any Ideas?
Thanks
Graham
Have the remote machine test connecting with a new ODBC DSN. Press the
Test
button on the ODBC Wizard and report the OS error returned. Since the
machine is remote,
it could be a problem with name resolution.
Ex. 11001 == HostNameNotFound == DNS/WINS issue.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Kevin McDonnell [MSFT] wrote:

> Have the remote machine test connecting with a new ODBC DSN. Press the
> Test
> button on the ODBC Wizard and report the OS error returned. Since the
> machine is remote,
> it could be a problem with name resolution.
> Ex. 11001 == HostNameNotFound == DNS/WINS issue.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
Thanks for the reply Kevin...
I have tried the ODBC wizard and the connection works fine. As I said I
have no problem connecting from the remote machine using Enterprise
Manager and Visual Studio, it is just the NUnit tests that can't access
the db server.
Thanks again
Graham
|||"when we run unit tests with NUnit on a remote machine the
connection attempt returns 'Sql Server does not exist or access denied'
with the same connection string. "
I would run network traces to determine where the problem is. You need to
validate
that the tcp connection is being made and the connection string is correct.
An ODBC trace won't show
you this level of detail.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Kevin McDonnell [MSFT] wrote:
> "when we run unit tests with NUnit on a remote machine the
> connection attempt returns 'Sql Server does not exist or access denied'
> with the same connection string. "
> I would run network traces to determine where the problem is. You need to
> validate
> that the tcp connection is being made and the connection string is correct.
> An ODBC trace won't show
> you this level of detail.
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
Thanks again Kevin
My networking knowledge is a little lacking I'm afraid. Could you give
me some pointers on how I would go about running 'network traces'.
Thanks
Graham
|||SQL Server is a Winsock application. So the 2nd article will help you
understand what to look for.
If you need more help you can always open up a support case.
Windows 2000 Server has netmon installed . You just need to enable it via
Add/Remove Windows components.
This version captures traffic to and from that machine. Only SMS has the
full version to capture traffic on any machine.
Q148942 How to Capture Network Traffic with Network Monitor
Q169292 The Basics of Reading TCP/IP Traces
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Connection fails during unit test

Hi
I am having trouble with a connection within our local network. A
development machine needs to connect to the main dev db server. Visual
Studio and Enterprise Manager on the dev machine connect fine. The
application under development connects fine when it is run with the
connection string
"Data Source=[servername]; Initial Catalog=[dbName];
Trusted_Connection=yes;"
The application also connects nicely using a named login and password.
My problem is, when we run unit tests with NUnit on a remote machine the
connection attempt returns 'Sql Server does not exist or access denied'
with the same connection string. We have completely turned off all
firewalls etc to no avail.
Any Ideas?
Thanks
GrahamHave the remote machine test connecting with a new ODBC DSN. Press the
Test
button on the ODBC Wizard and report the OS error returned. Since the
machine is remote,
it could be a problem with name resolution.
Ex. 11001 == HostNameNotFound == DNS/WINS issue.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin McDonnell [MSFT] wrote:

> Have the remote machine test connecting with a new ODBC DSN. Press the
> Test
> button on the ODBC Wizard and report the OS error returned. Since the
> machine is remote,
> it could be a problem with name resolution.
> Ex. 11001 == HostNameNotFound == DNS/WINS issue.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
Thanks for the reply Kevin...
I have tried the ODBC wizard and the connection works fine. As I said I
have no problem connecting from the remote machine using Enterprise
Manager and Visual Studio, it is just the NUnit tests that can't access
the db server.
Thanks again
Graham|||"when we run unit tests with NUnit on a remote machine the
connection attempt returns 'Sql Server does not exist or access denied'
with the same connection string. "
I would run network traces to determine where the problem is. You need to
validate
that the tcp connection is being made and the connection string is correct.
An ODBC trace won't show
you this level of detail.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin McDonnell [MSFT] wrote:
> "when we run unit tests with NUnit on a remote machine the
> connection attempt returns 'Sql Server does not exist or access denied'
> with the same connection string. "
> I would run network traces to determine where the problem is. You need to
> validate
> that the tcp connection is being made and the connection string is correct
.
> An ODBC trace won't show
> you this level of detail.
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
Thanks again Kevin
My networking knowledge is a little lacking I'm afraid. Could you give
me some pointers on how I would go about running 'network traces'.
Thanks
Graham|||SQL Server is a Winsock application. So the 2nd article will help you
understand what to look for.
If you need more help you can always open up a support case.
Windows 2000 Server has netmon installed . You just need to enable it via
Add/Remove Windows components.
This version captures traffic to and from that machine. Only SMS has the
full version to capture traffic on any machine.
Q148942 How to Capture Network Traffic with Network Monitor
Q169292 The Basics of Reading TCP/IP Traces
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

connection failed

Hello,
I have sql server 2000 on a XP/SP2 machine.. with XP firewall active.
But I cannot connect to sql server. I receive this message "Unable to
connect to server xxxxxx: SQL Server does not exist or access denied"; or
Login failed for user xxxxx. With QA same problem... I created the alias
with client network utility... but no way... i cannot access sql server.
anyone have an idea?
Thanks in advance
Alex
You would want to start with this article and the links it
references - the problems depend on protocols, what the
exact full error message is, what ports you have opened (if
any), etc:
How to configure Windows XP Service Pack 2 (SP2) for use
with SQL Server
http://support.microsoft.com/?id=841249
-Sue
On Fri, 11 Mar 2005 09:15:54 +0200, ".:alex:."
<alex_77ro@.yahoo.com> wrote:

>Hello,
> I have sql server 2000 on a XP/SP2 machine.. with XP firewall active.
>But I cannot connect to sql server. I receive this message "Unable to
>connect to server xxxxxx: SQL Server does not exist or access denied"; or
>Login failed for user xxxxx. With QA same problem... I created the alias
>with client network utility... but no way... i cannot access sql server.
>anyone have an idea?
>Thanks in advance
>Alex
>