TCP/IP corrupted

  • Thread starter Thread starter A. Fred
  • Start date Start date
A

A. Fred

I have a Windows Server 2003 that is a primary domain controller.
It has suddenly lost its TCP/IP connectivity.

The Network Adapter still exists My Network Places, and the Properites of
the
TCP/IP protocol is correct. I have run hardware diagnostics on the NIC and
it is OK.
The adapter is Enabled and I have a connection light on the Network
hub/switch.

Ipconfig.exe simply reports:
"Windows IP Configuration"
That's it. Nothing else.

I can ping 127.0.0.1, but not its own address (192.168.0.2) - unreachable.

Netdaig.exe says:
"Failed to get information for network adapter. The error occurred was:
The pipe is being closed. [FATAL] Cannot find TCP/IP configuration from
the registry."

From My Network Places Properties, if I select that adapter and choose
Device Repair,
it returns:
"Failed to query TCP/IP settings of the connection. Cannot proceed."

I cannot uninstall the TCP/IP protocol to try to re-install.

Any ideas? Thanks in advance.
 
I would like to follow up on myself. The system is "working" but it is not
fixed.

Per KB317518, I used the following command to reset TCP/IP:
netsh int ip reset <logfilename>
I then rebooted. It came back up with an operational network.

However... it got its IP address fed to it by a DHCP server. Being a server
itself with a fixed IP address, I reconfigured it to put its own IP settings
back.
Each time I change it to a static IP address, however, the problem returns.
If I set it up to automatically obtain an address, it works.

So, the server is online and working, but with a dynamic IP address
(not a good thing for a DC and server).

Thots?
 
:I would like to follow up on myself. The system is "working" but it is not
: fixed.
:
: Per KB317518, I used the following command to reset TCP/IP:
: netsh int ip reset <logfilename>
: I then rebooted. It came back up with an operational network.
:
: However... it got its IP address fed to it by a DHCP server. Being a
server
: itself with a fixed IP address, I reconfigured it to put its own IP
settings
: back.
: Each time I change it to a static IP address, however, the problem
returns.
: If I set it up to automatically obtain an address, it works.
:
: So, the server is online and working, but with a dynamic IP address
: (not a good thing for a DC and server).

I read a similar article that used this to fix it. Not sure about W2K3
Server though...

http://www.itc.virginia.edu/desktop/central/display/versions.php3?softwareID=67&nav=title

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
FAQ W2K/2K3 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;291382
 
Back
Top