Ping returns ::1: instead of IP Address

2011-11-13

Question

_{Sunday, November 13, 2011 1:50 AM}

I'm having a problem with my TS Gateway and I think it may be a DNS issue. Windows Server 2008 (not R2) is the server that is having the "issue". If I ping the server using the FQDN from anyplace else on the network it returns the proper IP address of 192.168.10.107 how ever when I ping the FQDN from the same server it returns ::1: If I ping just the server name it returns 192.168.10.107. I've looked though the DNS settings and the Hosts file and everything seems to be ok from my limited knowledge of DNS. Any ideas would be greatly appreciated. Thanks in advance!!

All replies (33)

_{Tuesday, November 15, 2011 8:48 AM ✅Answered}

i dont think the host file has something incorrect ,just usual lines(my opinion)

as dns first try to resolve from hostname then hostfile.

u can let toredo work as usual it will not be a problem,just will have some more traffic on ur network (as it will try to comunicate with ipv6 protocoll first)

toredo is a transition from ipv4 to ipv6,so it make posible that this protocolls comunicate with each other.

in few word.

if an aplication or host support ipv6 ur server will choose this protocoll to comunicate,if not they will use ipv4 as u have both active and running.

in my opinion,no problem if u disable it at the moment if u dont use ipv6 on ur network.

u can re-enable it anytime in the future .

disabing toredo have no impact on system work,is not same as disabling ipv6

this is just my opinion.

Renato

Renato Kurti CCNA,MCP,MCTS,MCITP

_{Tuesday, November 15, 2011 8:18 PM ✅Answered}

I'm siding with Renato, based on the resolution process, and it's not a problem. It's by default. It looks at IPv6 first. This is by design. As for disabling it, Microsoft really doesn't recommend disabling any portions of IPv6. So think about this carefully if you feel disabling any portion of IPv6 may help or not.

Should I disable IPv6? No. Microsoft no longer recommendeds disabling IPv6. - no.
http://msmvps.com/blogs/acefekay/archive/2010/05/27/how-to-disable-rss-tcp-chimney-feature-and-ipv6.aspx

I just tested this out on a Windows 2008 member server, and when I pinged it's single name or it's FQDN, the IPv6 Link-Local address responds. The hosts file looks exactly like yours, except the ::1 is not commented out. The following is an ipconfig and a ping to itself:

==============================================
C:\ipconfig

Windows IP Configuration

   Host Name . . . . . . . . . . . . : hostname
   Primary Dns Suffix . . . . . . . : domain.com
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : domain.com

