Connection Problem VB.Net 2003 to SQL 2000

[Fred]

Hi,

I have a webservice created in VB.NET 2003 hosted on a Windows 2003
server. This service inserts data into a SQL Server 2000 database also
hosted on a Windows 2003 server. The webserver is in a closed DMZ and
the Database Sever is on the internal network. The firewall is
configured to allow traffic to the DB Server on port 1433. Form the
outside world the request get passed throught to the webserver as it
should be. However when the request from the webserver is passed to
the DB server the request on port 1433 is being passed but two
requests one on port 137 and one on port 445 are being dropped. Can
anyone tell me why a simple sqlCommand.ExecuteNonQuery() would need to
use 137 and 445?

Many thanks

Fred

[=?Utf-8?B?S2VycnkgTW9vcm1hbg==?=]

Fred,

These articles don't apply directly to your situation, but they do explain
those additional ports:

http://support.microsoft.com/kb/841251/

http://support.microsoft.com/kb/841249/

Kerry Moorman
"Fred" wrote:

Hi,

I have a webservice created in VB.NET 2003 hosted on a Windows 2003
server. This service inserts data into a SQL Server 2000 database also
hosted on a Windows 2003 server. The webserver is in a closed DMZ and
the Database Sever is on the internal network. The firewall is
configured to allow traffic to the DB Server on port 1433. Form the
outside world the request get passed throught to the webserver as it
should be. However when the request from the webserver is passed to
the DB server the request on port 1433 is being passed but two
requests one on port 137 and one on port 445 are being dropped. Can
anyone tell me why a simple sqlCommand.ExecuteNonQuery() would need to
use 137 and 445?

Many thanks

Fred

[Fred]

Kerry,

Thanks for your reply.

I have since discovered that this problem only occurs on Windows 2003
R2 (SP1) On a server running Windows 2003 without SP1 the problem is
not there. I guess the next step is to try and find out what (if
anything) has changed in SP1 that could cause the problem.

Regards

Fred

On 6 Feb, 13:58, Kerry Moorman
<[e-mail]:

Fred,

These articles don't apply directly to your situation, but they do explain
those additional ports:

http://support.microsoft.com/kb/841251/

http://support.microsoft.com/kb/841249/

Kerry Moorman

"Fred" wrote:

Hi,

I have a webservice created in VB.NET 2003 hosted on a Windows 2003
server. This service inserts data into a SQL Server 2000 database also
hosted on a Windows 2003 server. The webserver is in a closed DMZ and
the Database Sever is on the internal network. The firewall is
configured to allow traffic to the DB Server on port 1433. Form the
outside world the request get passed throught to the webserver as it
should be. However when the request from the webserver is passed to
the DB server the request on port 1433 is being passed but two
requests one on port 137 and one on port 445 are being dropped. Can
anyone tell me why a simple sqlCommand.ExecuteNonQuery() would need to
use 137 and 445?

Many thanks

Fred- Hide quoted text -

- Show quoted text -