|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Cannot connect to SQL Server from localhost (no problem from any xp client)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. -- Show quoteKevin 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 Show quote "TheSQLGuru" <kgbo***@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. -- Show quoteKevin 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" <kgbo***@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 Show quote "TheSQLGuru" <kgbo***@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" <kgbo***@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. >>>> >>>> >>>> >>> >>> >> >> > >  |
|||||||||||||||||||||||
Other interesting topics