Ethernet adapter Teamed Local Area Connection:

   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : TEAM : Team #0
   Physical Address. . . . . . . . . : 00-11-43-D7-F8-3A
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2002:4a5e:3041:0:44ce:2832:dd78:ea0e(Pref
erred)
   Link-local IPv6 Address . . . . . : fe80::44ce:2832:dd78:ea0e%13(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.30.30(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : fe80::c2c1:c0ff:fe7c:32be%13
                                       192.168.30.1
   DHCPv6 IAID . . . . . . . . . . . : 335548739
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-51-1B-30-00-11-43-D7-F8-3A

   DNS Servers . . . . . . . . . . . : 192.168.30.10
                                                192.168.30.5
   Primary WINS Server . . . . . . . : 192.168.30.10
   Secondary WINS Server . . . . . . : 192.168.30.5
   NetBIOS over Tcpip. . . . . . . . : Enabled
<the rest was snipped>
==============================================

C:\ping hostname.domain.com or ping hostname - results are the same:

Pinging hostname.domain.com [fe80::44ce:2832:dd78:ea0e%13] from fe80::44ce
:2832:dd78:ea0e%13 with 32 bytes of data:
Reply from fe80::44ce:2832:dd78:ea0e%13: time<1ms
Reply from fe80::44ce:2832:dd78:ea0e%13: time<1ms
Reply from fe80::44ce:2832:dd78:ea0e%13: time<1ms
Reply from fe80::44ce:2832:dd78:ea0e%13: time<1ms

So curious, gpiong back to your original post, why do you think pinging the machine itself would be causing a "problem?"

Your nslookup responds properly to the IPv4 address.

And please note, ping is not the best tool to resolve resolution issues. Nslookup is the better tool. However, even in some cases, such as figuring out an AD issue, especially with AD Sites involved, nslookup doesn't help and would need to look at AD specific diagnostics.

It also depends on the application's resolution requirements. For example, SQL may look at NetBIOS names, whereas if it's an AD enabled or aware app, it will look at DNS, specifically the AD client side funtions to resolve AD SRV data.

Threfore, maybe I am not fully understanding what the "problem" is? Is there some sort of app on the TS that requires a ping response to function? Maybe you can elaborate on what you are seeing as a problem?

Ace Fekay
MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

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

_{Sunday, November 13, 2011 8:32 AM}

this is an IPv6 and it is normal reply if you enable IPv6 on the machine.

Samer F. Mustafa Microsoft Technical Team Leader. [email protected]

_{Sunday, November 13, 2011 8:50 AM}

that is localhost ipv6 ip address, is like 127.0.0.1(IPv4)

loopback addres for testing propose(to test ur NIC when there is no cable connected)

all normal,if u dont need that,just disable ipV6,in local area network,propeties,uncheck microsoft TCP/IP version 6

in hostfile there might be a line with this content,

::1 localhost

u can remove that to or put a # in the start of that line.

** **

Renato Kurti CCNA,MCP,MCTS,MCITP

_{Sunday, November 13, 2011 11:55 AM | 1 vote}

Will that cause problems if the DNS server is ipV4 (Win 2003)? I've also disabled the ipV6 on both cards as mentioned and commented out that portion in the hosts file yet still bringing up the ::1:

_{Sunday, November 13, 2011 1:44 PM | 1 vote}

hmmm thats strange

if no ipv6 is configured that must not come out (did u clear dns cache?) ipconfig /flushdns

no problem for the dns as u dont use ipv6 infrastructure.

i can think that u use ts and dns in the same server and that u have a single zone for all,and this is not recomandet ,u should configure and outside zone and an inside zone.

a temporary solution must be to add the record on ur host file of the server.

192.168.10.107 FQDN

and clear dns cache,the first place to get the ip is cache then host file then dns server.

hope this will help you to solve the problem

for a permanet solution if u need it i have to ask you some questions.

let me know

Renato

Renato Kurti CCNA,MCP,MCTS,MCITP

_{Monday, November 14, 2011 12:32 PM}

Ok I did the poor hosts file fix and that's working though not prefered. I'd prefer the permanent solution as this is on our test soon to be "live" network and it would be nice for DNS to work properly as it doesn't on our current NT 4 domain (ok stop laughing) :-) I really appreciate the help.

_{Monday, November 14, 2011 1:05 PM}

good to hear you make it work,as i told you this is not a permanent solution

for a permanent solution u need a good planification of DNS

i can help with that,but need some info from you

1) servers on ur company and theyr role.(exmp 3 servers wioth this roles each)

2) what ur planing to implement on ur company(exmp.DNS-DHCP-TS\ect ect)

i can help you to develope a good design.(with what u have normally)

Im courently a consultant (normally i will help you free of charge :)

have a nice time

Renato

Renato Kurti CCNA,MCP,MCTS,MCITP

_{Monday, November 14, 2011 1:42 PM}

Well right now we have everything loaded onto 3 servers (test environment). However I'm trying to work out what will be the best thing going forward. As far as servers go moving forward this is what we are heading towards:

