<html><head><style type="text/css">body {word-wrap: break-word; background-color:#ffffff;}</style></head><body><div style="font-family: sans-serif; font-size: 16px">Yes it was the same machine. I will load wireshark and see.<br><br>Shawn Cannon | NW Systems Administrator, Sr.<br>SSCP, MCITP, VCP3/4, EMCISA<br>Gladiator Technology, A ProfitStars® Solution<br><a href="tel:11395">11395</a> Old Roswell Rd | Alpharetta, GA <a href="tel:30009">30009</a><br>Office: (877) GLADTECH x<a href="tel:458190">458190</a> | Fax: <a href="tel:6784614625">(678) 461-4625</a><br>Direct: <a href="tel:6782424902">(678) 242-4902</a> | Mobile: <a href="tel:6786893700">(678) 689-3700</a><br><a href="http://www.gladiatortechnology.com">Http://www.gladiatortechnology.com</a></div><br><br>-----Original message-----<br><blockquote style="; border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><div style="font-family: sans-serif; font-size: 14px"><b>From: </b>Matthew Hall <mhall@mhcomputing.net><b><br>To: </b>Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu><b><br>Sent: </b>Mon, Dec 13, 2010 18:17:38 GMT+00:00<b><br>Subject: </b>Re: [syslog-ng] Microsoft SQL connect issue<br><br></div>On Mon, Dec 13, 2010 at 12:19:03PM -0500, Shawn Cannon wrote:<br>> I meant I ran tsql. :-)<br>> <br>> Shawn Cannon<br>> <br>> IT Professional<br>> <br>> > OK I installed it ans ran TDS using sql.hidden.local and the port number<br>> > and I was able to create the table. I changed my syslogng config file to<br>> > this same setting, yet it still gives me an error. I left the table in the<br>> > database that was created but even that did not help. Any ideas?<br><br>There have been some bugs in the past where syslog-ng was not always <br>connecting to the database correctly on the proper ports, etc. However <br>in your case this could only apply if something was also listening on <br>the default port I would assume, since it seemed like it had connected. <br>Although as one of the other posters had pointed out there could be an <br>inaccurate error message as well. Perhaps you could verify it's <br>connecting properly to the DB using Wireshark?<br><br>Was the tsql / sqsh / etc. based testing performed using the same <br>machine as the syslog-ng setup is running?<br><br>Matthew.<br>______________________________________________________________________________<br>Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>FAQ: <a href="http://www.campin.net/syslog-ng/faq.html">http://www.campin.net/syslog-ng/faq.html</a><br></blockquote></body></html>