-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, 12 Jan 2004, Jason Jeremias wrote:
I upgraded from Samba 2.2.8a to Samba 3.0.1, since doing I'm having problems with my SQL Server and applications running on Windows 2000. When a users (running a windows 98 client) attempts to query the SQL Server, either using ODBC (even the Test Sources) or an application that uses the db. I get a login failed from the sql app, and from the ODBC I get:
"Login failed for user '(null)', Reason: Not associated with a trusted SQL Server connection."
That error shows up in the SQL Server Logs, and its displayed at the client.
On the Samba side I see some NT user token: (NULL), in the logs but I'm not sure what else to look for..
I'm not sure what is going on but it seems like the W2k/SQL Server is not doing the Windows Authentication properly.
I've attached a testparm -vs and my smb.conf, I can provide logs or whatever is needed to help me solve the problem.
This might have been fixed in 3.0.2rc1. Could you test it and let me know? Thanks.
cheers, jerry ---------------------------------------------------------------------- Hewlett-Packard ------------------------- http://www.hp.com SAMBA Team ---------------------- http://www.samba.org GnuPG Key ---- http://www.plainjoe.org/gpg_public.asc "If we're adding to the noise, turn off this song" --Switchfoot (2003)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFADfNnIR7qMdg1EfYRAkFoAKCff/H0oUzBtDjbwmE9t+ui0dywWgCgg6bW UHPy7wlSJSoU00iHb0Z1CkI= =xwtN -----END PGP SIGNATURE-----
-- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
