Cannot Connect to SQL Server 2000 using Windows XP Pro account login info

When I try to create a System DSN connection to our SQL Server 2000
database that is installed on a Windows 2000 machine, I keep on
getting the following error:
Connection failed:
SQLState: '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
We do not have IIS or any web server installed on the database server
machine or the Windows XP Professional machine that is trying to
connect to the Windows 2000 machine. The machines can all see each
other, and we are actually have the machines networked via the
Workgroup setting, not using the Domain setting. Anyone have any ideas
as to what can be the issue?
Thanks,
Jay
(patel@.cs.utk.edu)Hi Patel,
Since you're not in a domain, Windows Authentication works very
differently. Windows Authentication is commonly used while you're in a
domain and the client has been authenticated on the domain. The error
message "null" indicates that we're unable to "impersonate" the client in
order to make a Windows Authenticated connection.
You have two optioins.
1. Duplicate the nt username & password on both machines and Use Named
Pipes to Connect.
2. Use SQL Standard Security instead of using Windows Authentication.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
How do I create a named pipe? I am not sure as to how to do that.
-Jay
(patel@.cs.utk.edu)
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||Named pipes are not created, but rather enabled - with both the
Client and Server Network Utilities.
For the Client Network Utility, start it by Start>Run>cliconfg.exe.
The left pane shows disabled protocols. The right pane shows enabled
protocols. In the left pane, click on Named Pipes and then use the
Enable button between the two panes.
For the Server Network Utility (at least for an MSDE version) find the
file SVRNETCN.EXE. Double click to start and the perform the same
actions as in the Client Network Utility, but for the server instance
in question. If you have installed the server as the default instance,
it will have no name, so its just the computer name that will appear
in the server name pull-down list.
If you have a firewall installed on the machines in question, please
say so, since there will be rules to create to open ports if you have
not done so already.
You should also see the article:
Potential causes of the "SQL Server does not exist or access denied"
error message
http://support.microsoft.com/defaul...306&Product=sql
Lou Arnold
Ottawa, Canada.
On Wed, 21 Jul 2004 21:15:32 -0700, Jay Patel <patel@.cs.utk.edu>
wrote:

>Kevin,
> How do I create a named pipe? I am not sure as to how to do that.
>-Jay
>(patel@.cs.utk.edu)
>*** Sent via Developersdex http://www.codecomments.com ***
>Don't just participate in USENET...get rewarded for it!|||Kevin,
Your option 1 below implies that you need Named pipes if you have no
domain controller and want Windows Authentication mode. Is that
correct' If so, is this requirement documented somewhere?
Lou Arnold
On Thu, 22 Jul 2004 00:31:06 GMT, kevmc@.online.microsoft.com (Kevin
McDonnell [MSFT]) wrote:

>Hi Patel,
> Since you're not in a domain, Windows Authentication works very
>differently. Windows Authentication is commonly used while you're in a
>domain and the client has been authenticated on the domain. The error
>message "null" indicates that we're unable to "impersonate" the client in
>order to make a Windows Authenticated connection.
>You have two optioins.
>1. Duplicate the nt username & password on both machines and Use Named
>Pipes to Connect.
>2. Use SQL Standard Security instead of using Windows Authentication.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and confers no rights.
>
>