<div>
If you cannot access a site or server by name but you can by IP, then it is most likely related to a DNS issue.<br>Make sure you have a forward lookup 'A record' in your domain DNS (assuming a Windows domain) for that server at 10.0.0.148. Otherwise, when you ping, the name will never resolve and can result in this issue.<br><br>If you have the proper A Record in DNS, another issue may be the PC you are attempting to ping from has a DNS entry in the NIC settings which is NOT your local Domain Controller. Such as a static 8.8.8.8 versus the IP of your DNS server. Changing to the DNS server IP may resolve this problem. <br><br>
</div>


President

rwheeler23

IT Manager

Michael Machie

Network Architect and EE TA

Craig Beck

<div>
appearantly in DNS the name is assiciated with localhost for IPv6 (::1).<br>DNS needs to be fixed.&nbsp; (or the host file).
</div>


<div>
<div class="content wysiwyg-content fr-view">
<p>I have a server that is sitting at 10.0.0.148. I can ping that with no problems.<br>Reply from 10.0.0.148: bytes=32 time &lt;1ms TTL=128<br>Reply from 10.0.0.148: bytes=32 time &lt;1ms TTL=128<br>Reply from 10.0.0.148: bytes=32 time &lt;1ms TTL=128<br>Reply from 10.0.0.148: bytes=32 time &lt;1ms TTL=128<br><br>However when I ping the server by name I get<br>Reply from ::1: time&lt;1ms<br>Reply from ::1: time&lt;1ms<br>Reply from ::1: time&lt;1ms<br>Reply from ::1: time&lt;1ms<br><br>Any idea what I need to do to correct this? This is a W2016 server.</p>
</div>
</div>



I have a server that is sitting at 10.0.0.148. I can ping that with no problems.
Reply from 10.0.0.148: bytes=32 time <1ms TTL=128
Reply from 10.0.0.148: bytes=32 time <1ms TTL=128
Reply from 10.0.0.148: bytes=32 time <1ms TTL=128
Reply from 10.0.0.148: bytes=32 time <1ms TTL=128
However when I ping the server by name I get
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Any idea what I need to do to correct this? This is a W2016 server.


If you cannot access a site or server by name but you can by IP, then it is most likely related to a DNS issue.
Make sure you have a forward lookup &#39;A record&#39; in your domain DNS (assuming a Windows domain) for that server at 10.0.0.148. Otherwise, when you ping, the name will never resolve and can result in this issue.
If you have the proper A Record in DNS, another issue may be the PC you are attempting to ping from has a DNS entry in the NIC settings which is NOT your local Domain Controller. Such as a static 8.8.8.8 versus the IP of your DNS server. Changing to the DNS server IP may resolve this problem.


appearantly in DNS the name is assiciated with localhost for IPv6 (::1).
DNS needs to be fixed.  (or the host file).

Pinging server by name not working.


I have a server that is sitting at 10.0.0.148. I can ping that with no problems.
Reply from 10.0.0.148: bytes=32 time &lt;1ms TTL=128
Reply from 10.0.0.148: bytes=32 time &lt;1ms TTL=128
Reply from 10.0.0.148: bytes=32 time &lt;1ms TTL=128
Reply from 10.0.0.148: bytes=32 time &lt;1ms TTL=128
However when I ping the server by name I get
Reply from ::1: time&lt;1ms
Reply from ::1: time&lt;1ms
Reply from ::1: time&lt;1ms
Reply from ::1: time&lt;1ms
Any idea what I need to do to correct this? This is a W2016 server.

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.