S
Schalley Ben
Hi
First of all, this is my first post on a newsgroup so don't shoot me if
I ask this in the wrong place.
Here is the situation. I'm developing an asp.net application with access
to a SQL Server 2000 on the companies network. On my development machine
I have Bitdefender Internet Security v10 installed. With the Bitdefender
Firewall disabled I have no problems in surfing and debugging the
application. However when the firewall is enabled, it asks if I want to
allow aspnet_wp.exe to connect to the sql server and off course I allow
this. The rule that allows aspnet_wp.exe to connect to the sql server is
successfully added to the firewall but still the connection to the sql
server fails. I communicated this with Bitdefender support but they
haven't come up with a solution yet.
Today I tried adding a rule to the firewall manually. The rule I added
allows ALL applications on my machine to connect to the SQL Server by
its ip-address and port, communication is allowed in both directions for
TCP only. This firewall rule (in my eyes everything but secure) lets the
asp.net application successfully connect to the SQL Server. Now because
of this rule I added, I started wondering if there are other .net
processes which need permission to connect to the SQL Server for a
successful connection. At least the firewall does not inform me of other
processes which try to connect.
Is there anyone who can help me?
Best Regards
Greetz & Thanx
Ben Schalley
First of all, this is my first post on a newsgroup so don't shoot me if
I ask this in the wrong place.
Here is the situation. I'm developing an asp.net application with access
to a SQL Server 2000 on the companies network. On my development machine
I have Bitdefender Internet Security v10 installed. With the Bitdefender
Firewall disabled I have no problems in surfing and debugging the
application. However when the firewall is enabled, it asks if I want to
allow aspnet_wp.exe to connect to the sql server and off course I allow
this. The rule that allows aspnet_wp.exe to connect to the sql server is
successfully added to the firewall but still the connection to the sql
server fails. I communicated this with Bitdefender support but they
haven't come up with a solution yet.
Today I tried adding a rule to the firewall manually. The rule I added
allows ALL applications on my machine to connect to the SQL Server by
its ip-address and port, communication is allowed in both directions for
TCP only. This firewall rule (in my eyes everything but secure) lets the
asp.net application successfully connect to the SQL Server. Now because
of this rule I added, I started wondering if there are other .net
processes which need permission to connect to the SQL Server for a
successful connection. At least the firewall does not inform me of other
processes which try to connect.
Is there anyone who can help me?
Best Regards
Greetz & Thanx
Ben Schalley