SQL Server 2005 connection problems

Hello!

I am having problems connecting to SQL server time to time.
In event log I keep getting msg like this:
Login failed for user 'sa'. [CLIENT: 192.168.x.x]

The user name is different in other msgs.

When I check the settings all is ok...all ports are enabled, all agents started...
Sometimes the problem goes away in few seconds. Sometimes the only thing to make it work is to reboot the WIN server and then its ok again.

I also checked log file for SQL server and I see errors like:
Message
[165] ODBC Error: 0, Driver's SQLAllocHandle on SQL_HANDLE_ENV failed [SQLSTATE IM004]
Message
[382] Logon to server 'SERVER' failed (SaveAllSchedules)

I am using Windows Small Business Server 2003 Premium Edition with SQL Server 2005 standard.

Thanks for suggestions!
celjan79Asked:
Who is Participating?
 
celjan79Connect With a Mentor Author Commented:
The problem was in one software which was running in background.
0
 
mcv22Commented:
It appears to be unauthorized access attempts to the SQL server. If this machine is externally accessible using public IP, consider using a firewall and blocking ports 1443, 1444 on that server from the external network.
0
 
celjan79Author Commented:
I dont allow external access to SQL and I do block all this ports.
0
2018 Annual Membership Survey

Here at Experts Exchange, we strive to give members the best experience. Help us improve the site by taking this survey today! (Bonus: Be entered to win a great tech prize for participating!)

 
mcv22Commented:
Try running a SQL profiler trace to audit login events and try to see what applications/processes are trying to login to your server from those IPs.
0
 
celjan79Author Commented:
I know which apps are trying to login because thats why the problem was found. When you try to run app you get run time error and login failed to SQL. Sometimes I get error that maybe SQL server isnt avaliable.

But if I wish to check other logins - how is this SQL profiler trace setting done?
0
 
mcv22Commented:
More info about SQL Profiler here : http://msdn.microsoft.com/en-us/library/ms187929%28v=SQL.90%29.aspx

The events you should be capturing can be found under Security Audit. Audit login and Audit login failed.
0
All Courses

From novice to tech pro — start learning today.