Networking Forums

Networking Forums > Computer Networking > Windows Networking > Event ID4191 with Nextreme BCM5708C on windows 2003 x64

Reply
Thread Tools Display Modes

Event ID4191 with Nextreme BCM5708C on windows 2003 x64

 
 
PeetD
Guest
Posts: n/a

 
      12-04-2008, 02:36 PM

Problems with Broadcom BCM5708C NetXtreme II GigE

I have a DELL poweredge 1900 server with a BCM5708C NIC which I want t
use as an Exchange 2007 mail server. The machine is installed wit
Windows 2003 server x64 standard edition SP2. After installation o
windows the driver for the NIC was installed. The current driver versio
is 4.4.15.0. Although the card seems to work fine (I can ping othe
computers locally and am able to browse the internet), I noticed tha
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 adapte
TCPIP\Parameters\Adapters\NDISWANIP. Interfaces on this adapter will no
be initialized.

For more information, see Help and Support Center a
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 t
MS Exchange services not starting. I can understand this since ther
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 th
resolution would be to deinstall TCP/IP from the NIC and reinstall i
again. However when I try doing so it seems that I can not Uninstall i
since that button is greyed out, so much for that. Next I saw that yo
could also do this via the command line: "netsh winsock reset", trie
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 kee
fixed IP address settings, after changing the address and closing th
TCP/IP properties, I open it again and notice that it's back to DHC
again :-(

Ok so I searched the web for this phenomenon and some people found o
windows 2003OS with Nextreme II adapters and DELL Poweredge PC that th
problem is caused by TOE being enabled on the NIC, disabling this woul
at least solve that problem (and I hoped the event ID 4191 would also b
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. Thi
procedure was described by DELL. However the problem is still there.
also tried this while physically removing the TOE key from th
motherboard, no change :-(

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

--
Peet
-----------------------------------------------------------------------
PeetD's Profile: http://forums.techarena.in/members/peetd.ht
View this thread: http://forums.techarena.in/server-networking/1082405.ht

http://forums.techarena.i

 
Reply With Quote
 
 
 
 
Meinolf Weber
Guest
Posts: n/a

 
      12-04-2008, 04:37 PM
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
>



 
Reply With Quote
 
PeetD
Guest
Posts: n/a

 
      12-04-2008, 06:07 PM

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

--
Peet
-----------------------------------------------------------------------
PeetD's Profile: http://forums.techarena.in/members/peetd.ht
View this thread: http://forums.techarena.in/server-networking/1082405.ht

http://forums.techarena.i

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Event ID 538 in Windows Server 2003 Dave Windows Networking 3 09-26-2006 04:54 PM
Windows Server 2003 SP1 Event 1030 and 1053 Arp Hiemstra Windows Networking 7 12-06-2005 05:13 PM
error event id 3019 in windows 2003 Jonatan Sancho Windows Networking 2 09-28-2005 03:01 PM
event 1054 on Windows 2003 member server Blake Windows Networking 0 06-28-2005 06:29 PM
Event ID 3019 on Windows 2003 Server Std. SP1 Marc Lueckert Windows Networking 0 05-24-2005 07:53 AM



1 2 3 4 5 6 7 8 9 10 11