Well, I figured it out. The trick was to figure out *how* the web server was trying to access the SQL box. I finally found the serve-side code and from there found the LMHOST file was the culprit. Once I changed the existing ip address, the published server policy on ISA did the trick. -----Original Message----- From: Scott Gwartney [mailto:SGwartney@xxxxxxxxxxx] Sent: Thursday, January 17, 2002 11:36 AM To: [ISAserver.org Discussion List] Subject: [isalist] SQL trouble http://www.ISAserver.org I told everyone I would be writing back soon! I've installed the ISA server today and, for the most part, everything is going smoothly. I am having some trouble with my SQL server though: The setup; Website between router and ISA The website uses a web app to query an SQL on the private side of the ISA Web browsers on the private side of the ISA are configured to not use proxy for addresses beginning with domain.com (where domain.com is the domain of the SQL enhanced website). However, even when the website is removed from the exceptions, things don't work. The problem; Whenever the website tries to query the SQL machine, I get and OLE DB error reporting general network errors. What I've tried; Opening all ports between the web server and the SQL box through ISA Publishing the SQL box Opening just port 1433 I'm out of ideas! Can someone help? TIA --Scott ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: sgwartney@xxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')