Network problems on W2K3 EntServer after installing SP2

Hello,
I have a HP DL 360 G5 Server with a NC373i-Interface with Windows Server
2003 Enterprise R2 32 bit and SQL-Server Enterprise 2005 SP1 installed.

After installing SP2 for windows, my SQL-Databases are no longer backupable
by the backup server (veritas netbackup). Sometimes they simply fail with
"network not readable". The NIC-statistik-counters began to count TCP-errors
(mostly "no buffer" errors).

The cables are checked and ok, the errors occur only since installing the
windows-service-pack.

In order to verify our guess we de-installed the sp and everything worked
fine again. Even the NIC-counters remain on zero.

Does anybody know, whether this is a bug with the hp agents or with the sp
of windows? Or has anybody encountered the same problem and knows how to
solve it? SP 2 solves other problems we have, so we need it.

Greetings

Celina

Hello Celina,

Check out this site:
http://www.chicagotech.net/netforums...5546e41bc4fd1b

Best regards

Meinolf Weber (Myweb)
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> Hello,
> I have a HP DL 360 G5 Server with a NC373i-Interface with Windows
> Server
> 2003 Enterprise R2 32 bit and SQL-Server Enterprise 2005 SP1
> installed.
> After installing SP2 for windows, my SQL-Databases are no longer
> backupable by the backup server (veritas netbackup). Sometimes they
> simply fail with "network not readable". The NIC-statistik-counters
> began to count TCP-errors (mostly "no buffer" errors).
>
> The cables are checked and ok, the errors occur only since installing
> the windows-service-pack.
>
> In order to verify our guess we de-installed the sp and everything
> worked fine again. Even the NIC-counters remain on zero.
>
> Does anybody know, whether this is a bug with the hp agents or with
> the sp of windows? Or has anybody encountered the same problem and
> knows how to solve it? SP 2 solves other problems we have, so we need
> it.
>
> Greetings
>
> Celina
>

Hello,
We found the solution:
A colleague of mine found an artikel on the web which mentions to disable
TOE on the NIC (http://www.networkworld.com/details/653.html). We did that
and the error has gone.

Greetings

Celina

"Meinolf Weber (Myweb)" wrote:

> Hello Celina,
>
> Check out this site:
> http://www.chicagotech.net/netforums...5546e41bc4fd1b
>
> Best regards
>
> Meinolf Weber (Myweb)
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
>
> > Hello,
> > I have a HP DL 360 G5 Server with a NC373i-Interface with Windows
> > Server
> > 2003 Enterprise R2 32 bit and SQL-Server Enterprise 2005 SP1
> > installed.
> > After installing SP2 for windows, my SQL-Databases are no longer
> > backupable by the backup server (veritas netbackup). Sometimes they
> > simply fail with "network not readable". The NIC-statistik-counters
> > began to count TCP-errors (mostly "no buffer" errors).
> >
> > The cables are checked and ok, the errors occur only since installing
> > the windows-service-pack.
> >
> > In order to verify our guess we de-installed the sp and everything
> > worked fine again. Even the NIC-counters remain on zero.
> >
> > Does anybody know, whether this is a bug with the hp agents or with
> > the sp of windows? Or has anybody encountered the same problem and
> > knows how to solve it? SP 2 solves other problems we have, so we need
> > it.
> >
> > Greetings
> >
> > Celina
> >
>
>
>

Hello Celina,

Nice to hear that you got it. Also the Info about the solution.

Best regards

Meinolf Weber (Myweb)
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> Hello,
> We found the solution:
> A colleague of mine found an artikel on the web which mentions to
> disable
> TOE on the NIC (http://www.networkworld.com/details/653.html). We did
> that
> and the error has gone.
> Greetings
>
> Celina
>
> "Meinolf Weber (Myweb)" wrote:
>
>> Hello Celina,
>>
>> Check out this site:
>> http://www.chicagotech.net/netforums...9&sid=0d5f0ba9
>> 4f4bcea3855546e41bc4fd1b
>> Best regards
>>
>> Meinolf Weber (Myweb)
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>>> Hello,
>>> I have a HP DL 360 G5 Server with a NC373i-Interface with Windows
>>> Server
>>> 2003 Enterprise R2 32 bit and SQL-Server Enterprise 2005 SP1
>>> installed.
>>> After installing SP2 for windows, my SQL-Databases are no longer
>>> backupable by the backup server (veritas netbackup). Sometimes they
>>> simply fail with "network not readable". The NIC-statistik-counters
>>> began to count TCP-errors (mostly "no buffer" errors).
>>> The cables are checked and ok, the errors occur only since
>>> installing the windows-service-pack.
>>>
>>> In order to verify our guess we de-installed the sp and everything
>>> worked fine again. Even the NIC-counters remain on zero.
>>>
>>> Does anybody know, whether this is a bug with the hp agents or with
>>> the sp of windows? Or has anybody encountered the same problem and
>>> knows how to solve it? SP 2 solves other problems we have, so we
>>> need it.
>>>
>>> Greetings
>>>
>>> Celina
>>>

"muhkem_" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> hi celina,
> How did you solve this problem ??
>
>


Hello muhkem,

This is in response to a thread that is over 2 years old. In most cases, it
is better to start a new thread under your own name. If you can provide info
about your current setup, hardware type, etc, and state the problems you are
having, along with EventID# errors you are seeing, it will help us to help
you with the specific problems you are experiencing.



--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.