Re: SQL Server Error: 1326 --> Interesting Finding
From: Jasper Smith (jasper_smith9@hotmail.com)
Date: 06/11/02
- Next message: mark: "Linked Server Login Mapping - strange thing..."
- Previous message: Lour: "Re: Remote Server vs. Linked Server"
- In reply to: Praveen: "SQL Server Error: 1326 --> Interesting Finding"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Jasper Smith" <jasper_smith9@hotmail.com> Date: Tue, 11 Jun 2002 18:52:16 +0100
Use TCP/IP as default client network library
The question you need to ask is why the users
can't connect to IPC$ on the server - what
kind of network is it - why can't the clients be
authenticated to the server ?
Error 1326 means "Logon failure: unknown user
name or bad password."
You can use makepipe and readpipe utilities to
troubleshoot . See BOL for details, also
INF: Readpipe Return Codes (Q110905)
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q110905
INF: Procedure for Testing Named Pipes (Q68941)
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q68941
HTH
Jasper Smith
"Praveen" <Praveen.Balakrishnan@lntinfotech.com> wrote in message
news:be9f01c21106$3aac1fb0$36ef2ecf@tkmsftngxa12...
> Hi,
> I've a problem..
>
> I want to import a few tables from SQL Server 2000
> database into a Access97 database.
>
> At the client end, I'm running Windows NT 4.0 workstation.
> Here, I have created a DSN to the SQL Server.
>
> I've opened the Access97 database on my client machine and
> I'm trying to import the tables.
>
> When I select the DSN (by Microsoft Access->File->Get
> External Data->Import->[Select FileType as ODBC]->[Select
> my DSN].. the SQL Server Login dialog appears and prompts
> for Username and password
>
> When I try to give a valid UserName and password (say bob
> and bob), it gives the error "Connection Failed: SQL
> Server Error: 1326 -
> [Microsoft][ODBC SQL Server Driver][dbnmpntw]Connection
> Open (CreateFile()).
>
> I'm giving a valid Username and password that exists on
> the Windows 2000 Server that is running the SQLServer.
>
> The funniest thing that is happening here is.. I goto
> Start->Run and give \\<My SQL Server Name, it asks for
> username and password.. and I give the same username and
> password (ie bob and bob) and it happily connects and
> shows me the list of available shares..
>
> Now, I come back to the SQLServer Login dialog and re-type
> the same username and password and Bingo.. I've now the
> list of all tables..
>
> What exactly happened during this time ?
>
> What could this mean.. ? I believe it has got something to
> do with Named pipes or something.. and I found a related
> article in the Microsoft knowledgebase.. they've given 3
> workarounds.. that are practically IMPRACTICAL to
> implement.. they say that "create identical
> usernames/passwords on each of the client systems".. Come
> on man.. I've 100's of clients that are running the client
> software.. It's just not possible to go and create one
> bob/bob on each client.. ha ha..
>
> Please somebody.. H E L P !!!!
>
> Is there a good workaround ?
>
> Hope I'm clear..
>
> thanx in advance,
>
> Praveen
> [Praveen.Balakrishnan@lntinfotech.com]
>
- Next message: mark: "Linked Server Login Mapping - strange thing..."
- Previous message: Lour: "Re: Remote Server vs. Linked Server"
- In reply to: Praveen: "SQL Server Error: 1326 --> Interesting Finding"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
