Re: NDISWAN TCPIP Event Error 4191 - Stack Problems



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@xxxxxxxxxxxxxxxxxxxx,
Harry Bates <harry.bates@xxxxxxxxxxxxxxx> 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?eventid=4191&eventno=869&source=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.aspx?scid=kb;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.aspx?scid=kb;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




.



Relevant Pages

  • RE: Registry explanation of ghosted network adapters
    ... NoteID for Adapter is the network adapter that TCP/IP is bound to. ... It appears that each individual network adapter has a unique PNPInstanceID ... The reason I ask is because server "a" is configured now with a NIC with MAC ... - I do not have to remove the ghost adapter from the registry because I want ...
    (microsoft.public.windows.server.networking)
  • RE: Custom Adapter Deployment
    ... Server, ... I used the Adapter Registry Wizard ...
    (microsoft.public.biztalk.general)
  • Re: 3 Ip Addresses on 1 adapter, multiple dns entries is a problem
    ... This server hosts an intranet site. ... I have another DNS ... You can also use this registry key: ... IP address of the server's local network adapter. ...
    (microsoft.public.windows.server.dns)
  • RE: issues authentication w/2003 server AND SP1, IIS 6, FPSE 2002
    ... Server 2003 with Service Pack 1. ... In Registry Editor, locate and then click the following registry key: ... > following article number to view the article in the Microsoft Knowledge Base: ...
    (microsoft.public.frontpage.extensions.windowsnt)
  • Re: ISA and IIS services getting confused
    ... the ServicePackNumber is set to 1 in the registry. ... you need to verify that you had applied SBS 2003 ... On the SBS server, click Start, click Run, type "regedit" (without ... To successfully install SBS 2003 SP1, ...
    (microsoft.public.windows.server.sbs)