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
>

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
AlexYou 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
>

Connection Failed

SQL 2000
Windows 2000 sp4

I have created a group called "queryonly" in Active Directory. I have
added myself to this group. When I attempt to create an ODBC connection
to the SQL server I get "connection failed".

When I add myself explicity (ie domain\user) it connects fine.

Why is the group not working? I want to cut down on some
administration.

Thanks.

JustinJustin wrote:
> SQL 2000
> Windows 2000 sp4
> I have created a group called "queryonly" in Active Directory. I have
> added myself to this group. When I attempt to create an ODBC connection
> to the SQL server I get "connection failed".
> When I add myself explicity (ie domain\user) it connects fine.
> Why is the group not working? I want to cut down on some
> administration.
> Thanks.
> Justin

Hi Justin,

Make sure that you log off and then log in after adding yourself to the
group. Sounds stupid, but it seems to work for me :)

Michael

Connection between Active Directory and SQL server in VB6

Hello,
I have a couple VB6 projects in which I need to connect to the SQL
server. Due to security reason I wonder what is the best way to connect
to the SQL server.
I understand using Window Authentication is really a good way to
connect to the SQL server, however, if the # of users grow, I then have
to create a large number of users in the SQL server which is not
preferable.
Instead I wonder if the following is doable:
Can I create security group in Active Directory which allows certain
groups connect to only certain DBs in the SQL server? But how can I do
with the connectionstring when I connect to the SQL server in my VB6
code.
I really wish this is workable. If so, how can I do it? If not, is
there any other suggestion that I can make certain groups of ppl
connect only to certain DBs?
Thanks in advance. Your help would be greatly appreciated.
WandaHi,
kindly check books online> index> search for
Windows NT groups
thanks,
--
Jose de Jesus Jr. Mcp,Mcdba
Data Architect
Sykes Asia (Manila philippines)
MCP #2324787
"wandali@.rogers.com" wrote:
> Hello,
> I have a couple VB6 projects in which I need to connect to the SQL
> server. Due to security reason I wonder what is the best way to connect
> to the SQL server.
> I understand using Window Authentication is really a good way to
> connect to the SQL server, however, if the # of users grow, I then have
> to create a large number of users in the SQL server which is not
> preferable.
> Instead I wonder if the following is doable:
> Can I create security group in Active Directory which allows certain
> groups connect to only certain DBs in the SQL server? But how can I do
> with the connectionstring when I connect to the SQL server in my VB6
> code.
> I really wish this is workable. If so, how can I do it? If not, is
> there any other suggestion that I can make certain groups of ppl
> connect only to certain DBs?
> Thanks in advance. Your help would be greatly appreciated.
> Wanda
>|||Can't find it, can you please provide me a link? Any more help?

Connection between Active Directory and SQL server in VB6

Hello,
I have a couple VB6 projects in which I need to connect to the SQL
server. Due to security reason I wonder what is the best way to connect
to the SQL server.
I understand using Window Authentication is really a good way to
connect to the SQL server, however, if the # of users grow, I then have
to create a large number of users in the SQL server which is not
preferable.
Instead I wonder if the following is doable:
Can I create security group in Active Directory which allows certain
groups connect to only certain DBs in the SQL server? But how can I do
with the connectionstring when I connect to the SQL server in my VB6
code.
I really wish this is workable. If so, how can I do it? If not, is
there any other suggestion that I can make certain groups of ppl
connect only to certain DBs?
Thanks in advance. Your help would be greatly appreciated.
WandaHi,
kindly check books online> index> search for
Windows NT groups
thanks,
Jose de Jesus Jr. Mcp,Mcdba
Data Architect
Sykes Asia (Manila philippines)
MCP #2324787
"wandali@.rogers.com" wrote:

> Hello,
> I have a couple VB6 projects in which I need to connect to the SQL
> server. Due to security reason I wonder what is the best way to connect
> to the SQL server.
> I understand using Window Authentication is really a good way to
> connect to the SQL server, however, if the # of users grow, I then have
> to create a large number of users in the SQL server which is not
> preferable.
> Instead I wonder if the following is doable:
> Can I create security group in Active Directory which allows certain
> groups connect to only certain DBs in the SQL server? But how can I do
> with the connectionstring when I connect to the SQL server in my VB6
> code.
> I really wish this is workable. If so, how can I do it? If not, is
> there any other suggestion that I can make certain groups of ppl
> connect only to certain DBs?
> Thanks in advance. Your help would be greatly appreciated.
> Wanda
>|||Can't find it, can you please provide me a link? Any more help?

Connection between Active Directory and SQL server in VB6

Hello,
I have a couple VB6 projects in which I need to connect to the SQL
server. Due to security reason I wonder what is the best way to connect
to the SQL server.
I understand using Window Authentication is really a good way to
connect to the SQL server, however, if the # of users grow, I then have
to create a large number of users in the SQL server which is not
preferable.
Instead I wonder if the following is doable:
Can I create security group in Active Directory which allows certain
groups connect to only certain DBs in the SQL server? But how can I do
with the connectionstring when I connect to the SQL server in my VB6
code.
I really wish this is workable. If so, how can I do it? If not, is
there any other suggestion that I can make certain groups of ppl
connect only to certain DBs?
Thanks in advance. Your help would be greatly appreciated.
Wanda
Hi,
kindly check books online> index> search for
Windows NT groups
thanks,
Jose de Jesus Jr. Mcp,Mcdba
Data Architect
Sykes Asia (Manila philippines)
MCP #2324787
"wandali@.rogers.com" wrote:

