find a computer name for an ip????

[Blankman]

Is there a command I can use or a tool if I have the ip address on my
network that will tell me the associated computer name?

Thanks!

 

[David Candy]

ping /a 127.0.0.1

NSLookup may also be of help in some circumstances

 

[Steve Nielsen]

ping /a 127.0.0.1

This will only ping the local loopback address and not return a hostname.

Steve

 

[Steve Nielsen]

Is there a command I can use or a tool if I have the ip address on my
network that will tell me the associated computer name?

Thanks!

I use Angry IP Scanner:

www.angryziber.com/ipscan

NMapWin is also useful:

www.sourceforge.net/projects/nmapwin

Steve

 

[David Candy]

Cause it does, it returns localhost which is the host name for that ip address.

 

[Steve Nielsen]

Cause it does, it returns localhost which is the host name for that ip address.

"Localhost" is always the host name for 127.0.0.1, but it is not what
the OP asked for, which was the computer name of a machine on the
network. Pinging the loopback address won't give that information.

Steve

 

[David Candy]

It an example you moron. I don't know his network IP addresses. How did you get so stupid.

 

[Steve N.]

It an example you moron. I don't know his network IP addresses. How did you get so stupid.

It's an inappropriate example. Why? IT DOES NOT ANSWER THE OP'S QUESTION.

Pinging the local loopback address (127.0.0.1) as you have suggested,
will *ALWAYS* give you "localhost" for a hostname (unless you have
modified the ETC\HOSTs file to associate it with another hostname (which
would most likely be a mistake)). It's LOCALHOST and has NOTHING to do
with the COMPUTER NAME. These are two distinctly different things.

Try the utilities I posted links for (they are both freeware! Yay!) and
maybe you will learn something. They DO answer directly the OP's request
and they DO work on private LANs (in most, if not all cases), and even
on mant routed WANs (depending on router filter configurations).

FYFI, I have been working in IT for probably much longer than most
people reading/posting here have been alive. Not a boast, merely a fact.
In addition, I'm not always right, in fact I am frequently wrong and
there is an awful lot that I simply do not know (which is one major
reason I frequent this newsgroup - to LEARN. Imagine that!!). I never
have had a problem admitting when I am wrong or simply saying, "I don't
know" (check my posting history here, oh please do! In fact I challenge
you to do so!).

I *rarely* resort to name-calling, such as you have done, in a public
discussion group (save one or two explicitly devoted to "flaming", and
then just for laughs). In your case, however, I just might make an
exception, Mister Candy. The odd thing is, there's really no need for me
to do so, as you apparently do so well enough at degrading yourself with
your own words.

Steve

 

[Steve N.]

It's an inappropriate example. Why? IT DOES NOT ANSWER THE OP'S QUESTION.

Pinging the local loopback address (127.0.0.1) as you have suggested,
will *ALWAYS* give you "localhost" for a hostname (unless you have
modified the ETC\HOSTs file to associate it with another hostname (which
would most likely be a mistake)). It's LOCALHOST and has NOTHING to do
with the COMPUTER NAME. These are two distinctly different things.

Self-correction; should read:

"It's a HOSTNAME and has NOTHING to do with the COMPUTER NAME. These are
two distinctly different things."

Additionally, PING /A does not always return a hostname anyway. It
depends on DNS or the ETC\HOSTS file to resolve an IP address to a hostname.

-Steve

 

[Steve N.]

Self-correction; should read:

"It's a HOSTNAME and has NOTHING to do with the COMPUTER NAME. These are
two distinctly different things."

Additionally, PING /A does not always return a hostname anyway. It
depends on DNS or the ETC\HOSTS file to resolve an IP address to a
hostname.

-Steve

No response in 3 days. It figures. What's the matter Candy, are you
afraid to actually LEARN SOMETHING for a change?

Steve