NDISWAN TCPIP Event Error 4191 - Stack Problems

Posted this last week in microsoft.public.windows.server.general with no
results:





Server 2003 Enterprise

Event Type: Error
Event Source: Tcpip
Event Category: None
Event ID: 4191
Date: 1/9/2008
Time: 9:22:55 AM
User: N/A
Computer: MTNGT500
Description:
IP could not open the registry key for adapter
TCPIP\Parameters\Adapters\NDISWANIP. Interfaces on this adapter will not be
initialized.

Obviously, a lot of you have seen this error in the past. As always with
Win2000, we would uninstall TCP/IP and re-install it to fix the problem
(KB284955). Also, obvious is that M$ has made the IP stack a core component
from Windows XP on to current OSes. A few years ago I ran into this problem
and we were not able to fix the error in 2003 Server a few years ago. "Netsh
int ip reset" command does not work as it only rebuilds the the normal NIC
adapters registry and does not do anything with ndiswanip adapter linkage.
Are there any fixes out there for this problem yet? I don't understand why
this is still an issue without a legit fix, as I have seen this problem a
number of times on the net. Thank you in advance for any help you can
provide.

Harry Bates
Lead Infrastructure Engineering/Diagnostics
Lockheed Martin

In news:OCjm$krVIHA.2000@TK2MSFTNGP05.phx.gbl,
Harry Bates <harry.bates@NO-SPAMlmco.com> typed:
> Posted this last week in microsoft.public.windows.server.general with
> no results:
>
>
>
>
>
> Server 2003 Enterprise
>
> Event Type: Error
> Event Source: Tcpip
> Event Category: None
> Event ID: 4191
> Date: 1/9/2008
> Time: 9:22:55 AM
> User: N/A
> Computer: MTNGT500
> Description:
> IP could not open the registry key for adapter
> TCPIP\Parameters\Adapters\NDISWANIP. Interfaces on this adapter will
> not be initialized.
>
> Obviously, a lot of you have seen this error in the past. As always
> with Win2000, we would uninstall TCP/IP and re-install it to fix the
> problem (KB284955). Also, obvious is that M$ has made the IP stack a
> core component from Windows XP on to current OSes. A few years ago I
> ran into this problem and we were not able to fix the error in 2003
> Server a few years ago. "Netsh int ip reset" command does not work as
> it only rebuilds the the normal NIC adapters registry and does not do
> anything with ndiswanip adapter linkage. Are there any fixes out
> there for this problem yet? I don't understand why this is still an
> issue without a legit fix, as I have seen this problem a number of
> times on the net. Thank you in advance for any help you can provide.
>
> Harry Bates
> Lead Infrastructure Engineering/Diagnostics
> Lockheed Martin

I guess you saw this article at this link already?
http://www.eventid.net/display.asp?e...=Tcpip&phase=1

Is RRAS installed? If so, take a look at this (referenced from teh above
article):
Routing and Remote Access Service does not start and event ID 20103 message
is logged
http://support.microsoft.com/default...b;en-us;299013


How about this?
325356 - HOW TO Remove and Reinstall TCP-IP on a Windows Server 2003 Domain
Controller:
http://support.microsoft.com/default...b;en-us;325356

--
Regards,
Ace

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

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations

In news:%23luGIWwVIHA.1376@TK2MSFTNGP02.phx.gbl,
Ace Fekay [MVP] <PleaseAskMe@SomeDomain.com> typed:


Here's one more:
How to reset Internet Protocol (TCP-IP) in Windows Server 2003:
http://support.microsoft.com/default.aspx?kbid=317518

Ace

Thank you so much Ace. KB325356 re-initialized the stack.

