Hi Corey,

In the web reports, if you select 'Event -> Event Search' do those three new systems, show up showing events from within the last 24 hours? This will tell us if those systems can reach the database or if we have a bigger problem.

Hi Steve,

No they do not show up. Next steps?

Which database are you using? Mssql or mysql?

You could run the self support utility on one of the hosts (there is a link in the support section of eventsentry.com) and see if that reports any issues.

Finally, are you receiving alerts from those hosts?

ms sql. I am not receiving alerts from them. i will try the self support utility if i can find it.

OK, this rules out any issues with the database ODBC drivers, since MSSQL drivers are included by default.

It would appear as if the link to that utility has been moved (I am looking into this), however, the self support utility should be installed on your computer and a link should exist in the start menu.

Please let me know if do not have it.

i found the utility off the main public page. Here are the results:

Unable to connect to database action "MSSQL Database" due to the following error: [08001] [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied. (17)

I CAN ping the sql server from the client computers that are having trouble. Could this still mean a possible firewall issue? These two servers in a dmz network, but the agent installs just fine to these machines and reports and shows up successfully in the ES console.

Is the traffic sent and received on port 1433?

PS. Here is the link I found to the support utility:
http://test.eventsentry.com/support_kb_search.php

Hi Corey,

This sounds like it may be a firewall related issue since you've got other machines writing to the database. From one of the remote machines, could you attempt to telnet to your database machine. Since you mentioned that these are 2k8 machine, you'll need to install the 'Telnet Client' by going to Control Panel > Programs and Features > Turn Windows features on or off, and select the 'Telnet Client'. Then from the command prompt, you can do a telnet to the database server:

telnet {servername} 1433

What do you see when you do this? Do you receive a blinking cursor?

appears 1433 is currently blocked since it wont connect yet i can telnet to other machines from one of these hosts. my next question then, is opening just 1433 enough? I may be mistaken but if memory serves me I thought SQL iniated a connection on 1433 but then uses a random port for the client to server communication. Is that accurate? Anyway to tie to traffic down to use only 1433 instead of a whole range of ports?

Opening port 1433 should be sufficient. SQL Server does not use random ports. Other MS products do this (I believe Exchange Server), but opening the port SQL Server is listening on should work.

Hi Corey,

The SQL server (destination server) would receive on the standard port 1433 because that is what MSSQL server is configured for.

A random port will be used by the remote system (sending system) picked out of ports that are available on that system. Since this would be an outgoing port for that system there typically would not be any firewall issues.

Thanks guys. Will have this change made and report back when completed.

port 1433 opened and everything appears well now. The server show under Event Search in Web Reports now, as well as have a computer object that can be monitored on the dashboard. I was informed there were no restrictions. Apparently not the case.

Thanks for helping me narrow it down guys.

Thanks for the update Corey,
Glad you were able to get this working.