Mr Clevver
Idiot Savant
- Local time
- Today, 22:56
- Joined
- Jun 26, 2008
- Messages
- 17
[Solved] - See solution at the bottom
Hi all,
We have an Access based system that connects to SQL Server 2000 through ODBC. Most of the client PCs use XP, and this all works fine. We recently, however, bought a couple of Win7 PCs and I'm having more than a little trouble setting up the DSN for the OSBN connection.
Usually, on the XP PCs, I would log onto the SQLserver PC through My Network, and save the username and password when it asks me for them. I would then setup a DSN for the connection using the "With Windows NT Authentication using network login ID" option, and this would all work fine.
On the Windows 7 PCs this produced an error "Login failed for user '(null)'. Reason: Not associated with a trusted SQL server connection."
It does connect if I change the client configuration from TCP/IP, to Named Pipes, but I'm not keen on the idea of having different connection types across various clients, and I'd rather know why it's suddenly not working.
I have tried changing the SQL server to Mixed Mode, but it hasn't made a difference.
[/solved]
I got around this simply by installing SQL Native Client, as opposed to the SQL Server that comes with Win7, out of the box
Hi all,
We have an Access based system that connects to SQL Server 2000 through ODBC. Most of the client PCs use XP, and this all works fine. We recently, however, bought a couple of Win7 PCs and I'm having more than a little trouble setting up the DSN for the OSBN connection.
Usually, on the XP PCs, I would log onto the SQLserver PC through My Network, and save the username and password when it asks me for them. I would then setup a DSN for the connection using the "With Windows NT Authentication using network login ID" option, and this would all work fine.
On the Windows 7 PCs this produced an error "Login failed for user '(null)'. Reason: Not associated with a trusted SQL server connection."
It does connect if I change the client configuration from TCP/IP, to Named Pipes, but I'm not keen on the idea of having different connection types across various clients, and I'd rather know why it's suddenly not working.
I have tried changing the SQL server to Mixed Mode, but it hasn't made a difference.
[/solved]
I got around this simply by installing SQL Native Client, as opposed to the SQL Server that comes with Win7, out of the box
Last edited:
