Disabling firewall only way to connect, was working

Well, I discovered my once-working web app is failing to connect to SQL Server.
I had the windows Firewall running and working with a non-standard port and
responding to subnet only.
Windows update is configure to auto install. At some point in late December
the machine was rebooted. Coincidentally, after that, the only way to make
the connection work was to completely disable the windows firewall. Not an
option.
Windows 2003 - With latest critical updates from MS
SQL Server 2005 SP1
SQL and IIS are on separate machines.
TCP is the only enabled protocol for SQL
VS.Net 2005, using System.Data.SqlClient
Connection string is: Data Source=nnn.nnn.nnn.nnn,9919;Initial
Catalog=dbname;User Id=yourname;Password=yourpassword
I have tried moving SQL back to PORT 1433, and added sqlsvrer.exe as an
acceptable application, but it did not work.
MS SQL Server Management Studio does not connect with firewall enabled.
I was able to connect our production web application to our development
database. I was not able to connect our development server's version to the
production database. Both production and development have the same firewall
settings and MS updates. So, I am guessing there is something very wrong with
our production SQL?
Not sure if this is related, but I have noticed a 10 or so second lag
between Remote Desktop access initiation and an answer. On our
web servers the answer is near instant. Once in, it works fine. We are on
a very large network.
Any ideas? Am I missing a port?
Nevermind. Fixed.
Removed and recreated firewall setting for SQL. Also, the default gateway
was not the same between machines. These had not been modified in over 6
months.
Seems to work now.
"Devin" wrote:

> Well, I discovered my once-working web app is failing to connect to SQL Server.
> I had the windows Firewall running and working with a non-standard port and
> responding to subnet only.
> Windows update is configure to auto install. At some point in late December
> the machine was rebooted. Coincidentally, after that, the only way to make
> the connection work was to completely disable the windows firewall. Not an
> option.
> Windows 2003 - With latest critical updates from MS
> SQL Server 2005 SP1
> SQL and IIS are on separate machines.
> TCP is the only enabled protocol for SQL
> VS.Net 2005, using System.Data.SqlClient
> Connection string is: Data Source=nnn.nnn.nnn.nnn,9919;Initial
> Catalog=dbname;User Id=yourname;Password=yourpassword
> I have tried moving SQL back to PORT 1433, and added sqlsvrer.exe as an
> acceptable application, but it did not work.
> MS SQL Server Management Studio does not connect with firewall enabled.
> I was able to connect our production web application to our development
> database. I was not able to connect our development server's version to the
> production database. Both production and development have the same firewall
> settings and MS updates. So, I am guessing there is something very wrong with
> our production SQL?
> Not sure if this is related, but I have noticed a 10 or so second lag
> between Remote Desktop access initiation and an answer. On our
> web servers the answer is near instant. Once in, it works fine. We are on
> a very large network.
> Any ideas? Am I missing a port?
>