MediaSmartServer.net http://www.mediasmartserver.net/forums/ |
|
DNS resolves to 127.0.0.1 on 2WIRE 3800HGV-B U-verse gateway http://www.mediasmartserver.net/forums/viewtopic.php?f=7&t=11610 |
Page 1 of 1 |
Author: | msawyer91 [ Thu Nov 17, 2011 1:38 pm ] |
Post subject: | DNS resolves to 127.0.0.1 on 2WIRE 3800HGV-B U-verse gateway |
In the last few weeks, I've noticed an issue that I can't seem to put my finger to. A couple weeks ago, I was remoted into my WHS 2011 box via remote desktop, and I rebooted it. Since the server was sitting a few feet away, the health light turning solid was a visual cue that the server was booted back up. When I tried to remote back into it, I got this error message: "Your computer could not connect to another console session on the remote computer because you already have a console session in progress." I googled and dug around, but to make an extremely long story really, really short, the problem was this. If I pinged the server's name (HUNKAHUNKASLAB), the response I got back was 127.0.0.1. In other words, the desktop was trying to connect to itself! The response I should have gotten was 192.168.1.79--the IP address this server has had for over 2 months, even after several reboots. Today I rebooted a virtual machine, named PARIETALBONE, because it was set to NAT and not direct connection. When I pinged PARIETALBONE from my work laptop (MSAWYER6), the response I got back was 127.0.0.1! PARIETALBONE uses WHS 2011 for backups, but when I used Remote Access on the WHS 2011 box and tried connecting to PARIETALBONE, the desktop for HUNKAHUNKASLAB (the WHS 2011 server) appeared. And so I remoted into WHS 2011 and pinged PARIETALBONE. 127.0.0.1 was the response! Running commands such as ipconfig /flushdns, nbtstat -R and even restarting the dnscache (DNS Client) service does NOT fix the problem. Creating a HOSTS file entry or rebooting the machine seems to be the only answer. If I ping a machine I know does not exist (i.e. HELLOWORLD) on my home network, I get the response that "Ping request could not find the host name." This is an expected response. But if a machine that was on the network drops off for a little bit (i.e. a reboot), why would ping requests to that machine report back 127.0.0.1 ??? If I connect to http://192.168.1.254 (the 2WIRE AT&T U-verse router), the machine shows up there as online and has the CORRECT IP address. And all of the computers show 192.168.1.254 as the default gateway AND as the DNS server. The router model is 2WIRE 3800HGV-B. Did a recent Windows Update bring this about? This is very annoying. I don't like having all these HOSTS file entries, as doing this on multiple systems is just not a good practice. EDIT: This problem is appearing on my computers running Windows 7 (one Ultimate, one Enterprise), Windows Server 2008 R2 and WHS 2011. I have not yet noticed if it appears on my WHS v1 box or a virtual machine running Server 2003. EDIT #2: I tried disabling NetBIOS lookups, LMHOSTS lookups and IPv6. None of these fixed the problem. |
Author: | msawyer91 [ Thu Nov 17, 2011 3:46 pm ] |
Post subject: | Re: DNS resolves to 127.0.0.1 on 2WIRE 3800HGV-B U-verse gat |
Some additional information may prove helpful. I decided to ping the machine PARIETALBONE from my personal laptop. Here's what I get back. I also did a route print, which I found in this article (it's old, but describes the same problem): http://www.computing.net/answers/window ... 72249.html Code: Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Windows\system32>ping parietalbone Pinging parietalbone.gateway.2wire.net [127.0.0.1] with 32 bytes of data: Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Ping statistics for 127.0.0.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Windows\system32>route print =========================================================================== Interface List 11...98 4b e1 a1 17 8f ......Realtek PCIe GBE Family Controller 14...e0 2a 82 ca 9e bd ......Bluetooth Device (Personal Area Network) 1...........................Software Loopback Interface 1 12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 19...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface 18...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.89 10 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 192.168.1.0 255.255.255.0 On-link 192.168.1.89 266 192.168.1.89 255.255.255.255 On-link 192.168.1.89 266 192.168.1.255 255.255.255.255 On-link 192.168.1.89 266 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 192.168.1.89 266 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 192.168.1.89 266 =========================================================================== Persistent Routes: None IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 19 58 ::/0 On-link 1 306 ::1/128 On-link 19 58 2001::/32 On-link 19 306 2001:0:4137:9e76:3c80:1e42:9cf8:b184/128 On-link 11 266 fe80::/64 On-link 19 306 fe80::/64 On-link 19 306 fe80::3c80:1e42:9cf8:b184/128 On-link 11 266 fe80::c9a8:4a34:a27b:ce9/128 On-link 1 306 ff00::/8 On-link 19 306 ff00::/8 On-link 11 266 ff00::/8 On-link =========================================================================== Persistent Routes: None C:\Windows\system32> If I remote into the WHS 2011 box, which has only a single network connection (you probably noticed above the laptop has a wired connection to the primary network and a wireless connection to the development/test network I have at home). Here are the results from the WHS 2011 box (an EX487): Code: C:\Users\Administrator>ping parietalbone Pinging parietalbone.gateway.2wire.net [127.0.0.1] with 32 bytes of data: Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Ping statistics for 127.0.0.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\Administrator>route print =========================================================================== Interface List 11...00 0a e4 89 e1 96 ......Realtek PCIe GBE Family Controller 1...........................Software Loopback Interface 1 13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 12...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.79 10 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 192.168.1.0 255.255.255.0 On-link 192.168.1.79 266 192.168.1.79 255.255.255.255 On-link 192.168.1.79 266 192.168.1.255 255.255.255.255 On-link 192.168.1.79 266 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 192.168.1.79 266 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 192.168.1.79 266 =========================================================================== Persistent Routes: None IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 12 58 ::/0 On-link 1 306 ::1/128 On-link 12 58 2001::/32 On-link 12 306 2001:0:4137:9e76:306c:17ce:9cf8:b184/128 On-link 11 266 fe80::/64 On-link 12 306 fe80::/64 On-link 12 306 fe80::306c:17ce:9cf8:b184/128 On-link 11 266 fe80::d8fe:3303:100f:a92/128 On-link 1 306 ff00::/8 On-link 12 306 ff00::/8 On-link 11 266 ff00::/8 On-link =========================================================================== Persistent Routes: None C:\Users\Administrator> The 192.168.1.254 identified as the Gateway in the IPv4 table for both computers is the IP of the 2WIRE router, or what AT&T U-verse calls the Residential Gateway. If I pull up the website for that device (http://192.168.1.254), I very clearly see the machine PARIETALBONE as being online, with a DHCP IP of 192.168.1.81. And since 192.168.1.254 is the sole DNS server for both of these computers, WHERE is Windows coming up with 127.0.0.1 when the DNS server (the Residential Gateway) very clearly shows 192.168.1.81 is the IP address of PARIETALBONE? |
Author: | msawyer91 [ Thu Nov 17, 2011 4:22 pm ] |
Post subject: | Re: DNS resolves to 127.0.0.1 on 2WIRE 3800HGV-B U-verse gat |
I think the problem may be solved. I have several network utilities on my iPhone, so I decided to ping PARIETALBONE from my iPhone. Why not rule out Windows as the guilty party? Sure enough, 127.0.0.1 was the result! So that effectively lets Microsoft off the hook. Attachment: And so I decided to poke around on problems with 2WIRE and/or U-verse and 127.0.0.1. And I found some forum hits. Here were two that really stuck out: http://www.dslreports.com/forum/r263937 ... 3800HGV-B- http://arstechnica.com/civis/viewtopic. ... &t=1157167 Interestingly, these posts seemed to focus on two things. A 2WIRE residential gateway model 3800HGV-B with firmware version 6.3.7.42-plus.tm. I checked mine. Model 3800HGV-B? Check. Firmware version 6.3.7.42-plus.tm? Check. Sadly, the resolution seemed to be to perform a factory reset. This obliterates all stored settings, included port forwarding (I have dozens), password, wireless configuration, etc. Performing a simple reboot (including an unplugging of the power cord) did not resolve the problem. However, some folks suggested trying the simpler, less destructive "clear device" approach, followed by a reboot. I tried this, and it seems to have worked! |
Author: | yakuza [ Fri Nov 18, 2011 1:33 pm ] |
Post subject: | Re: DNS resolves to 127.0.0.1 on 2WIRE 3800HGV-B U-verse gat |
I have to admit I was stumped, though it did sound like a DNS issue which would have been performed by your router. Glad you got it working, at least for now, thanks for sharing the solution. |
Author: | msawyer91 [ Sun Nov 20, 2011 3:55 pm ] |
Post subject: | Re: DNS resolves to 127.0.0.1 on 2WIRE 3800HGV-B U-verse gat |
Thanks Alex. Unfortunately it did clear all of my firewall (port forward settings). I didn't realize this right away. I left for deer hunting Friday night and yesterday my mom called trying to access my SharePoint server (she has a site on it), and couldn't. Today I checked and saw all my port forwarding settings were gone. Fortunately the custom applications (names, ports) were still defined, so I just had to reassign them to their targets. |
Author: | yakuza [ Sun Nov 20, 2011 11:46 pm ] |
Post subject: | Re: DNS resolves to 127.0.0.1 on 2WIRE 3800HGV-B U-verse gat |
That's a bummer you lost all the port forwards, what a pain! I gotta say my few interactions with 2Wire have never been pleasant, I found the configuration to be super confusing. I've been very pleased with the Tomato firmware on my Linksys routers. |
Page 1 of 1 | All times are UTC - 7 hours [ DST ] |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |