July 11, 2003 at 12:23 pm
Hey Brian,
Yep same problem. Can't be a firewall issue or I wouldn't see the entry in the event log on the server right? Are there firewall rules that say forget what he's passing and just take his domain creditials?
quote:
What happens if you try and connect as sa using Query Analyzer from the client? Same issue?K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
John Zacharkan
John Zacharkan
July 11, 2003 at 12:25 pm
Okay. What happens if you fire up QA and use the sa account from a client in Domain A?
Trying to narrow this down.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
July 11, 2003 at 12:32 pm
Are you sure the client security is set up for SQL Server and NT?
All the best,
Dale
Author: An Introduction to SQL Server 2005 Management Studio
July 11, 2003 at 12:33 pm
I have MSDE 8.00.194 installed. which also includes of course the tools.
Should also mention that it looks like it tries to register 3 times before failing - so I get the same two errors 3 times.
quote:
Nevermind. I just got it. Are you referring to Enterprise Manager? Did you install client tools?
John Zacharkan
John Zacharkan
July 11, 2003 at 12:35 pm
I tried the sa same problem
quote:
Okay. What happens if you fire up QA and use the sa account from a client in Domain A?Trying to narrow this down.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
John Zacharkan
John Zacharkan
July 11, 2003 at 12:37 pm
yes, I am very sure it is setp otherwise my web apps wouldn't be working. And yeah I look just to be safe.
quote:
Are you sure the client security is set up for SQL Server and NT?
John Zacharkan
John Zacharkan
July 11, 2003 at 12:38 pm
Wait I'll try that, miss understood your question
quote:
I tried the sa same problemquote:
Okay. What happens if you fire up QA and use the sa account from a client in Domain A?Trying to narrow this down.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
John Zacharkan
John Zacharkan
John Zacharkan
July 11, 2003 at 12:41 pm
Okay, if you've got other SQL Server logins connecting successfully, have you verified the sa password? For instance, can you terminal into the server and login? You'll avoid IPSec or anything else that might be a barrier because you'll be using shared memory.
If you don't have other SQL Server logins connecting successfully, verify mixed, stop and restart the SQL Server service.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
July 11, 2003 at 12:48 pm
Ready for a real tail spin, On a computer that is not part of any domain, it's a workgroup I'm able to connect/register with the sa account.
John Zacharkan
John Zacharkan
July 11, 2003 at 12:49 pm
quote:
Ready for a real tail spin, On a computer that is not part of any domain, it's a workgroup I'm able to connect/register with the sa account. Different OS xp proJohn Zacharkan
John Zacharkan
John Zacharkan
July 11, 2003 at 12:49 pm
This URL is excellent for verifying your MSDE set up and SQL Server Login authentication. It might be worth checking out:
http://www.highpoint.edu/~rheiges/CIS430/MSDE%20Setup%20Notes.doc
All the best,
Dale
Author: An Introduction to SQL Server 2005 Management Studio
July 11, 2003 at 12:51 pm
Extremely odd. Not sure why it's forcing you to Windows authentication regardless. That doesn't make a whole lot of sense.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
July 11, 2003 at 12:57 pm
I hope I'm not throwing things way off base here but I just found this. It seemed weird enough to mention:
quote:
I was running MSDE and it had web access. Recently, the login to my SQL Server changed. What happened?You could have been attacked by the SQLSpida worm. This worm attacks SQL Server instances and MSDE installations with an sa login of no password. Basically, the worm changes the password for the sa login. If you use the sa login to gain access to your MSDE, the approach can lock you out.
You need to change the password for the sa login. The short-term solution is to change the password for the sa login to one that you set. This will let you login again.
All the best,
Dale
Author: An Introduction to SQL Server 2005 Management Studio
July 11, 2003 at 1:00 pm
No, it's not SPIDA. Had it been, he wouldn't have been able to log on as SA from another system, which he was able to do. Spida changes the password and attacks the sa account when no password is set.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
July 11, 2003 at 1:02 pm
A network trace would be real handy right now... Are you or do you have anyone capable of sorting through one? Is Network Monitor set up on the server in question?
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
Viewing 15 posts - 16 through 30 (of 36 total)
You must be logged in to reply to this topic. Login to reply