• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 283
  • Last Modified:

Ping probems...

I have a machine named MACHINE_A

I go to another machine....MACHINE_B (this is any machine on the network nothing specific).....

I ping (ping 129.1.5.28)

I get a reply.....GREAT!!!!

I ping (ping MACHINE_A)

I get Request Timed Out....

I go to the WINS and DNS servers.  Specifically added static mappings for MACHINE_A 129.1.5.28....Still no go.

What's going on.
0
dspent
Asked:
dspent
  • 6
  • 3
1 Solution
 
sirbountyCommented:
Sounds like you need to Enable NetBIOS over TCP/IP:
  From control panel..
  Right-click your Local Area Connection and click Properties
  Scroll down in "This connection uses the following items:" to find Internet Protocol (TCP/IP)
  Select it (highlight it) and click properties
  Click the Advanced button on the General tab.
  Click the WINS tab.
  Under NetBIOS setting heading
   Click Enable NetBIOS over TCP/IP
  Click OK, OK, OK and close out of Network Connections & Control Panel
0
 
sirbountyCommented:
You can also add an entry in %systemroot%\system32\drivers\etc\LMHOSTS
Open the (LMHOSTS.SAM - sample) file with Notepad to see how it's to be laid out...
0
 
sirbountyCommented:
Oh - and if/when you make changes to LMHOSTS,
 NBTSTAT -R
will reload from lmhosts so you don't have to reboot...
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
dspentAuthor Commented:
nope thats not it....its enabled and is the default config for everymachine.  We use static IP addressing.  Forgot to add also...We have just started (a couple months ago) running our own DNS servers.  Previously we had another company managing DNS....They still are our ISP but we have slowly changed every machine to point to the new DNS server which forwards internet requests to the ISP's DNS.

From what I can gather MACHINE_A's name is associated with another IP address in their system....

When I ping MACHINE_A by name it says

PINGING MACHINE_A [129.1.5.22] with 32 bytes of data

Request Timed Out...
Request Timed Out...
Request Timed Out...
Request Timed Out...

the problem is MACHINE_A is 129.1.5.28
0
 
sirbountyCommented:
What does
NLTEST MACHINE_A
get you for IP address and DNS server info?
0
 
dspentAuthor Commented:
I FIXED IT!!!!

I went into the WINS server and displayed all records.  Then searched for the bad IP and the good IP.  I deleted everything.  I actually found records with both ip's (strange, they weren't there before)....anyway after that I added static entries for this machine with the correct ip and did the same for the DNS server.  everything is working ok now.


Now, my next question is, I'm sure this will work for all of the machines that are using OUR dns/wins servers.....But will the correct information replicate out to our ISP's DNS servers and replace the bad data that started this problem in the first place?
0
 
sirbountyCommented:
Eventually, yes.
If you tombstone those records, the deletions should replicate fine...
0
 
dspentAuthor Commented:
yep....sure did.  I fixed my own problem but I'd rather give points than abandon the question or just close it. so  Thanks sirbounty.
0
 
sirbountyCommented:
Thanx to you too.  Glad you got it sorted.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now