> Hello,
> I have a couple VB6 projects in which I need to connect to the SQL
> server. Due to security reason I wonder what is the best way to connect
> to the SQL server.
> I understand using Window Authentication is really a good way to
> connect to the SQL server, however, if the # of users grow, I then have
> to create a large number of users in the SQL server which is not
> preferable.
> Instead I wonder if the following is doable:
> Can I create security group in Active Directory which allows certain
> groups connect to only certain DBs in the SQL server? But how can I do
> with the connectionstring when I connect to the SQL server in my VB6
> code.
> I really wish this is workable. If so, how can I do it? If not, is
> there any other suggestion that I can make certain groups of ppl
> connect only to certain DBs?
> Thanks in advance. Your help would be greatly appreciated.
> Wanda
>
|||Can't find it, can you please provide me a link? Any more help?

Connection ADOMD

The problem occur when we use ADOMD to create a Cube in an ASP.NET 2.0 application with impersonate and Windows Authentication active in web.config and Integrated Security in the MSOLAP connection to the Analysis Services 2000. When we list de catalogs from Analysis Services we get authenticated with the impersonated Windows Account, but when we try to Create a new cube on a catalog, we get authenticated with the ASPNET windows account, even with impersonate set to true. We are using the 9.0 client version of MSOLAP provider to connect to an Analysis Services 2000 (8.0).

HI,thiago:

I believe this topic is related to theSQL Server Analysis Services. Now we have not this section in the forum, but here is the better place you can post your thread in and there are more experts will be glad to help you to solve your problem:

http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=83&SiteID=1

Connecting VIA IP Address

When I try to connect via IP to a newly created Active Active cluster I
have to add the port to the IP for it to work. An example is if my IP
is 10.0.0.1 and I try to connect it times out. if I try 10.0.0.1,1433
then it works fine. Am I missing a setting somewhere to make this work
just by using the IP? Oh... and just to note this work the same accross
the network or if I am logged on local to the box.
thanks
Chris
I should have stated this but I am using SQL Server 2000 and the server
is Windows 2003
|||I should have stated this but I am using SQL Server 200 on a Windows
2003 cluster

COnnecting via IP address

When I try to connect via IP to a newly created Active Active cluster I
have to add the port to the IP for it to work. An example is if my IP
is 10.0.0.1 and I try to connect it times out. if I try 10.0.0.1,1433
then it works fine. Am I missing a setting somewhere to make this work
just by using the IP? Oh... and just to note this work the same accross
the network or if I am logged on local to the box.
thanks
Chris
I should have stated this but I am using SQL Server 200 on a Windows
2003 cluster
|||Your SQL Server instance must be a named instance listening on port 1433. If
it were a default instance, connecting to the IP without specifying a port
would have automatically led to the default port of 1433, and would have
succeeded.
With a named instance, however, you are not directed to 1433 by default.
Either the client has to be told by the server via UDP 1434 as to what port
to use, or it has to identify the port explicitly. And if the client is
using an explicit IP address, you are not using UDP 1434.
Linchi
<cfrank@.investorforce.com> wrote in message
news:1140797262.929065.72080@.i40g2000cwc.googlegro ups.com...
> When I try to connect via IP to a newly created Active Active cluster I
> have to add the port to the IP for it to work. An example is if my IP
> is 10.0.0.1 and I try to connect it times out. if I try 10.0.0.1,1433
> then it works fine. Am I missing a setting somewhere to make this work
> just by using the IP? Oh... and just to note this work the same accross
> the network or if I am logged on local to the box.
> thanks
> Chris
>

COnnecting via IP address

When I try to connect via IP to a newly created Active Active cluster I
have to add the port to the IP for it to work. An example is if my IP
is 10.0.0.1 and I try to connect it times out. if I try 10.0.0.1,1433
then it works fine. Am I missing a setting somewhere to make this work
just by using the IP? Oh... and just to note this work the same accross
the network or if I am logged on local to the box.
thanks
ChrisI should have stated this but I am using SQL Server 200 on a Windows
2003 cluster|||Your SQL Server instance must be a named instance listening on port 1433. If
it were a default instance, connecting to the IP without specifying a port
would have automatically led to the default port of 1433, and would have
succeeded.
With a named instance, however, you are not directed to 1433 by default.
Either the client has to be told by the server via UDP 1434 as to what port
to use, or it has to identify the port explicitly. And if the client is
using an explicit IP address, you are not using UDP 1434.
Linchi
<cfrank@.investorforce.com> wrote in message
news:1140797262.929065.72080@.i40g2000cwc.googlegroups.com...
> When I try to connect via IP to a newly created Active Active cluster I
> have to add the port to the IP for it to work. An example is if my IP
> is 10.0.0.1 and I try to connect it times out. if I try 10.0.0.1,1433
> then it works fine. Am I missing a setting somewhere to make this work
> just by using the IP? Oh... and just to note this work the same accross
> the network or if I am logged on local to the box.
> thanks
> Chris
>