Jump to content

Some Pc's Not Resolving


Depco
 Share

Recommended Posts

My company has a fractional T1 and all users are conected to it through a hub. Some of our PC's are resolving to TCH and some are resolving to our old host.

 

I cleared out the temp files and did a release all, renew all for our internal IP addresses. They are assigned through DHCP on a Windows 2000 server.

 

This is preventing some users from getting their email too.

 

How can this be?

Link to comment
Share on other sites

CheckDNS shows a good resolve to TCH.

 

From a machine in your network that is NOT getting through, run a tracert to your domain and see where it falls. Then also run a tracert from one that does resolve to TCH. Compare the two to see where you're losing the DNS update.

Link to comment
Share on other sites

Not sure what to make of this.

This trace is for a PC that resolves corectly:

 

C:\>tracert www.depcopump.com

 

Tracing route to depcopump.com [207.44.240.63]

over a maximum of 30 hops:

 

1 <1 ms <1 ms <1 ms 192.168.100.1

2 * * * Request timed out.

3 * * * Request timed out.

4 * * * Request timed out.

5 * * * Request timed out.

6 * * * Request timed out.

7 * * * Request timed out.

8 * * * Request timed out.

9 * * * Request timed out.

10 * * * Request timed out.

11 * * * Request timed out.

12 56 ms 55 ms 56 ms server23.totalchoicehosting.com [207.44.240.63]

 

 

Trace complete.

 

This PC is not resolving correctly:

 

C:\>tracert www.depcopump.com

 

Tracing route to depcopump.com [66.216.42.76]

over a maximum of 30 hops:

 

1 <1 ms <1 ms <1 ms 192.168.100.1

2 * * * Request timed out.

3 * * * Request timed out.

4 * * * Request timed out.

5 * * * Request timed out.

6 * * * Request timed out.

7 * * * Request timed out.

8 * * * Request timed out.

9 * * * Request timed out.

10 * * * Request timed out.

11 * * * Request timed out.

12 63 ms 72 ms 63 ms NODE-76.HOSTING-NETWORK.COM [66.216.42.76]

 

 

Trace complete.

Link to comment
Share on other sites

To check the computers settings, at a command prompt, type ipconfig /all

The last entry should be "DNS Servers." Normally a DHCP server will set these, so if they're getting their IPs from the same DHCP server then the DNS servers should also be the same. But apparently these are not.

 

Really, the traceroutes themselves make no difference -- the failure to resolve happens between the requesting computer and the DNS server before the traceroute even begins.

 

Notice how the bad one starts like this:

Tracing route to depcopump.com [66.216.42.76]

 

And the good one starts like this:

Tracing route to depcopump.com [207.44.240.63]

 

The one that's not resolving is plain and simple getting a bad answer from its DNS server.

 

What OS are these machines? If they turn out to have the same DNS server(s), let us know what those are and the OS of the problem machines, and maybe I can help out some more.

Link to comment
Share on other sites

True enough, but if the only answer it knows is that badly out of date then it seems like a "bad" answer to me.

 

I suspect some of these machines have DNS servers hard-coded into them while the others are getting their DNS server setting from DHCP.

Link to comment
Share on other sites

Ah, this is a possibility too. Still, it is odd that they have one or more servers (or clusters) so out of synch.

 

Now if only we could get those "ipconfig /all" results cut-and-pasted in here, we could maybe solve this one!!!

Link to comment
Share on other sites

Thanks for all the activity on this post!

 

I went to the machines that were not working correctly and I specifically disabled netBIOS over TCP/IP. Now they all work.

 

All machines should be getting their settings from DHCP.

 

This machine works:

I:\>ipconfig /all

 

Windows IP Configuration

 

Host Name . . . . . . . . . . . . : davidm

Primary Dns Suffix . . . . . . . : DepcoPump

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : DepcoPump

 

Ethernet adapter Local Area Connection:

 

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC

Physical Address. . . . . . . . . : 00-04-61-42-D0-4C

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.xxx.xxx

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.100.1

DHCP Server . . . . . . . . . . . : 192.168.100.2

DNS Servers . . . . . . . . . . . : 192.168.100.2

206.222.97.82

206.222.97.50

Lease Obtained. . . . . . . . . . : Monday, May 05, 2003 7:25:17 AM

Lease Expires . . . . . . . . . . : Tuesday, May 13, 2003 7:25:17 AM

 

Thanks for the help!!

Dave

Link to comment
Share on other sites

I'm having what I think is the same problem.... we are two machines on a hub. Mine is not resolving (although it has sporadically resolved over the past two days). My domain (newly transferred to TCH) is virtualconceptions.com. I ran checkdns...

 

Answer from m.root-servers.net: domain 'virtualconceptions' not found.

 

Never mind..... I got it fixed

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...