Re: SQL or ISA firewall problem
- From: "Matt Neerincx [MS]" <mattn@xxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 21 Aug 2005 21:57:40 -0700
Note when you start doing transaction with SQL, this switches the tcp socket
into keepalive mode.
In keepalive mode the connection will send 1 byte keepalives every 30
seconds on idle connections, you can see this in netmon for example.
Not sure why this is causing the firewall to act up, but just throwing in a
possible clue for you.
Matt Neerincx [MSFT]
This posting is provided "AS IS", with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"Joe Bucar" <jbucar@xxxxxxxxxxx> wrote in message
news:e1H75mQnFHA.2484@xxxxxxxxxxxxxxxxxxxxxxx
> Thank You for your response. The port is configured to accept
> connections. The problem is for some reason after a couple of application
> transactions the I lose the connection.
> Joe
> "Dandy Weyn [Dandyman]" <dandy@xxxxxxxxxxxx> wrote in message
> news:%23sdlkZJnFHA.3900@xxxxxxxxxxxxxxxxxxxxxxx
>> It looks that ISA Server is not configured for the SQL Server port 1433
>> to accept connections.
>> You might want to create a protocol rule on the ISA Server that accepts
>> incoming SQL Server connections.
>>
>> --
>> Dandy Weyn
>> [MCSE-MCSA-MCDBA-MCDST-MCT]
>> http://www.dandyman.net
>>
>> Check my SQL Server Resource Pages at http://www.dandyman.net/sql
>> "Joe Bucar" <jbucar@xxxxxxxxxxx> wrote in message
>> news:%23oACQGFnFHA.4064@xxxxxxxxxxxxxxxxxxxxxxx
>>> Hello,
>>> I have a problem and I do not know if it is a SQL problem or a ISA
>>> firewall problem. I have two seperate SBS servers 'Server A' is a SBS
>>> 2000 and 'Server B' is a SBS 2003 and both have SQL 2000 installed on
>>> them. On a workstation on 'Server B' I am running an application that
>>> is accessing the SQL database on 'Server A' via ODBC. I can login on
>>> the application and do between 5 or 6 transactions before I get a SQL
>>> connection error. While I am doing the transactions I am running
>>> netstat in the background and when I see the SYN_SENT that is when the
>>> connection error happens. If I disable the ISA firewall client I can
>>> run transactions until the cows come home and not have a SQL connection
>>> problem. Is this a SQL or a firewall problem?
>>>
>>> The following is the netstat with the firewall
>>> TCP 192.168.16.167:1800 192.168.16.2:55352 ESTABLISHED
>>> TCP 192.168.16.167:1801 192.168.16.2:55354 ESTABLISHED
>>> TCP 192.168.16.167:1802 192.168.16.2:55356 ESTABLISHED
>>> TCP 192.168.16.167:1803 192.168.16.2:55358 ESTABLISHED
>>> TCP 192.168.16.167:1804 192.168.16.2:55360 ESTABLISHED
>>> TCP 192.168.16.167:1805 192.168.16.2:55262 SYN_SENT
>>> TCP 192.168.16.167:2967 192.168.16.2:8080 CLOSE_WAIT
>>>
>>> The following is the netstat with the firewall disabled.
>>> TCP 192.168.16.167:1806 192.168.1.59:1433 ESTABLISHED
>>> TCP 192.168.16.167:1807 192.168.1.59:1433 ESTABLISHED
>>> TCP 192.168.16.167:1808 192.168.1.59:1433 ESTABLISHED
>>> TCP 192.168.16.167:1809 192.168.1.59:1433 ESTABLISHED
>>> TCP 192.168.16.167:1810 192.168.1.59:1433 ESTABLISHED
>>> TCP 192.168.16.167:1811 192.168.1.59:1433 ESTABLISHED
>>>
>>> I beleive the problem is with the firewall but I can not figure out what
>>> the problem is or configure it. The only thing that make sense to me is
>>> that the firewall thinks it is under attack. Any help would be
>>> apriciated.
>>>
>>> Thank You,
>>>
>>> Joe
>>>
>>
>>
>
>
.
- References:
- SQL or ISA firewall problem
- From: Joe Bucar
- Re: SQL or ISA firewall problem
- From: Dandy Weyn [Dandyman]
- Re: SQL or ISA firewall problem
- From: Joe Bucar
- SQL or ISA firewall problem
- Prev by Date: Re: blob and network packet size
- Next by Date: Deadlock
- Previous by thread: Re: SQL or ISA firewall problem
- Next by thread: Re: Unexpected Login Screen When Accessing SQL Data Via .NET Intranet
- Index(es):
Relevant Pages
|
