[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 394
  • Last Modified:

Microsoft, Server, 2003, DNS, TCP/IP, Networking

Hi,
On my standalone server I cannot ping its own IP address. I checked the logs and saw that since the 31st Oct '08, the following entry appears in my System event log. No work was done on the server leading up to the 31st, (ie. app installs, reboots, nothing bar MS Updates that where downloaded but not yet installed);

Event Type:      Warning
Event Source:      DnsApi
Event Category:      None
Event ID:      11166
Date:            10/31/2008
Time:            6:48:06 PM
User:            N/A
Computer:      ISS-COREDB
Description:
The system failed to register host (A) resource records (RRs) for network adapter
with settings:

   Adapter Name : {012EC1BF-9F14-455B-97BB-C69C93EDF1E1}
   Host Name : iss-coredb
   Primary Domain Suffix : PLUTO.local
   DNS server list :
           10.101.1.6, 10.101.2.2
   Sent update to server : 10.101.1.6
   IP Address(es) :
     10.101.1.18

 The reason the system could not register these RRs was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request.

 You can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your DNS server or network systems administrator. For specific error code, see the record data displayed below.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 38 23 00 00               8#..    

--------------------------------------------------------------------------------------------------------------------------


http://go.microsoft.com/fwlink/events.asp leads to "We're sorry There is no additional information about this  ....."

and ipconfig /registerdns does not work, just adds the same event ID in the logs.

I give it a dynamic address and it pings that okay, 127.0.0.1 pings okay. The A host record in the security tab has the same rights and entries as other server's A host records. A different static IP address pings itself okay and the 10.101.1.18 addess on another machines pings itself okay.

I do not have another NIC to try and the Server has SP2 and the only third party application is an Oracle Databse which talks to another oracle database on another server 10.101.1.19. which was inmstall ion the server on the 6th Nov 08.

I have removed the A host record for 1.18 and manualy added it but still no.

Any ideas?

Thanks.
Fergus.
0
nostrasystems
Asked:
nostrasystems
  • 5
  • 4
1 Solution
 
Darius GhassemCommented:
0
 
nostrasystemsAuthor Commented:
Hi,

I had already tried http://www.eventid.net/display.asp?eventid=11166&eventno=3393&source=DnsApi&phase=1
 But I saw in the second one about giving the servername$ full controll as suspose to write on the A host record.  I then did a registerdns and no entries appeared in event log. But I still cannot ping the IP of the server from the server!
0
 
Darius GhassemCommented:
Disable any firewall's you might have enabled. Do you have 2 NICs?
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
nostrasystemsAuthor Commented:
There is no firewall on the server and I do not have another NIC, only one.
0
 
Darius GhassemCommented:
Maybe resetting the TCP\IP will help.

http://support.microsoft.com/kb/317518
0
 
nostrasystemsAuthor Commented:
Hi,

I tried that, the log is attached. It reset the TCP\IP okay and I rebooted. I got a DHCP address of 10.101.1.94 and was able to ping itself I then set it its proper IP address of 1.18 but still not able to ping. I have set it as 1.17 and it pings okay. See ping results below.
-------------------------------------------------------------
C:\>PING ISS-COREDB

Pinging iss-coredb.PLUTO.local [10.101.1.94] with 32 bytes of data:

Reply from 10.101.1.94: bytes=32 time<1ms TTL=128
Reply from 10.101.1.94: bytes=32 time<1ms TTL=128
Reply from 10.101.1.94: bytes=32 time<1ms TTL=128
Reply from 10.101.1.94: bytes=32 time<1ms TTL=128

Ping statistics for 10.101.1.94:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>PING ISS-COREDB

Pinging iss-coredb.PLUTO.local [10.101.1.18] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 10.101.1.18:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\>PING ISS-COREDB

Pinging iss-coredb.PLUTO.local [10.101.1.17] with 32 bytes of data:

Reply from 10.101.1.17: bytes=32 time<1ms TTL=128
Reply from 10.101.1.17: bytes=32 time<1ms TTL=128
Reply from 10.101.1.17: bytes=32 time<1ms TTL=128
Reply from 10.101.1.17: bytes=32 time<1ms TTL=128

Ping statistics for 10.101.1.17:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
---------------------------------------------------------------------
I have attached the resetlog if it might help.

-Thanks.
resetlog.txt
0
 
Darius GhassemCommented:
Well that is weird but usually you have a firewall that will block the ping but since you have disabled it then you shouldn't have this issue.
0
 
nostrasystemsAuthor Commented:
I still have the issue! Can anyone help?
0
 
Darius GhassemCommented:
Check to see what your dynamic update security level is set for.

http://technet.microsoft.com/en-us/library/cc780714.aspx
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now