Cannot connect in mixed mode after installing SQL2K on client
From: Carl Olsson (caos_at_regerar.com)
Date: 11/22/04
- Next message: PerFry: "Re: Local named pipes better than TCP/IP?"
- Previous message: Mike Epprecht (SQL MVP): "RE: Bind failed on TCP port 1044."
- Next in thread: Rand Boyd [MSFT]: "RE: Cannot connect in mixed mode after installing SQL2K on client"
- Reply: Rand Boyd [MSFT]: "RE: Cannot connect in mixed mode after installing SQL2K on client"
- Messages sorted by: [ date ] [ thread ]
Date: 22 Nov 2004 03:44:18 -0800
Server: W2K server with SQL 7.0, all WU patches applied
Client: W2K professional, all WU patches applied
I have an application that resides entirely on the server, only a
shortcut is installed on the client. It connects to SQL using mixed
mode authentication.
When I installed SQL server 2000 (that is, as much of it as it is
possible to install on a non-server W2K) on my client I no longer
could connect to the server. The error message from the app said I had
no access to the server. I haven't written this app myself so I do not
know what the connection string looks like.
I can still connect successfully from another computer.
Nobody that signs on to my computer can connect.
I know SQL 2000 defaults to using trusted mode authentication but does
it also prevent usage of mixed mode? Sounds too weird to be true...
Better suggestions, anyone?
- Next message: PerFry: "Re: Local named pipes better than TCP/IP?"
- Previous message: Mike Epprecht (SQL MVP): "RE: Bind failed on TCP port 1044."
- Next in thread: Rand Boyd [MSFT]: "RE: Cannot connect in mixed mode after installing SQL2K on client"
- Reply: Rand Boyd [MSFT]: "RE: Cannot connect in mixed mode after installing SQL2K on client"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|