Hi ng!
The facts:
SQL Server 2005 is installed on a Windows 2003 server within a domain. Every
XP-Clients can connect to SQL Server via ODBC without any problems.
The problem
From the localhost I cannot connect to SQL-Server, AND from any (2) other
W2K
Server in the same domain I cannot connect to SQL Server.
Here is the original error message, in german:
SQLState: '01000'
SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
[Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheitsfehler
Have you any hints for me? I worked since 5 Days on this Problem...
The solution: :)
THX
Markus
PS: my german is much better...
Sorry for dubbleposting,I have not seen this ng bevor.For local, perhaps Shared Memory driver is disabled? See server config
manager, sql server 2005 network configuration tab.
For remote win2K, check surface area config for Remote Connections - are
both tcp and named pipes enables?
Also you can go to the win2K machines and set up aliases using ODBC or
native client managers.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
> Hi ng!
> The facts:
> SQL Server 2005 is installed on a Windows 2003 server within a domain.
> Every
> XP-Clients can connect to SQL Server via ODBC without any problems.
> The problem
> From the localhost I cannot connect to SQL-Server, AND from any (2) other
> W2K
> Server in the same domain I cannot connect to SQL Server.
>
> Here is the original error message, in german:
> SQLState: '01000'
> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
> Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheitsfehler
>
> Have you any hints for me? I worked since 5 Days on this Problem...
> The solution: :)
> THX
> Markus
> PS: my german is much better...
> Sorry for dubbleposting,I have not seen this ng bevor.
>
>|||Shared Memory is disabled.
3 Clients are XP, there are all works fine
3 Servers 2K3 (2 of this are TS): nobody can connect the database
I am only use ODBC, no native client, only tcp is activ
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13krh3qgfmd58d8@.corp.supernews.com...
> For local, perhaps Shared Memory driver is disabled? See server config
> manager, sql server 2005 network configuration tab.
> For remote win2K, check surface area config for Remote Connections - are
> both tcp and named pipes enables?
> Also you can go to the win2K machines and set up aliases using ODBC or
> native client managers.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> Hi ng!
>> The facts:
>> SQL Server 2005 is installed on a Windows 2003 server within a domain.
>> Every
>> XP-Clients can connect to SQL Server via ODBC without any problems.
>> The problem
>> From the localhost I cannot connect to SQL-Server, AND from any (2) other
>> W2K
>> Server in the same domain I cannot connect to SQL Server.
>>
>> Here is the original error message, in german:
>> SQLState: '01000'
>> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
>> Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
>> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
>> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheitsfehler
>>
>> Have you any hints for me? I worked since 5 Days on this Problem...
>> The solution: :)
>> THX
>> Markus
>> PS: my german is much better...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>|||Local connections on same box will attempt to use Shared Mem IIRC, so try
with it enabled.
You say you use only ODBC, but built-in sql server tools such as QA or SSMS
use whatever their default is set up to be, which could be named pipes. Try
forcibly setting the connection mechanism to tcp and see if it works.
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
> Shared Memory is disabled.
> 3 Clients are XP, there are all works fine
> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
> I am only use ODBC, no native client, only tcp is activ
> Markus
>
> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
> news:13krh3qgfmd58d8@.corp.supernews.com...
>> For local, perhaps Shared Memory driver is disabled? See server config
>> manager, sql server 2005 network configuration tab.
>> For remote win2K, check surface area config for Remote Connections - are
>> both tcp and named pipes enables?
>> Also you can go to the win2K machines and set up aliases using ODBC or
>> native client managers.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> Hi ng!
>> The facts:
>> SQL Server 2005 is installed on a Windows 2003 server within a domain.
>> Every
>> XP-Clients can connect to SQL Server via ODBC without any problems.
>> The problem
>> From the localhost I cannot connect to SQL-Server, AND from any (2)
>> other W2K
>> Server in the same domain I cannot connect to SQL Server.
>>
>> Here is the original error message, in german:
>> SQLState: '01000'
>> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
>> Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
>> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
>> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheitsfehler
>>
>> Have you any hints for me? I worked since 5 Days on this Problem...
>> The solution: :)
>> THX
>> Markus
>> PS: my german is much better...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>>
>|||Hi Kevin!
SSMS with tcp/ip works.
I have try to connect via MSSMS to connect from a w2k3 serve to the other
w2k3 Server (SQL Server), this works.
The only thing is, I cannot connect via ODBC from local host or any other
W2k3 Server to my W2k3 Server with SQL 2005. I can connect from any XP
Workstion without problems.
The ODBC - Driver Config is the same on XP ans W2k3. I think the only
differnt ist the ODBC Driver Version:
On XP I use the follwing ODBC Driver: SQL Server V2000.85.1117.00
on W2K3 : 2000.86.3959.00
I am not use the native client, shared memory and tcp/ip is on, the rest
off, SQL Native Client: all is off
\\sqlserver\myprog is always map to s:\
myprog.exe and myprog.ini is always the same
My connection string looks like this (with and without integratet security):
DSN=MYPROG_MSSQL;Database=MYPROG
-or-
DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password
-or-
DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password;Trusted_Connection=No;Encrypt=No;
Any Ideas?
THX in advanced
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13krpmsnuutd460@.corp.supernews.com...
> Local connections on same box will attempt to use Shared Mem IIRC, so try
> with it enabled.
> You say you use only ODBC, but built-in sql server tools such as QA or
> SSMS use whatever their default is set up to be, which could be named
> pipes. Try forcibly setting the connection mechanism to tcp and see if it
> works.
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> Shared Memory is disabled.
>> 3 Clients are XP, there are all works fine
>> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
>> I am only use ODBC, no native client, only tcp is activ
>> Markus
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
>> news:13krh3qgfmd58d8@.corp.supernews.com...
>> For local, perhaps Shared Memory driver is disabled? See server config
>> manager, sql server 2005 network configuration tab.
>> For remote win2K, check surface area config for Remote Connections - are
>> both tcp and named pipes enables?
>> Also you can go to the win2K machines and set up aliases using ODBC or
>> native client managers.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> Hi ng!
>> The facts:
>> SQL Server 2005 is installed on a Windows 2003 server within a domain.
>> Every
>> XP-Clients can connect to SQL Server via ODBC without any problems.
>> The problem
>> From the localhost I cannot connect to SQL-Server, AND from any (2)
>> other W2K
>> Server in the same domain I cannot connect to SQL Server.
>>
>> Here is the original error message, in german:
>> SQLState: '01000'
>> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
>> Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
>> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
>> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheitsfehler
>>
>> Have you any hints for me? I worked since 5 Days on this Problem...
>> The solution: :)
>> THX
>> Markus
>> PS: my german is much better...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>>
>>
>|||Sorry - I have exhausted my ideas on this one. Time to give MS Support a
call!
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:%23z4vCloMIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hi Kevin!
> SSMS with tcp/ip works.
>
> I have try to connect via MSSMS to connect from a w2k3 serve to the other
> w2k3 Server (SQL Server), this works.
> The only thing is, I cannot connect via ODBC from local host or any other
> W2k3 Server to my W2k3 Server with SQL 2005. I can connect from any XP
> Workstion without problems.
> The ODBC - Driver Config is the same on XP ans W2k3. I think the only
> differnt ist the ODBC Driver Version:
> On XP I use the follwing ODBC Driver: SQL Server V2000.85.1117.00
> on W2K3 : 2000.86.3959.00
> I am not use the native client, shared memory and tcp/ip is on, the rest
> off, SQL Native Client: all is off
>
> \\sqlserver\myprog is always map to s:\
> myprog.exe and myprog.ini is always the same
> My connection string looks like this (with and without integratet
> security):
> DSN=MYPROG_MSSQL;Database=MYPROG
> -or-
> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password
> -or-
> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password;Trusted_Connection=No;Encrypt=No;
>
> Any Ideas?
> THX in advanced
> Markus
>
>
> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
> news:13krpmsnuutd460@.corp.supernews.com...
>> Local connections on same box will attempt to use Shared Mem IIRC, so try
>> with it enabled.
>> You say you use only ODBC, but built-in sql server tools such as QA or
>> SSMS use whatever their default is set up to be, which could be named
>> pipes. Try forcibly setting the connection mechanism to tcp and see if
>> it works.
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> Shared Memory is disabled.
>> 3 Clients are XP, there are all works fine
>> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
>> I am only use ODBC, no native client, only tcp is activ
>> Markus
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
>> news:13krh3qgfmd58d8@.corp.supernews.com...
>> For local, perhaps Shared Memory driver is disabled? See server config
>> manager, sql server 2005 network configuration tab.
>> For remote win2K, check surface area config for Remote Connections -
>> are both tcp and named pipes enables?
>> Also you can go to the win2K machines and set up aliases using ODBC or
>> native client managers.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> Hi ng!
>> The facts:
>> SQL Server 2005 is installed on a Windows 2003 server within a domain.
>> Every
>> XP-Clients can connect to SQL Server via ODBC without any problems.
>> The problem
>> From the localhost I cannot connect to SQL-Server, AND from any (2)
>> other W2K
>> Server in the same domain I cannot connect to SQL Server.
>>
>> Here is the original error message, in german:
>> SQLState: '01000'
>> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
>> Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
>> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
>> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheitsfehler
>>
>> Have you any hints for me? I worked since 5 Days on this Problem...
>> The solution: :)
>> THX
>> Markus
>> PS: my german is much better...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>>
>>
>>
>|||Hi Kevin,
when I set my Programm "compatible with XP" (in Programm properties), then
the connection works!
But its not a real solution, so I have to connect from 2 Servers and the
property dialog for compatible mode is only availible on a local drive.
Any Ideas?
Thx
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13kui5qdav3mqed@.corp.supernews.com...
> Sorry - I have exhausted my ideas on this one. Time to give MS Support a
> call!
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:%23z4vCloMIHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hi Kevin!
>> SSMS with tcp/ip works.
>>
>> I have try to connect via MSSMS to connect from a w2k3 serve to the other
>> w2k3 Server (SQL Server), this works.
>> The only thing is, I cannot connect via ODBC from local host or any other
>> W2k3 Server to my W2k3 Server with SQL 2005. I can connect from any XP
>> Workstion without problems.
>> The ODBC - Driver Config is the same on XP ans W2k3. I think the only
>> differnt ist the ODBC Driver Version:
>> On XP I use the follwing ODBC Driver: SQL Server V2000.85.1117.00
>> on W2K3 : 2000.86.3959.00
>> I am not use the native client, shared memory and tcp/ip is on, the rest
>> off, SQL Native Client: all is off
>>
>> \\sqlserver\myprog is always map to s:\
>> myprog.exe and myprog.ini is always the same
>> My connection string looks like this (with and without integratet
>> security):
>> DSN=MYPROG_MSSQL;Database=MYPROG
>> -or-
>> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password
>> -or-
>> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password;Trusted_Connection=No;Encrypt=No;
>>
>> Any Ideas?
>> THX in advanced
>> Markus
>>
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
>> news:13krpmsnuutd460@.corp.supernews.com...
>> Local connections on same box will attempt to use Shared Mem IIRC, so
>> try with it enabled.
>> You say you use only ODBC, but built-in sql server tools such as QA or
>> SSMS use whatever their default is set up to be, which could be named
>> pipes. Try forcibly setting the connection mechanism to tcp and see if
>> it works.
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> Shared Memory is disabled.
>> 3 Clients are XP, there are all works fine
>> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
>> I am only use ODBC, no native client, only tcp is activ
>> Markus
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
>> news:13krh3qgfmd58d8@.corp.supernews.com...
>> For local, perhaps Shared Memory driver is disabled? See server
>> config manager, sql server 2005 network configuration tab.
>> For remote win2K, check surface area config for Remote Connections -
>> are both tcp and named pipes enables?
>> Also you can go to the win2K machines and set up aliases using ODBC or
>> native client managers.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> Hi ng!
>> The facts:
>> SQL Server 2005 is installed on a Windows 2003 server within a
>> domain. Every
>> XP-Clients can connect to SQL Server via ODBC without any problems.
>> The problem
>> From the localhost I cannot connect to SQL-Server, AND from any (2)
>> other W2K
>> Server in the same domain I cannot connect to SQL Server.
>>
>> Here is the original error message, in german:
>> SQLState: '01000'
>> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
>> Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
>> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
>> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL
>> Sicherheitsfehler
>>
>> Have you any hints for me? I worked since 5 Days on this Problem...
>> The solution: :)
>> THX
>> Markus
>> PS: my german is much better...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>>
>>
>>
>>
>
Showing posts with label localhost. Show all posts
Showing posts with label localhost. Show all posts
Friday, February 24, 2012
Cannot connect to SQL Server from localhost (no problem from any xp client)
Hi ng!
The facts:
SQL Server 2005 is installed on a Windows 2003 server within a domain. Every
XP-Clients can connect to SQL Server via ODBC without any problems.
The problem
From the localhost I cannot connect to SQL-Server, AND from any (2) other
W2K
Server in the same domain I cannot connect to SQL Server.
Here is the original error message, in german:
SQLState: '01000'
SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
Driver]& #91;SharedMemory]ConnectionOpen(SECDoCli
entHandshake())-
Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
[Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheits
fehler
Have you any hints for me? I worked since 5 Days on this Problem...
The solution:
THX
Markus
PS: my german is much better...
Sorry for dubbleposting,I have not seen this ng bevor.For local, perhaps Shared Memory driver is disabled? See server config
manager, sql server 2005 network configuration tab.
For remote win2K, check surface area config for Remote Connections - are
both tcp and named pipes enables?
Also you can go to the win2K machines and set up aliases using ODBC or
native client managers.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
> Hi ng!
> The facts:
> SQL Server 2005 is installed on a Windows 2003 server within a domain.
> Every
> XP-Clients can connect to SQL Server via ODBC without any problems.
> The problem
> From the localhost I cannot connect to SQL-Server, AND from any (2) other
> W2K
> Server in the same domain I cannot connect to SQL Server.
>
> Here is the original error message, in german:
> SQLState: '01000'
> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
> Driver]& #91;SharedMemory]ConnectionOpen(SECDoCli
entHandshake())-
> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherhei
tsfehler
>
> Have you any hints for me? I worked since 5 Days on this Problem...
> The solution:
> THX
> Markus
> PS: my german is much better...
> Sorry for dubbleposting,I have not seen this ng bevor.
>
>|||Shared Memory is disabled.
3 Clients are XP, there are all works fine
3 Servers 2K3 (2 of this are TS): nobody can connect the database
I am only use ODBC, no native client, only tcp is activ
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13krh3qgfmd58d8@.corp.supernews.com...
> For local, perhaps Shared Memory driver is disabled? See server config
> manager, sql server 2005 network configuration tab.
> For remote win2K, check surface area config for Remote Connections - are
> both tcp and named pipes enables?
> Also you can go to the win2K machines and set up aliases using ODBC or
> native client managers.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>|||Local connections on same box will attempt to use Shared Mem IIRC, so try
with it enabled.
You say you use only ODBC, but built-in sql server tools such as QA or SSMS
use whatever their default is set up to be, which could be named pipes. Try
forcibly setting the connection mechanism to tcp and see if it works.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
> Shared Memory is disabled.
> 3 Clients are XP, there are all works fine
> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
> I am only use ODBC, no native client, only tcp is activ
> Markus
>
> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
> news:13krh3qgfmd58d8@.corp.supernews.com...
>|||Hi Kevin!
SSMS with tcp/ip works.
I have try to connect via MSSMS to connect from a w2k3 serve to the other
w2k3 Server (SQL Server), this works.
The only thing is, I cannot connect via ODBC from local host or any other
W2k3 Server to my W2k3 Server with SQL 2005. I can connect from any XP
Workstion without problems.
The ODBC - Driver Config is the same on XP ans W2k3. I think the only
differnt ist the ODBC Driver Version:
On XP I use the follwing ODBC Driver: SQL Server V2000.85.1117.00
on W2K3 : 2000.86.3959.00
I am not use the native client, shared memory and tcp/ip is on, the rest
off, SQL Native Client: all is off
\\sqlserver\myprog is always map to s:\
myprog.exe and myprog.ini is always the same
My connection string looks like this (with and without integratet security):
DSN=MYPROG_MSSQL;Database=MYPROG
-or-
DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;
PWD=password
-or-
DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;
PWD=password;Trusted_Connection=No;E
ncrypt=No;
Any Ideas?
THX in advanced
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13krpmsnuutd460@.corp.supernews.com...
> Local connections on same box will attempt to use Shared Mem IIRC, so try
> with it enabled.
> You say you use only ODBC, but built-in sql server tools such as QA or
> SSMS use whatever their default is set up to be, which could be named
> pipes. Try forcibly setting the connection mechanism to tcp and see if it
> works.
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
>|||Sorry - I have exhausted my ideas on this one. Time to give MS Support a
call!
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:%23z4vCloMIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hi Kevin!
> SSMS with tcp/ip works.
>
> I have try to connect via MSSMS to connect from a w2k3 serve to the other
> w2k3 Server (SQL Server), this works.
> The only thing is, I cannot connect via ODBC from local host or any other
> W2k3 Server to my W2k3 Server with SQL 2005. I can connect from any XP
> Workstion without problems.
> The ODBC - Driver Config is the same on XP ans W2k3. I think the only
> differnt ist the ODBC Driver Version:
> On XP I use the follwing ODBC Driver: SQL Server V2000.85.1117.00
> on W2K3 : 2000.86.3959.00
> I am not use the native client, shared memory and tcp/ip is on, the rest
> off, SQL Native Client: all is off
>
> \\sqlserver\myprog is always map to s:\
> myprog.exe and myprog.ini is always the same
> My connection string looks like this (with and without integratet
> security):
> DSN=MYPROG_MSSQL;Database=MYPROG
> -or-
> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;
PWD=password
> -or-
> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;
PWD=password;Trusted_Connection=No
;Encrypt=No;
>
> Any Ideas?
> THX in advanced
> Markus
>
>
> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
> news:13krpmsnuutd460@.corp.supernews.com...
>|||Hi Kevin,
when I set my Programm "compatible with XP" (in Programm properties), then
the connection works!
But its not a real solution, so I have to connect from 2 Servers and the
property dialog for compatible mode is only availible on a local drive.
Any Ideas?
Thx
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13kui5qdav3mqed@.corp.supernews.com...
> Sorry - I have exhausted my ideas on this one. Time to give MS Support a
> call!
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:%23z4vCloMIHA.4712@.TK2MSFTNGP04.phx.gbl...
>
The facts:
SQL Server 2005 is installed on a Windows 2003 server within a domain. Every
XP-Clients can connect to SQL Server via ODBC without any problems.
The problem
From the localhost I cannot connect to SQL-Server, AND from any (2) other
W2K
Server in the same domain I cannot connect to SQL Server.
Here is the original error message, in german:
SQLState: '01000'
SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
Driver]& #91;SharedMemory]ConnectionOpen(SECDoCli
entHandshake())-
Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
[Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheits
fehler
Have you any hints for me? I worked since 5 Days on this Problem...
The solution:
THX
Markus
PS: my german is much better...
Sorry for dubbleposting,I have not seen this ng bevor.For local, perhaps Shared Memory driver is disabled? See server config
manager, sql server 2005 network configuration tab.
For remote win2K, check surface area config for Remote Connections - are
both tcp and named pipes enables?
Also you can go to the win2K machines and set up aliases using ODBC or
native client managers.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
> Hi ng!
> The facts:
> SQL Server 2005 is installed on a Windows 2003 server within a domain.
> Every
> XP-Clients can connect to SQL Server via ODBC without any problems.
> The problem
> From the localhost I cannot connect to SQL-Server, AND from any (2) other
> W2K
> Server in the same domain I cannot connect to SQL Server.
>
> Here is the original error message, in german:
> SQLState: '01000'
> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
> Driver]& #91;SharedMemory]ConnectionOpen(SECDoCli
entHandshake())-
> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherhei
tsfehler
>
> Have you any hints for me? I worked since 5 Days on this Problem...
> The solution:
> THX
> Markus
> PS: my german is much better...
> Sorry for dubbleposting,I have not seen this ng bevor.
>
>|||Shared Memory is disabled.
3 Clients are XP, there are all works fine
3 Servers 2K3 (2 of this are TS): nobody can connect the database
I am only use ODBC, no native client, only tcp is activ
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13krh3qgfmd58d8@.corp.supernews.com...
> For local, perhaps Shared Memory driver is disabled? See server config
> manager, sql server 2005 network configuration tab.
> For remote win2K, check surface area config for Remote Connections - are
> both tcp and named pipes enables?
> Also you can go to the win2K machines and set up aliases using ODBC or
> native client managers.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>|||Local connections on same box will attempt to use Shared Mem IIRC, so try
with it enabled.
You say you use only ODBC, but built-in sql server tools such as QA or SSMS
use whatever their default is set up to be, which could be named pipes. Try
forcibly setting the connection mechanism to tcp and see if it works.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
> Shared Memory is disabled.
> 3 Clients are XP, there are all works fine
> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
> I am only use ODBC, no native client, only tcp is activ
> Markus
>
> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
> news:13krh3qgfmd58d8@.corp.supernews.com...
>|||Hi Kevin!
SSMS with tcp/ip works.
I have try to connect via MSSMS to connect from a w2k3 serve to the other
w2k3 Server (SQL Server), this works.
The only thing is, I cannot connect via ODBC from local host or any other
W2k3 Server to my W2k3 Server with SQL 2005. I can connect from any XP
Workstion without problems.
The ODBC - Driver Config is the same on XP ans W2k3. I think the only
differnt ist the ODBC Driver Version:
On XP I use the follwing ODBC Driver: SQL Server V2000.85.1117.00
on W2K3 : 2000.86.3959.00
I am not use the native client, shared memory and tcp/ip is on, the rest
off, SQL Native Client: all is off
\\sqlserver\myprog is always map to s:\
myprog.exe and myprog.ini is always the same
My connection string looks like this (with and without integratet security):
DSN=MYPROG_MSSQL;Database=MYPROG
-or-
DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;
PWD=password
-or-
DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;
PWD=password;Trusted_Connection=No;E
ncrypt=No;
Any Ideas?
THX in advanced
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13krpmsnuutd460@.corp.supernews.com...
> Local connections on same box will attempt to use Shared Mem IIRC, so try
> with it enabled.
> You say you use only ODBC, but built-in sql server tools such as QA or
> SSMS use whatever their default is set up to be, which could be named
> pipes. Try forcibly setting the connection mechanism to tcp and see if it
> works.
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
>|||Sorry - I have exhausted my ideas on this one. Time to give MS Support a
call!
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:%23z4vCloMIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hi Kevin!
> SSMS with tcp/ip works.
>
> I have try to connect via MSSMS to connect from a w2k3 serve to the other
> w2k3 Server (SQL Server), this works.
> The only thing is, I cannot connect via ODBC from local host or any other
> W2k3 Server to my W2k3 Server with SQL 2005. I can connect from any XP
> Workstion without problems.
> The ODBC - Driver Config is the same on XP ans W2k3. I think the only
> differnt ist the ODBC Driver Version:
> On XP I use the follwing ODBC Driver: SQL Server V2000.85.1117.00
> on W2K3 : 2000.86.3959.00
> I am not use the native client, shared memory and tcp/ip is on, the rest
> off, SQL Native Client: all is off
>
> \\sqlserver\myprog is always map to s:\
> myprog.exe and myprog.ini is always the same
> My connection string looks like this (with and without integratet
> security):
> DSN=MYPROG_MSSQL;Database=MYPROG
> -or-
> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;
PWD=password
> -or-
> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;
PWD=password;Trusted_Connection=No
;Encrypt=No;
>
> Any Ideas?
> THX in advanced
> Markus
>
>
> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
> news:13krpmsnuutd460@.corp.supernews.com...
>|||Hi Kevin,
when I set my Programm "compatible with XP" (in Programm properties), then
the connection works!
But its not a real solution, so I have to connect from 2 Servers and the
property dialog for compatible mode is only availible on a local drive.
Any Ideas?
Thx
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13kui5qdav3mqed@.corp.supernews.com...
> Sorry - I have exhausted my ideas on this one. Time to give MS Support a
> call!
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:%23z4vCloMIHA.4712@.TK2MSFTNGP04.phx.gbl...
>
Tuesday, February 14, 2012
Cannot connect to localhost using Windows Security Group as login
I have a test environment set up at home with a small windows server 2003 Active Directory domain. I created a windows security group on the dc and added myself and another user to the group. I then use this group as a login for SQL Server and add the login to the sysadmin server role. This works exactly as I would expect on the Windows Server computer (which is also the Domain Controller) regardless of which computer I use to connect to this Windows Server computer. However, when I set up the exact same login on the local sql server instance of my client laptop running windows xp pro, the I get an error message (Login failed for user MYDOMAIN\dgolds...) when I attempt to connect to the local instance of SQL server, even though I am able to connect to the instance on the domain controller with no problems using this same client laptop under the same user account. The only way I am able to connect locally on the laptop under this account (which does not have local admin privileges on any box, for testing purposes) is to add the user account separately as a login, rather than as part of a group. I'm curious as to why being a member of a security group that is part of the sysadmin server role does not allow me to connect to the local instance of SQL Server on this client laptop. The windows server computer is running SQL2k5 Enterprise, and the client laptop is running SQL2k5 developer. Any insight into this would be appreciated.
Thanks,
Dave
Let's focus on the laptop for a moment, becuase that seems to be where your question is. Is all this true?
1. You have an instance of SQL Server on the laptop
2. You have a user (UserA) in a Windows group (GroupA)
3. The Windows Group (GroupA) has been added as a login to SQL Server as a Windows account
4. When UserA tries to log in to the local instance of SQL Server on the laptop, they can't get in
5. If you add UserA to the local Instance of SQL Server on the laptop, they can get in
Do I have all that right?
|||All of that is correct.
Thanks,
-Dave
|||Then let me ask a few more questions:
1. Is the user a domain Windows user?
2. Which service accounts did you use to start SQL Server on the laptop? Are they starting with a user account or the localsystem account?
|||The user is a domain Windows user. Originally the laptop was using the local system account as its service account, but I thought that might be the problem so I tried using the same service account (a domain user account that I configured specifically as a SQL Server Service Account) that I use on the server, but unfortunately I got the same results.
Thanks,
-Dave
|||OK - I think we're getting closer. I'm going to assume the laptop is on the domain, since you say you've added that Windows group to SQL Server as a login. Does the account that you are starting SQL Server with on the laptop have the ability to resolve network names?
To help investigate your problem, make sure you check the logs the system creates. You can read more about that here:
http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1
|||The laptop is definitely on the domain. As far as the account that I am starting SQL Server with on the laptop having the ability to resolve network names, I'm not sure-how would I find that out?
Thanks,
Dave
|||I'm sure there's an easier way, but I normally just log on as that user, create a local group and then try to add someone from the domain to that local group.|||Hi,
The SQL Server Service Account that I'm using does have the ability to resolve network names on the laptop.
Thanks,
-Dave
|||Very odd. At this point, it sounds like you're doing everything properly. It has to be something to do with the security policies on that machine, but without access to it I'm afraid it would take a lot of back-and-forth to figure out where it is. I would suggest checking the logs for the system, using the techniques I outline in this guide:
http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1
If that doesn't help point out the issue, then you may have to open a support call so that someone can gain access to your machine. sorry that I couldn't be more help here.
|||Dave, I don't know if this will help, but could you check the error message for the login failure in the ERRORLOG file and post here the two lines that describe the state and message of the error?
Thanks
Laurentiu
Thanks for all the suggestions. It turns out that there was something going on with this group (I'm not sure what). I created another group in the same Active Directory location with the same users as members and it works fine.
Thanks,
-Dave
Cannot connect to localhost using Windows Security Group as login
I have a test environment set up at home with a small windows server 2003 Active Directory domain. I created a windows security group on the dc and added myself and another user to the group. I then use this group as a login for SQL Server and add the login to the sysadmin server role. This works exactly as I would expect on the Windows Server computer (which is also the Domain Controller) regardless of which computer I use to connect to this Windows Server computer. However, when I set up the exact same login on the local sql server instance of my client laptop running windows xp pro, the I get an error message (Login failed for user MYDOMAIN\dgolds...) when I attempt to connect to the local instance of SQL server, even though I am able to connect to the instance on the domain controller with no problems using this same client laptop under the same user account. The only way I am able to connect locally on the laptop under this account (which does not have local admin privileges on any box, for testing purposes) is to add the user account separately as a login, rather than as part of a group. I'm curious as to why being a member of a security group that is part of the sysadmin server role does not allow me to connect to the local instance of SQL Server on this client laptop. The windows server computer is running SQL2k5 Enterprise, and the client laptop is running SQL2k5 developer. Any insight into this would be appreciated.
Thanks,
Dave
Let's focus on the laptop for a moment, becuase that seems to be where your question is. Is all this true?
1. You have an instance of SQL Server on the laptop
2. You have a user (UserA) in a Windows group (GroupA)
3. The Windows Group (GroupA) has been added as a login to SQL Server as a Windows account
4. When UserA tries to log in to the local instance of SQL Server on the laptop, they can't get in
5. If you add UserA to the local Instance of SQL Server on the laptop, they can get in
Do I have all that right?
|||All of that is correct.
Thanks,
-Dave
|||Then let me ask a few more questions:
1. Is the user a domain Windows user?
2. Which service accounts did you use to start SQL Server on the laptop? Are they starting with a user account or the localsystem account?
|||The user is a domain Windows user. Originally the laptop was using the local system account as its service account, but I thought that might be the problem so I tried using the same service account (a domain user account that I configured specifically as a SQL Server Service Account) that I use on the server, but unfortunately I got the same results.
Thanks,
-Dave
|||OK - I think we're getting closer. I'm going to assume the laptop is on the domain, since you say you've added that Windows group to SQL Server as a login. Does the account that you are starting SQL Server with on the laptop have the ability to resolve network names?
To help investigate your problem, make sure you check the logs the system creates. You can read more about that here:
http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1
|||The laptop is definitely on the domain. As far as the account that I am starting SQL Server with on the laptop having the ability to resolve network names, I'm not sure-how would I find that out?
Thanks,
Dave
|||I'm sure there's an easier way, but I normally just log on as that user, create a local group and then try to add someone from the domain to that local group.|||Hi,
The SQL Server Service Account that I'm using does have the ability to resolve network names on the laptop.
Thanks,
-Dave
|||Very odd. At this point, it sounds like you're doing everything properly. It has to be something to do with the security policies on that machine, but without access to it I'm afraid it would take a lot of back-and-forth to figure out where it is. I would suggest checking the logs for the system, using the techniques I outline in this guide:
http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1
If that doesn't help point out the issue, then you may have to open a support call so that someone can gain access to your machine. sorry that I couldn't be more help here.
|||Dave, I don't know if this will help, but could you check the error message for the login failure in the ERRORLOG file and post here the two lines that describe the state and message of the error?
Thanks
Laurentiu
Thanks for all the suggestions. It turns out that there was something going on with this group (I'm not sure what). I created another group in the same Active Directory location with the same users as members and it works fine.
Thanks,
-Dave
Cannot connect to localhost using Windows Security Group as login
I have a test environment set up at home with a small windows server 2003 Active Directory domain. I created a windows security group on the dc and added myself and another user to the group. I then use this group as a login for SQL Server and add the login to the sysadmin server role. This works exactly as I would expect on the Windows Server computer (which is also the Domain Controller) regardless of which computer I use to connect to this Windows Server computer. However, when I set up the exact same login on the local sql server instance of my client laptop running windows xp pro, the I get an error message (Login failed for user MYDOMAIN\dgolds...) when I attempt to connect to the local instance of SQL server, even though I am able to connect to the instance on the domain controller with no problems using this same client laptop under the same user account. The only way I am able to connect locally on the laptop under this account (which does not have local admin privileges on any box, for testing purposes) is to add the user account separately as a login, rather than as part of a group. I'm curious as to why being a member of a security group that is part of the sysadmin server role does not allow me to connect to the local instance of SQL Server on this client laptop. The windows server computer is running SQL2k5 Enterprise, and the client laptop is running SQL2k5 developer. Any insight into this would be appreciated.
Thanks,
Dave
Let's focus on the laptop for a moment, becuase that seems to be where your question is. Is all this true?
1. You have an instance of SQL Server on the laptop
2. You have a user (UserA) in a Windows group (GroupA)
3. The Windows Group (GroupA) has been added as a login to SQL Server as a Windows account
4. When UserA tries to log in to the local instance of SQL Server on the laptop, they can't get in
5. If you add UserA to the local Instance of SQL Server on the laptop, they can get in
Do I have all that right?
|||All of that is correct.
Thanks,
-Dave
|||Then let me ask a few more questions:
1. Is the user a domain Windows user?
2. Which service accounts did you use to start SQL Server on the laptop? Are they starting with a user account or the localsystem account?
|||The user is a domain Windows user. Originally the laptop was using the local system account as its service account, but I thought that might be the problem so I tried using the same service account (a domain user account that I configured specifically as a SQL Server Service Account) that I use on the server, but unfortunately I got the same results.
Thanks,
-Dave
|||OK - I think we're getting closer. I'm going to assume the laptop is on the domain, since you say you've added that Windows group to SQL Server as a login. Does the account that you are starting SQL Server with on the laptop have the ability to resolve network names?
To help investigate your problem, make sure you check the logs the system creates. You can read more about that here:
http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1
|||The laptop is definitely on the domain. As far as the account that I am starting SQL Server with on the laptop having the ability to resolve network names, I'm not sure-how would I find that out?
Thanks,
Dave
|||I'm sure there's an easier way, but I normally just log on as that user, create a local group and then try to add someone from the domain to that local group.|||Hi,
The SQL Server Service Account that I'm using does have the ability to resolve network names on the laptop.
Thanks,
-Dave
|||Very odd. At this point, it sounds like you're doing everything properly. It has to be something to do with the security policies on that machine, but without access to it I'm afraid it would take a lot of back-and-forth to figure out where it is. I would suggest checking the logs for the system, using the techniques I outline in this guide:
http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1
If that doesn't help point out the issue, then you may have to open a support call so that someone can gain access to your machine. sorry that I couldn't be more help here.
|||Dave, I don't know if this will help, but could you check the error message for the login failure in the ERRORLOG file and post here the two lines that describe the state and message of the error?
Thanks
Laurentiu
Thanks for all the suggestions. It turns out that there was something going on with this group (I'm not sure what). I created another group in the same Active Directory location with the same users as members and it works fine.
Thanks,
-Dave
Cannot connect to localhost using Windows Security Group as login
I have a test environment set up at home with a small windows server 2003 Active Directory domain. I created a windows security group on the dc and added myself and another user to the group. I then use this group as a login for SQL Server and add the login to the sysadmin server role. This works exactly as I would expect on the Windows Server computer (which is also the Domain Controller) regardless of which computer I use to connect to this Windows Server computer. However, when I set up the exact same login on the local sql server instance of my client laptop running windows xp pro, the I get an error message (Login failed for user MYDOMAIN\dgolds...) when I attempt to connect to the local instance of SQL server, even though I am able to connect to the instance on the domain controller with no problems using this same client laptop under the same user account. The only way I am able to connect locally on the laptop under this account (which does not have local admin privileges on any box, for testing purposes) is to add the user account separately as a login, rather than as part of a group. I'm curious as to why being a member of a security group that is part of the sysadmin server role does not allow me to connect to the local instance of SQL Server on this client laptop. The windows server computer is running SQL2k5 Enterprise, and the client laptop is running SQL2k5 developer. Any insight into this would be appreciated.
Thanks,
Dave
Let's focus on the laptop for a moment, becuase that seems to be where your question is. Is all this true?
1. You have an instance of SQL Server on the laptop
2. You have a user (UserA) in a Windows group (GroupA)
3. The Windows Group (GroupA) has been added as a login to SQL Server as a Windows account
4. When UserA tries to log in to the local instance of SQL Server on the laptop, they can't get in
5. If you add UserA to the local Instance of SQL Server on the laptop, they can get in
Do I have all that right?
|||All of that is correct.
Thanks,
-Dave
|||Then let me ask a few more questions:
1. Is the user a domain Windows user?
2. Which service accounts did you use to start SQL Server on the laptop? Are they starting with a user account or the localsystem account?
|||The user is a domain Windows user. Originally the laptop was using the local system account as its service account, but I thought that might be the problem so I tried using the same service account (a domain user account that I configured specifically as a SQL Server Service Account) that I use on the server, but unfortunately I got the same results.
Thanks,
-Dave
|||OK - I think we're getting closer. I'm going to assume the laptop is on the domain, since you say you've added that Windows group to SQL Server as a login. Does the account that you are starting SQL Server with on the laptop have the ability to resolve network names?
To help investigate your problem, make sure you check the logs the system creates. You can read more about that here:
http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1
|||The laptop is definitely on the domain. As far as the account that I am starting SQL Server with on the laptop having the ability to resolve network names, I'm not sure-how would I find that out?
Thanks,
Dave
|||I'm sure there's an easier way, but I normally just log on as that user, create a local group and then try to add someone from the domain to that local group.|||Hi,
The SQL Server Service Account that I'm using does have the ability to resolve network names on the laptop.
Thanks,
-Dave
|||Very odd. At this point, it sounds like you're doing everything properly. It has to be something to do with the security policies on that machine, but without access to it I'm afraid it would take a lot of back-and-forth to figure out where it is. I would suggest checking the logs for the system, using the techniques I outline in this guide:
http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1
If that doesn't help point out the issue, then you may have to open a support call so that someone can gain access to your machine. sorry that I couldn't be more help here.
|||Dave, I don't know if this will help, but could you check the error message for the login failure in the ERRORLOG file and post here the two lines that describe the state and message of the error?
Thanks
Laurentiu
Thanks for all the suggestions. It turns out that there was something going on with this group (I'm not sure what). I created another group in the same Active Directory location with the same users as members and it works fine.
Thanks,
-Dave
Cannot connect to localhost from "Server Explorer" in Visual Studio 2005.
hi ,
I am trying to connect to my local SQL server 2005 from "Server Explorer" but it is giving the error of "Remote Connectons" not allowed.
I am using "windows authentication" login.
My SQLExpress and SQLExpress browser are running from "SQL server configuration manager".
If i use a "App.Config" file to connect to database, the SQl connection can open and i can run the stored procedure.... but cannot access the database on my local machine.
Please help.
thanks for reply.
With regards,
Girish.
Hi Girish,
by default all remote connections are disabled. Open sql server configuration manager and enable the appropriate type of connection. (... and take a look at your windows firewall on your local machine!)
CU
tosc
|||Can you post your connection string and the exact error message?|||An error has occured while establishing a connection to the server. When connection to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server|||Hi Girish,
there is a post at SQL Protocol which might helps: http://blogs.msdn.com/sql_protocols/archive/2007/03/31/named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server.aspx
CU
tosc
|||You did not post the whole error message, the part you omitted contains most important part of this error message, it's a winerr code.
What's your connection string? Did you put .\sqlexpress or only .? You should use .\sqlexpress.
|||Done ... thanks for the help.
With regards,
Girish
Cannot connect to localhost from "Server Explorer" in Visual Studio 2005.
hi ,
I am trying to connect to my local SQL server 2005 from "Server Explorer" but it is giving the error of "Remote Connectons" not allowed.
I am using "windows authentication" login.
My SQLExpress and SQLExpress browser are running from "SQL server configuration manager".
If i use a "App.Config" file to connect to database, the SQl connection can open and i can run the stored procedure.... but cannot access the database on my local machine.
Please help.
thanks for reply.
With regards,
Girish.
Hi Girish,
by default all remote connections are disabled. Open sql server configuration manager and enable the appropriate type of connection. (... and take a look at your windows firewall on your local machine!)
CU
tosc
|||Can you post your connection string and the exact error message?|||An error has occured while establishing a connection to the server. When connection to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server|||Hi Girish,
there is a post at SQL Protocol which might helps: http://blogs.msdn.com/sql_protocols/archive/2007/03/31/named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server.aspx
CU
tosc
|||You did not post the whole error message, the part you omitted contains most important part of this error message, it's a winerr code.
What's your connection string? Did you put .\sqlexpress or only .? You should use .\sqlexpress.
|||Done ... thanks for the help.
With regards,
Girish
Sunday, February 12, 2012
Cannot connect to localhost
If I try to connect to localhost in the connection manager I get the error
"Test connection failed because of an error in initialising provider. Login timeout expired."
If I try to connect using server/instance in the connection mananger however, it connects just fine.
Any ideas?
Gary
hi Gary,
if you installed a named instance as it seems (server\Instance) you will not be able to just use "localhost".. you have to provide the full instance name, thus ServerName\InstanceName or "(Local)\InstanceName" or whatever... but the instancename must be provided as well..
regards
cannot connect to http://localhost/ReportServer
how to give deploy roles using Report Manager
--
Message posted via http://www.sqlmonster.comUser that will be deploying reports need to have publisher permissions for RS.
"pavan kumar via SQLMonster.com" wrote:
> how to give deploy roles using Report Manager
> --
> Message posted via http://www.sqlmonster.com
>|||how to give permissions using rsconfig. its giving an error that 'report
server is not found'
--
Message posted via http://www.sqlmonster.com
--
Message posted via http://www.sqlmonster.comUser that will be deploying reports need to have publisher permissions for RS.
"pavan kumar via SQLMonster.com" wrote:
> how to give deploy roles using Report Manager
> --
> Message posted via http://www.sqlmonster.com
>|||how to give permissions using rsconfig. its giving an error that 'report
server is not found'
--
Message posted via http://www.sqlmonster.com
Subscribe to:
Posts (Atom)