DNS/DHCP
AD DS
2 - 3 Terminal Servers (moving away from hosting 90+% of the company desktops and going to remote apps and a few Desktops, so not sure how many yet)
TS Gateway/Web Access (probably a web server of some sort as we run a Intranet site which right now is a linux server but I'd prefer to run windows so I can do ASP which would make my life easier).
Database (SQL Server)
File/Application Server
Backup

As far as physical servers, we have 2 "new ones", and 3 of our current servers (2 are 2 x 2 cores and 1 is 2 x 4 cores) that we are going to migrate over to the "new network" and we are purchasing a new Database Server in Q1 of 2012. We have be toying with the idea of running some virtual servers using RedHat or something similar as the Virtulization Software. We are a smaller company with right around 50 users total with about 32 - 36 on during peak times with a remote location that currently connects to our home office through a direct line T1 (not 100% sure about this one as it was set up long before I got here and could probably be done better but that's another issue).

I think I got everything. If not please let me know.

_{Monday, November 14, 2011 4:16 PM}

Ok I did the poor hosts file fix and that's working though not prefered. I'd prefer the permanent solution as this is on our test soon to be "live" network and it would be nice for DNS to work properly as it doesn't on our current NT 4 domain (ok stop laughing) :-) I really appreciate the help.

To remove the "::1" DNS address from the interface, follow this steps in the following link.

Should I disable IPv6? No. Microsoft no longer recommendeds disabling IPv6.
This article also contains information on how to Disable RSS TCP Chimney Feature and removing IPv6.
How to remove "::1" IPv6 DNS address that shows up in an ipconfg /all
http://msmvps.com/blogs/acefekay/archive/2010/05/27/how-to-disable-rss-tcp-chimney-feature-and-ipv6.aspx

I suggest and recommend to put the hosts file back to default.

I would also suggest to not disable IPv6. It's tied into the OS and may break things. Read the link above for more specifics.

Ace

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

_{Monday, November 14, 2011 4:18 PM}

Ace, our DNS server is Win 2k3 (doh!!! just remembered, sorry), will that cause problems?

_{Monday, November 14, 2011 4:25 PM}

FYI, if the new servers you purchased can handle multiple virtual OS guests comfortably (enough RAM, CPU horsepower, etc), if you purchase a copy of Windows 2008 R2 Enterprise Edition (not the Standard Edition), the licensing feature allows you to install one copy as a HyperV host, and allows you to install up to four (4) guest using the same DVD and PID key.

Here are a couple of links, but I suggest to contact your Microsoft Channel Partner Distributor for specific licensing info. If you don't have one, I can suggest one.

Licensing Guide:
http://www.microsoft.com/en-us/server-cloud/buy/pricing-licensing.aspx

On HypeV:

Windows 2008 benefits. Click on the Virtualization Calculator to apply your scenario:
http://www.microsoft.com/en-us/server-cloud/windows-server/hyper-v-benefits.aspx

In addition, if you only have a total of 50 users and don't expect to grow much further, or at least not beyond 75 users, you can look into Small Business Server 2011 Standard with the Premium add-on. It gives you the ability to use HyperV for the servers, as well as gives you a copy of Exchange 2010, SQL, Sharepoint, etc, all part of the same package.
http://www.microsoft.com/en-us/server-cloud/windows-small-business-server/default.aspx

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

_{Monday, November 14, 2011 4:44 PM}

Yes, they are dual 6 cores currently only 16GB each, but we are going to up them 32GB + once we move to production/end of test phase. I asked the powers that be and there is no interest in the Small Business version. We'd have to add a Network Card or two to do the virtulization, but something we are looking into anyway. Though going the Enterprise Route may be a good idea/choice. Plus we have a dual quad core that may be a good candidate for some of the lighter weight roles.

_{Monday, November 14, 2011 4:47 PM}

Off topic but since you brought up server editions, will 2008R2 Cals work with 2008 Servers? As our two test servers are running 2008(not R2).

_{Monday, November 14, 2011 4:49 PM}

Ace, our DNS server is Win 2k3 (doh!!! just remembered, sorry), will that cause problems?

The "::1" DNS IP is associated with Windows 2008 and WIndows 2008 R2. I haven't seen this associated with Windows 2003 unless you've installed IPv6 for some reason. Originally you posted it's a Windows 2008 server, hence why I replied how to remove it.

Otherwise, if you have IPv6 installed on WIndows 2003, curious, what is its purpose?

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

_{Monday, November 14, 2011 4:51 PM}

I completely forgot that our DNS server is running 2003, I noticed it when I loged into it to check the results of pinging the server in question with the FQDN.

_{Monday, November 14, 2011 4:53 PM}

Yes, they are dual 6 cores currently only 16GB each, but we are going to up them 32GB + once we move to production/end of test phase. I asked the powers that be and there is no interest in the Small Business version. We'd have to add a Network Card or two to do the virtulization, but something we are looking into anyway. Though going the Enterprise Route may be a good idea/choice. Plus we have a dual quad core that may be a good candidate for some of the lighter weight roles.

SOunds fine for HyperV. Just keep in mind, you can't make the HyperV host (the server itself) a domain controller. And if you are installing a DC as a HyperV guest, assuming you are using HyperV, you must "partially disable" the time service in HyperV or you will get AD problems. If using VMWare, you must fully disable the time sync service on the VMWare host.

The time service is important for AD. All machines must be within a 5 min skew or AD Kerb auth will fail. The HyperV host time services is not partially disabled, or VMWare's sf not fully disabled, it will interfere and cause a greater time skew causing numerous problems.

Virtualizing Domain Controllers and the Windows Time Service
http://msmvps.com/blogs/acefekay/archive/2011/08/23/virtualizing-domain-controllers-and-the-windows-time-service.aspx

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

_{Monday, November 14, 2011 4:54 PM}

Off topic but since you brought up server editions, will 2008R2 Cals work with 2008 Servers? As our two test servers are running 2008(not R2).

Licensing is different and applies specifically to the server edition. Contact your channel provider for specifics. If you don't have one, I can suggest one.

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

_{Monday, November 14, 2011 4:59 PM}

I completely forgot that our DNS server is running 2003, I noticed it when I loged into it to check the results of pinging the server in question with the FQDN.

As I said, the IPv6 loopback address, "::1" is what's configured by default if you have IPv6 installed, and I usually see this with Windows 2008 and 2008 R2.

If you are saying you have a 2003 server and do not have a 2008 or 2008 R2, then it tells me IPv6 was installed on 2003. On 2003 you can remove it.

Remove IPv6 Windows 2003:
http://technet.microsoft.com/en-us/library/cc779349(WS.10).aspx

How to install (and remove) and configure IPv6 in Windows 2003 Enterprise:
http://support.microsoft.com/kb/325449

Otherwise, please post an unedited ipconfig /all of all DNS servers you have in your environment, as well as a sample workstation, to get a better understanding of what you have.

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

_{Monday, November 14, 2011 5:13 PM}

Sorry for the confusion, our "test network" is 3 servers, 2 2008 and 1 2003, our DNS/File server is the 2003 Server and the Database and Terminal Servers are both 2008.

DNS Server (2003):

C:\Documents and Settings\Derek>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : ta-test
   Primary Dns Suffix . . . . . . . : Thomas-Agency.local
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : Thomas-Agency.local

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
   Physical Address. . . . . . . . . : 00-0D-61-0C-7A-D1
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.10.202
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.10.10
   DNS Servers . . . . . . . . . . . : 192.168.10.202

Only Workstation physically on the network (XP):

C:\Documents and Settings\George.THOMAS-AGENCY>ipconfig /all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : vistaduoxp
        Primary Dns Suffix . . . . . . . : Thomas-Agency.local
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : Thomas-Agency.local

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix . :
        Description . . . . . . . . . . . : Intel(R) 82566DC Gigabit Network Con
nection
        Physical Address. . . . . . . . . : 00-16-76-B5-A7-04
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.10.9
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.10.10
        DNS Servers . . . . . . . . . . . : 192.168.10.202
                                            192.168.10.10

Terminal Server (2008):

C:\Users\Derek>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : micronxeon5
   Primary Dns Suffix . . . . . . . : Thomas-Agency.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : Thomas-Agency.local

Ethernet adapter Local Area Connection 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Broadcom BCM5716C NetXtreme II GigE (NDIS
VBD Client) #2
   Physical Address. . . . . . . . . : 84-2B-2B-46-5F-30
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Broadcom BCM5716C NetXtreme II GigE (NDIS
VBD Client)
   Physical Address. . . . . . . . . : 84-2B-2B-46-5F-2F
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.10.107(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.10.10
   DNS Servers . . . . . . . . . . . : 192.168.10.202
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 8:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : isatap.{4CACEFB1-E29D-4626-BEC6-B089B024F
2C4}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : isatap.{974D5E70-F728-4419-9324-7CAE38EFB
7C6}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

_{Monday, November 14, 2011 5:39 PM}

Thanks for posting that.

Your gateway (your router) is 192.168.10.10. So what's it doing configured as an DNS address on your ta-test machine?? It's not a DNS address. Read more on this below.

Active Directory's Reliance on DNS, and why you should never use an ISP's DNS address or your router as a DNS address, or any other DNS server that does not host the AD zone name
http://msmvps.com/blogs/acefekay/archive/2009/08/17/ad-and-its-reliance-on-dns.aspx

I think you said this is not an AD environment. Whether you do or not, the same thing applies with internal name resolution with an internal DNS server.

The rule is if you are using an internal DNS server, you must ONLY specify the internal DNS server, and no outsiders. If you do, including the router, which isn't really a DNS server but proxying all DNS queries to an outside address, then you will get inconsitent results across the board, because those outside DNS server will not have the any knowledge of your internal zone or records.

As for pinging the TS server itself, and you are still seeing a ::1 response, please check the hosts file again, and make sure you only have:

localhost 127.0.0.1
; localhost ::1

Then run an ipconfig /flushdns

Try the ping again.

If you are still seeing it, please post the actual ping the way you are pinging it, and its results, as well as an nslookup of the same name.

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

_{Monday, November 14, 2011 5:47 PM}

Ok it's cringe time... the Terminal Server in question is also the AD DS, TS Gateway and IIS Server :-) I did mention it's a test environment right :-)
Secondly I didn't set up that portion of the network so don't blame me, I at least know it's bad :-) Still new to this part of the PC World, thus the "Jack of All Trades Master of None" part. However I'm trying to learn vs just get answers so I think I'm right in that part at least. As you may have noticed buried up above our current network DNS doesn't work and it's the same setup which was set up by the same person. I've given up on that network and trying to fix this one as I'll be inheriting it once he retires.

So I'm guessing I need to "re-do" the DNS for the network?

_{Monday, November 14, 2011 5:52 PM}

Ok minor change to the above statement (sigh), the 2003 Server is also a Domain Controller, along with the 2008 Terminal Server/everything else under the sun Server. I need to start drinking more I think....

_{Monday, November 14, 2011 6:39 PM}

Ok I have changed the DNS Setting and set up the forwarder on the DNS server, All 4 machines now only have the DNS Server of 192.168.10.202
Little nervous at first (never did it before), but so far it's working...
I deleted the entires from the Hosts file and flushed the DNS and it's back to giving me the ::1: (Is this ok, or will it pose problems?) Also would it be worth it to install the IPV6 on the 2003 DNS server, even though it won't be migrating and should be going away in the next 2 - 3 months (moving it to 2008 or 2008 R2).

_{Monday, November 14, 2011 6:53 PM}

I don't know why you were nervous? It wasn't configured right the first time. That would make me nervous not having it configured properly!

Also, I don't understand why you are still getting the ::1 as a response. Did you run an ipconfig /flushdns?

We really, really need to see examples, and from what machine you are doing this from to further evaluate it.

Let's try this so as we're clear as to what we need to see.

From the DC:

ping micronxeon5.Thomas-Agency.local
Pint micronxeon5
Run:

C:\nslookup <enter>
micronxeon5.Thomas-Agency.local

(post the results)

then try:
micronxeon5

(post the results)

Repeat from the TS machine.

Repeat from a workstation. Post the results.

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

_{Monday, November 14, 2011 7:13 PM}

What can I say, changing the DNS settings on a server that is being used by other people (including my boss) can cause problems... but then again you are right, it was worse when it was done wrong. Now for the fun talk of "Hey I fixed DNS on the new network" talk...

Anyways, first... Thank you for all your help I greatly apprecaite it, I'm learning quite a bit more about DNS!!

Second:

From the DC/DNS Server
C:\Documents and Settings\Derek>ping micronxeon5.Thomas-Agency.local

Pinging micronxeon5.Thomas-Agency.local [192.168.10.107] with 32 bytes of data:

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

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

C:\Documents and Settings\Derek>ping micronxeon5.Thomas-Agency.local

Pinging micronxeon5.Thomas-Agency.local [192.168.10.107] with 32 bytes of data:

Reply from 192.168.10.107: bytes=32 time<1ms TTL=128
etc...

C:\Documents and Settings\Derek>ping micronxeon5

Pinging micronxeon5.Thomas-Agency.local [192.168.10.107] with 32 bytes of data:

Reply from 192.168.10.107: bytes=32 time<1ms TTL=128
etc....

C:\Documents and Settings\Derek>nslookup
Default Server: ta-test.thomas-agency.local
Address: 192.168.10.202

> micronxeon5
Server: ta-test.thomas-agency.local
Address: 192.168.10.202

Name: micronxeon5.Thomas-Agency.local
Address: 192.168.10.107

=================================================================

Workstation:

C:\Documents and Settings\George.THOMAS-AGENCY>ping micronxeon5

Pinging micronxeon5.Thomas-Agency.local [192.168.10.107] with 32 bytes of data:

Reply from 192.168.10.107: bytes=32 time<1ms TTL=128
etc...

C:\Documents and Settings\George.THOMAS-AGENCY>ping micronxeon5.Thomas-Agency.lo
cal

Pinging micronxeon5.Thomas-Agency.local [192.168.10.107] with 32 bytes of data:

Reply from 192.168.10.107: bytes=32 time<1ms TTL=128
Reply from 192.168.10.107: bytes=32 time<1ms TTL=128
etc...

C:\Documents and Settings\George.THOMAS-AGENCY>nslookup
Default Server: ta-test.thomas-agency.local
Address: 192.168.10.202

> micronxeon5
Server: ta-test.thomas-agency.local
Address: 192.168.10.202

Name: micronxeon5.Thomas-Agency.local
Address: 192.168.10.107

===================================================================

TS (Micronxeon5)

C:\Users\Derek>ping micronxeon5

Pinging micronxeon5.Thomas-Agency.local [::1] from ::1 with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

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

C:\Users\Derek>ping micronxeon5.Thomas-Agency.local

Pinging micronxeon5.Thomas-Agency.local [::1] from ::1 with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

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

C:\Users\Derek>nslookup
Default Server: ta-test.thomas-agency.local
Address: 192.168.10.202

> micronxeon5
Server: ta-test.thomas-agency.local
Address: 192.168.10.202

Name: micronxeon5.Thomas-Agency.local
Address: 192.168.10.107

_{Monday, November 14, 2011 11:57 PM | 1 vote}

haha why i dident think about this before

i think i know the "problem" now (is not a problem at all)

Tunnel adapter Local Area Connection* 11:

**   Media State . . . . . . . . . . . : Media disconnected**
**   Connection-specific DNS Suffix . :**
**   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface**
**   Physical Address. . . . . . . . . : 02-00-54-55-4E-01**
**   DHCP Enabled. . . . . . . . . . . : No**
**   Autoconfiguration Enabled . . . . : Yes**

u have just wake up teredo

and make ipv6 the best ping response ,try ping -4 to get ipv4 address

u have to see what make it active

The Teredo component is enabled but inactive by default. In order to become active, u must either install an application that needs to use Teredo, or configure the advanced settings on a Windows Firewall exception to use edge traversal.

to disable teredo use this command (not before u find what make it active and if u need it)

ntesh interface teredo set state disable

u can find here more info

http://technet.microsoft.com/en-us/library/cc770710(WS.10).aspx

Tell me the result pls as i cant test it right now :(

Good luck

Renato Kurti CCNA,MCP,MCTS,MCITP

_{Tuesday, November 15, 2011 12:50 AM}

I have a question before I go disabling stuff, is this actually a "problem" or just the way things work with IPv6? I think I mentioned it but if not our current network is running off a NT 4 DC, so a lot of these stuff is "new" to me, well that and up until a few months ago I was a programmer and now I'm the "everything guy". So I'm trying to learn as much as I can and not screw too much up as I go along.

_{Tuesday, November 15, 2011 4:24 AM}

Just to check something before disabling anything, can you first post your hosts file to allow us to take a look, please?

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

_{Tuesday, November 15, 2011 1:29 PM}

Nothing too special:

# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

127.0.0.1 localhost
#::1 localhost

That's from the "example" part to the bottom of the file...

_{Wednesday, November 16, 2011 10:45 AM}

i think i got misundestood

i dident recomend to disable anything,i just say it to isolate the problem,as Ace say is not recomanded to disable anything from microsoft.

as i say before,i think ur server is ok ,so is nothing wrong in cofiguration in DNS .

what it was supposed to be in the start of this post.

now you may have a full picture of the situation.

so i agree with ACE last post:

** **

Renato Kurti CCNA,MCP,MCTS,MCITP

_{Wednesday, November 16, 2011 12:26 PM}

Originally I was having problems (well I still am) with my TS Web Access and the one error was that it wasn't able to find the Terminal Server (which is the same server as the gateway). I know we have problems with our current networks DNS so I wanted to make sure that the ::1: wasn't causing a problem as I'm new to this part of my job. In the process of going through this I have learned a lot more about DNS and have it working "properly" now and not pointing to the router (I always thought that was wrong/didn't seem right). So I guess we are good to go for this part at least. Thanks!!

_{Thursday, March 29, 2018 8:41 AM}

If the problem is the ping replay with ipv6 displayed try ping -4 .... this display ipv4

Share via

Ping returns ::1: instead of IP Address

Question

All replies (33)

Additional resources