"Ace Fekay [MVP]" <PleaseAskMe@SomeDomain.com> wrote in message
news:%23luGIWwVIHA.1376@TK2MSFTNGP02.phx.gbl...
> In news:OCjm$krVIHA.2000@TK2MSFTNGP05.phx.gbl,
> Harry Bates <harry.bates@NO-SPAMlmco.com> typed:
>> Posted this last week in microsoft.public.windows.server.general with
>> no results:
>>
>>
>>
>>
>>
>> Server 2003 Enterprise
>>
>> Event Type: Error
>> Event Source: Tcpip
>> Event Category: None
>> Event ID: 4191
>> Date: 1/9/2008
>> Time: 9:22:55 AM
>> User: N/A
>> Computer: MTNGT500
>> Description:
>> IP could not open the registry key for adapter
>> TCPIP\Parameters\Adapters\NDISWANIP. Interfaces on this adapter will
>> not be initialized.
>>
>> Obviously, a lot of you have seen this error in the past. As always
>> with Win2000, we would uninstall TCP/IP and re-install it to fix the
>> problem (KB284955). Also, obvious is that M$ has made the IP stack a
>> core component from Windows XP on to current OSes. A few years ago I
>> ran into this problem and we were not able to fix the error in 2003
>> Server a few years ago. "Netsh int ip reset" command does not work as
>> it only rebuilds the the normal NIC adapters registry and does not do
>> anything with ndiswanip adapter linkage. Are there any fixes out
>> there for this problem yet? I don't understand why this is still an
>> issue without a legit fix, as I have seen this problem a number of
>> times on the net. Thank you in advance for any help you can provide.
>>
>> Harry Bates
>> Lead Infrastructure Engineering/Diagnostics
>> Lockheed Martin
>
> I guess you saw this article at this link already?
> http://www.eventid.net/display.asp?e...=Tcpip&phase=1
>
> Is RRAS installed? If so, take a look at this (referenced from teh above
> article):
> Routing and Remote Access Service does not start and event ID 20103
> message is logged
> http://support.microsoft.com/default...b;en-us;299013
>
>
> How about this?
> 325356 - HOW TO Remove and Reinstall TCP-IP on a Windows Server 2003
> Domain Controller:
> http://support.microsoft.com/default...b;en-us;325356
>
> --
> Regards,
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
> MVP Microsoft MVP - Directory Services
> Microsoft Certified Trainer
>
> Infinite Diversities in Infinite Combinations
>
>
>

In news:ej0B$k4VIHA.4740@TK2MSFTNGP02.phx.gbl,
Harry Bates <harry.bates@NO-SPAMlmco.com> typed:
> Thank you so much Ace. KB325356 re-initialized the stack.

Glad to be of service. :-)

Will the netsh command work in Windows 2000 Server? I too have lost my
ndiswanip registry entry. It happened as a result of restoring the system
state during disaster recovery. I can ping devices on my local network, but
cannot ping anything on the internet side of the router. Neither an ip
address or URL returns a response. Also, I cannot uninstall TCP/IP in
Network Connection properties.

Thanks.
--
J M Hart


"Ace Fekay [MVP]" wrote:

> In news:OCjm$krVIHA.2000@TK2MSFTNGP05.phx.gbl,
> Harry Bates <harry.bates@NO-SPAMlmco.com> typed:
> > Posted this last week in microsoft.public.windows.server.general with
> > no results:
> >
> >
> >
> >
> >
> > Server 2003 Enterprise
> >
> > Event Type: Error
> > Event Source: Tcpip
> > Event Category: None
> > Event ID: 4191
> > Date: 1/9/2008
> > Time: 9:22:55 AM
> > User: N/A
> > Computer: MTNGT500
> > Description:
> > IP could not open the registry key for adapter
> > TCPIP\Parameters\Adapters\NDISWANIP. Interfaces on this adapter will
> > not be initialized.
> >
> > Obviously, a lot of you have seen this error in the past. As always
> > with Win2000, we would uninstall TCP/IP and re-install it to fix the
> > problem (KB284955). Also, obvious is that M$ has made the IP stack a
> > core component from Windows XP on to current OSes. A few years ago I
> > ran into this problem and we were not able to fix the error in 2003
> > Server a few years ago. "Netsh int ip reset" command does not work as
> > it only rebuilds the the normal NIC adapters registry and does not do
> > anything with ndiswanip adapter linkage. Are there any fixes out
> > there for this problem yet? I don't understand why this is still an
> > issue without a legit fix, as I have seen this problem a number of
> > times on the net. Thank you in advance for any help you can provide.
> >
> > Harry Bates
> > Lead Infrastructure Engineering/Diagnostics
> > Lockheed Martin
>
> I guess you saw this article at this link already?
> http://www.eventid.net/display.asp?e...=Tcpip&phase=1
>
> Is RRAS installed? If so, take a look at this (referenced from teh above
> article):
> Routing and Remote Access Service does not start and event ID 20103 message
> is logged
> http://support.microsoft.com/default...b;en-us;299013
>
>
> How about this?
> 325356 - HOW TO Remove and Reinstall TCP-IP on a Windows Server 2003 Domain
> Controller:
> http://support.microsoft.com/default...b;en-us;325356
>
> --
> Regards,
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
> MVP Microsoft MVP - Directory Services
> Microsoft Certified Trainer
>
> Infinite Diversities in Infinite Combinations
>
>
>
>

