Event ID4191 with Nextreme BCM5708C on windows 2003 x64

[PeetD]

Problems with Broadcom BCM5708C NetXtreme II GigE

I have a DELL poweredge 1900 server with a BCM5708C NIC which I want to use as an Exchange 2007 mail server. The machine is installed with Windows 2003 server x64 standard edition SP2. After installation of windows the driver for the NIC was installed. The current driver version is 4.4.15.0. Although the card seems to work fine (I can ping other computers locally and am able to browse the internet), I noticed that there is an error in the windows system event log:

Event Type: Error
Event Source: Tcpip
Event Category: None
Event ID: 4191
Date: 4-12-2008
Time: 15:07:23
User: N/A
Computer: MSMAIL1
Description:
IP could not open the registry key for adapter TCPIP\Parameters\Adapters\NDISWANIP. Interfaces on this adapter will not be initialized.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 02 00 50 00 ......P.
0008: 00 00 00 00 5f 10 00 c0 ...._..À
0010: 04 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

After this error appears a lot of other errors appear, all refering to MS Exchange services not starting. I can understand this since there seems to be a TCP/IP problem, so I focus on this error.

Looking up the event ID in MS support site, they say that the resolution would be to deinstall TCP/IP from the NIC and reinstall it again. However when I try doing so it seems that I can not Uninstall it since that button is greyed out, so much for that. Next I saw that you could also do this via the command line: "netsh winsock reset", tried that, no difference after that still the same behaviour (after reboot).
What also bothers me about the NIC is the fact that it will not keep fixed IP address settings, after changing the address and closing the TCP/IP properties, I open it again and notice that it's back to DHCP again :-(

Ok so I searched the web for this phenomenon and some people found on windows 2003OS with Nextreme II adapters and DELL Poweredge PC that the problem is caused by TOE being enabled on the NIC, disabling this would at least solve that problem (and I hoped the event ID 4191 would also be gone). See
http://forums.isaserver.org/unable_t...2075476/tm.htm
So I disabled TOE by executing the following on the command line: "netsh int ip set chimney DISABLED" and rebooted the system. This procedure was described by DELL. However the problem is still there. I also tried this while physically removing the TOE key from the motherboard, no change :-(

I tried upgrading the NICs firmware, no change. Uninstalling the NIC and reinstalling it, no change. So now I am out of options, hoping somebody out there has a bright idea or experience that can help me out.

Hello PeetD,

Check this one even it states windows 2000:
http://support.microsoft.com/kb/284955

http://www.eventid.net/display.asp?e...=Tcpip&phase=1

http://technet.microsoft.com/en-us/l.../cc727738.aspx

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Problems with Broadcom BCM5708C NetXtreme II GigE
>
> I have a DELL poweredge 1900 server with a BCM5708C NIC which I want
> to use as an Exchange 2007 mail server. The machine is installed with
> Windows 2003 server x64 standard edition SP2. After installation of
> windows the driver for the NIC was installed. The current driver
> version is 4.4.15.0. Although the card seems to work fine (I can ping
> other computers locally and am able to browse the internet), I noticed
> that there is an error in the windows system event log:
>
> Event Type: Error
> Event Source: Tcpip
> Event Category: None
> Event ID: 4191
> Date: 4-12-2008
> Time: 15:07:23
> User: N/A
> Computer: MSMAIL1
> Description:
> IP could not open the registry key for adapter
> TCPIP\Parameters\Adapters\NDISWANIP. Interfaces on this adapter will
> not
> be initialized.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 00 00 00 00 02 00 50 00 ......P.
> 0008: 00 00 00 00 5f 10 00 c0 ...._..À
> 0010: 04 00 00 00 00 00 00 00 ........
> 0018: 00 00 00 00 00 00 00 00 ........
> 0020: 00 00 00 00 00 00 00 00 ........
> After this error appears a lot of other errors appear, all refering to
> MS Exchange services not starting. I can understand this since there
> seems to be a TCP/IP problem, so I focus on this error.
>
> Looking up the event ID in MS support site, they say that the
> resolution would be to deinstall TCP/IP from the NIC and reinstall it
> again. However when I try doing so it seems that I can not Uninstall
> it since that button is greyed out, so much for that. Next I saw that
> you could also do this via the command line: "netsh winsock reset",
> tried that, no difference after that still the same behaviour (after
> reboot).
>
> What also bothers me about the NIC is the fact that it will not keep
> fixed IP address settings, after changing the address and closing the
> TCP/IP properties, I open it again and notice that it's back to DHCP
> again :-(
>
> Ok so I searched the web for this phenomenon and some people found on
> windows 2003OS with Nextreme II adapters and DELL Poweredge PC that
> the
> problem is caused by TOE being enabled on the NIC, disabling this
> would
> at least solve that problem (and I hoped the event ID 4191 would also
> be
> gone). See
> http://forums.isaserver.org/unable_t...ess/m_20020754
> 76/tm.htm
> So I disabled TOE by executing the following on the command line:
> "netsh int ip set chimney DISABLED" and rebooted the system. This
> procedure was described by DELL. However the problem is still there. I
> also tried this while physically removing the TOE key from the
> motherboard, no change :-(
> I tried upgrading the NICs firmware, no change. Uninstalling the NIC
> and reinstalling it, no change. So now I am out of options, hoping
> somebody out there has a bright idea or experience that can help me
> out.
>
> http://forums.techarena.in
>

[PeetD]

@Meinolf,
Thanks but like I stated in the problem, I already tried resetting winsock (did not work).