dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
6007
Grok451
join:2008-10-08
Temple City, CA

Grok451

Member

2Wire resolves local IP addresses incorrectly

The following command sequence and output shows the 2Wire returning inconsistent results. It resolves a local IP as one device name, but then it resolves a diffent device name back to the first IP.

C:\>net stop dnscache

The DNS Client service was stopped successfully.

C:\>ipconfig /displaydns

Windows IP Configuration

Could not display the DNS Resolver Cache.

C:\>nslookup 192.168.1.71
Server: home
Address: 192.168.1.254

Name: philleecheesesteak
Address: 192.168.1.71

C:\>nslookup pennys-ipod-3
Server: home
Address: 192.168.1.254

Name: pennys-ipod-3.gateway.2wire.net
Address: 192.168.1.71

Server "home" is the 2Wire at 192.168.1.254 as expected. Addresses are dhcp assigned. "philleecheesesteak" is not currently on the network, but once was and at that time was assigned the IP listed. "pennys-ipod-3" is currently connected.

When I restart the DNS client service and display the dns cache, "philleecheesesteak" shows up, but "pennys-ipod-3" is nowhere to be found.

71.1.168.192.in-addr.arpa
----------------------------------------
Record Name . . . . . : 71.1.168.192.in-addr.arpa
Record Type . . . . . : 12
Time To Live . . . . : 41688
Data Length . . . . . : 4
Section . . . . . . . : Answer
PTR Record . . . . . : philleecheesesteak

Record Name . . . . . : homeportal.gateway.2wire.net
Record Type . . . . . : 1
Time To Live . . . . : 41688
Data Length . . . . . : 4
Section . . . . . . . : Additional
A (Host) Record . . . : 192.168.1.254

What's going wrong and how do I fix this?

wayjac
MVM
join:2001-12-22
Indy

wayjac

MVM

You can clear all the names/ip's on the resets page
Grok451
join:2008-10-08
Temple City, CA

Grok451

Member

said by wayjac:

You can clear all the names/ip's on the resets page

Sorry, forgot to put that in the original post. I already did that and verified that the device list was cleared. It did not fix the problem.

wayjac
MVM
join:2001-12-22
Indy

wayjac

MVM

Did you ever put the philleecheesesteak name and ip on the 2wire 2wire dns resolve page

Is the name philleecheesesteak listed on the firewall settings page
Grok451
join:2008-10-08
Temple City, CA

Grok451

Member

said by wayjac:

Did you ever put the philleecheesesteak name and ip on the 2wire 2wire dns resolve page

Is the name philleecheesesteak listed on the firewall settings page

No, to both questions.

wayjac
MVM
join:2001-12-22
Indy

wayjac

MVM

I have no more suggestions for you
bbear2
Premium Member
join:2003-10-06
dot.earth

bbear2 to Grok451

Premium Member

to Grok451
Have you tried a factory reset of the router?
Grok451
join:2008-10-08
Temple City, CA

Grok451

Member

said by bbear2:

Have you tried a factory reset of the router?

Haven't tried that - hope to avoid having to do that.
bbear2
Premium Member
join:2003-10-06
dot.earth

bbear2

Premium Member

said by Grok451:

said by bbear2:

Have you tried a factory reset of the router?

Haven't tried that - hope to avoid having to do that.

Have you at least done a reboot?
Grok451
join:2008-10-08
Temple City, CA

1 edit

Grok451

Member

Yes, I have rebooted. I have also cleared the device list so that the 2Wire would rediscover devices. I verified that the device list was empty and then it started to be populated with the wired devices and more were added as wireless devices attached. The device list appears to be accurate, but when I use nslookup (and also a utility, WnetWatcher: »nirsoft.net/utils/wirele ··· her.html) about a half-dozen out of 50+ devices come up with incorrect device names.
bbear2
Premium Member
join:2003-10-06
dot.earth

bbear2

Premium Member

To further troubleshoot, I would need to see the device list & the DNS Name Table.

»192.168.1.254/xslt?PAGE= ··· PAGE=J08
»192.168.1.254/xslt?PAGE= ··· PAGE=J38
Grok451
join:2008-10-08
Temple City, CA

Grok451

Member


Device List

Name Table

Device at 192.168.1.247
Device List and Name Table shown.

nslookup for the following IPs show incorrect names:

192.168.1.69 - keithslappy (instead of Nancy-PC)
192.168.1.72 - DennisAcer (instead of shawns-iphone)

Another anomaly: Note that "WAP-Closet" is shown in the Device List as "(not set)" and does not appear in the Name table, even though that device has been configured with a static IP and is up and active on the network at 192.168.1.247.

Thanks for taking a look at this!
bbear2
Premium Member
join:2003-10-06
dot.earth

1 edit

bbear2

Premium Member

And you can confirm that ALL of these devices are DHCP and not staic IPs?

To confirm, from the 2wire's perspective, look at the Device Status of each device on this page: »192.168.1.254/xslt?PAGE= ··· PAGE=C07

They should all say either Connected DHCP or Not Connected. Let me know if you have anything that says otherwise.
Grok451
join:2008-10-08
Temple City, CA

Grok451

Member

Click for full size
Address Allocation
The is the Address Allocation page. There are some static IP's for the WAP devices (192.168.1.246 - 249) and the LAN printer (192.168.1.101). The rest of the devices are DHCP.
bbear2
Premium Member
join:2003-10-06
dot.earth

bbear2 to Grok451

Premium Member

to Grok451
ok this helpful. One more page please and this should be the last one. »192.168.1.254/xslt?PAGE= ··· PAGE=C06
Grok451
join:2008-10-08
Temple City, CA

1 edit

Grok451

Member

Click for full size
Here you go!
bbear2
Premium Member
join:2003-10-06
dot.earth

bbear2 to Grok451

Premium Member

to Grok451
OKAY. Notice in the upper right corner the DHCP range: 192.168.1.64 - 192.168.1.253. And from your previous post you have static IPs at 192.168.1.246 - 192.168.1.249. This is not good.

What you've done here is to assign some DHCP addresses that the 2wire thinks are available as static. I know the 2wire didn't complain with a warning or error either. But in my direct experience, I've done this too, and determined that when you muck with the 2wires' DHCP addresses it does strange unpredictable things; not unlike what you were describing.

To try to validate this, you have two choices, one is to redefine your DHCP address range to be sure it does NOT contain your static addresses --- or you can redefine your static IPs to be within the 192.168.1.1 - .63 range in which it is currently defined.
Grok451
join:2008-10-08
Temple City, CA

Grok451

Member

Interesting. Thank you so much for the analysis.

This will take some planning as I have some firewall rules to change and a LAN printer that is leased from a vendor with static IP at 192.168.1.101.

I'll post the results when I'm able to implement the changes.

Thanks again!