In news:FC94FC17-DF9B-4A15-84B3-D85CCB51BDD8@microsoft.com,
JoeH <joehart55@earthlink.net> typed:
> Will the netsh command work in Windows 2000 Server? I too have lost
> my ndiswanip registry entry. It happened as a result of restoring
> the system state during disaster recovery. I can ping devices on my
> local network, but cannot ping anything on the internet side of the
> router. Neither an ip address or URL returns a response. Also, I
> cannot uninstall TCP/IP in Network Connection properties.
>
> Thanks.

It should. Give it a shot.

Ace

You will probably need to use what Ace pointed out earlier for me:

How about this?
325356 - HOW TO Remove and Reinstall TCP-IP on a Windows Server 2003 Domain
Controller:
http://support.microsoft.com/default...b;en-us;325356

"JoeH" <joehart55@earthlink.net> wrote in message
news:FC94FC17-DF9B-4A15-84B3-D85CCB51BDD8@microsoft.com...
> Will the netsh command work in Windows 2000 Server? I too have lost my
> ndiswanip registry entry. It happened as a result of restoring the system
> state during disaster recovery. I can ping devices on my local network,
> but
> cannot ping anything on the internet side of the router. Neither an ip
> address or URL returns a response. Also, I cannot uninstall TCP/IP in
> Network Connection properties.
>
> Thanks.
> --
> J M Hart
>
>
> "Ace Fekay [MVP]" wrote:
>
>> In news:OCjm$krVIHA.2000@TK2MSFTNGP05.phx.gbl,
>> Harry Bates <harry.bates@NO-SPAMlmco.com> typed:
>> > Posted this last week in microsoft.public.windows.server.general with
>> > no results:
>> >
>> >
>> >
>> >
>> >
>> > Server 2003 Enterprise
>> >
>> > Event Type: Error
>> > Event Source: Tcpip
>> > Event Category: None
>> > Event ID: 4191
>> > Date: 1/9/2008
>> > Time: 9:22:55 AM
>> > User: N/A
>> > Computer: MTNGT500
>> > Description:
>> > IP could not open the registry key for adapter
>> > TCPIP\Parameters\Adapters\NDISWANIP. Interfaces on this adapter will
>> > not be initialized.
>> >
>> > Obviously, a lot of you have seen this error in the past. As always
>> > with Win2000, we would uninstall TCP/IP and re-install it to fix the
>> > problem (KB284955). Also, obvious is that M$ has made the IP stack a
>> > core component from Windows XP on to current OSes. A few years ago I
>> > ran into this problem and we were not able to fix the error in 2003
>> > Server a few years ago. "Netsh int ip reset" command does not work as
>> > it only rebuilds the the normal NIC adapters registry and does not do
>> > anything with ndiswanip adapter linkage. Are there any fixes out
>> > there for this problem yet? I don't understand why this is still an
>> > issue without a legit fix, as I have seen this problem a number of
>> > times on the net. Thank you in advance for any help you can provide.
>> >
>> > Harry Bates
>> > Lead Infrastructure Engineering/Diagnostics
>> > Lockheed Martin
>>
>> I guess you saw this article at this link already?
>> http://www.eventid.net/display.asp?e...=Tcpip&phase=1
>>
>> Is RRAS installed? If so, take a look at this (referenced from teh above
>> article):
>> Routing and Remote Access Service does not start and event ID 20103
>> message
>> is logged
>> http://support.microsoft.com/default...b;en-us;299013
>>
>>
>> How about this?
>> 325356 - HOW TO Remove and Reinstall TCP-IP on a Windows Server 2003
>> Domain
>> Controller:
>> http://support.microsoft.com/default...b;en-us;325356
>>
>> --
>> Regards,
>> Ace
>>
>> This posting is provided "AS-IS" with no warranties or guarantees and
>> confers no rights.
>>
>> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
>> MVP Microsoft MVP - Directory Services
>> Microsoft Certified Trainer
>>
>> Infinite Diversities in Infinite Combinations
>>
>>
>>
>>

In news:uVGeCCveIHA.4260@TK2MSFTNGP05.phx.gbl,
Harry Bates <harry.bates@NO-SPAMlmco.com> typed:
> You will probably need to use what Ace pointed out earlier for me:
>
> How about this?
> 325356 - HOW TO Remove and Reinstall TCP-IP on a Windows Server 2003
> Domain Controller:
> http://support.microsoft.com/default...b;en-us;325356

Good call Harry!
:-)