Not able to ping
stumped
itself... this is occuring even when i am giving the IP address.. but i am
able to ping the machine from another machine..could someone suggest a
solution for this...???
--
A Diamond is a just Piece of Coal that did well under pressure.
Herb Martin
"stumped" <stu...@discussions.microsoft.com> wrote in message
news:20165A42-08BB-4868...@microsoft.com...
>I am working on Windows Server 2003.. i am unable to ping the machine from
> itself... this is occuring even when i am giving the IP address.. but i am
> able to ping the machine from another machine..could someone suggest a
> solution for this...???
Unlikely to be an accurate report -- sorry for saying this but it just isn't
likely.
If you ping 192.168.2.1 from another machine successfully you will
(practically)
always be able to ping that SAME machine from its own command prompt.
Most likely the IP address is being used by another machine.
Have you tried pinging 127.0.0.1?
IF this fails then IP is not initialized and bound to an adapter and this
would
pretty much prove that you are reaching some OTHER machines when you
do the ping remotely.
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
stumped
that when i pinged the machine with its name it showed an IP address
aaa.bbb.ccc.ddd.. but when i did the same from another machine it showed as
aaa.bbb.ccc.eee... So i tried the latter IP address from the local machine
and was able to ping it... as far as 127.0.0.1 goes i am able to get a
response for that ...
--
A Diamond is a just Piece of Coal that did well under pressure.
AJR
localhost.
"stumped" <stu...@discussions.microsoft.com> wrote in message
news:20165A42-08BB-4868...@microsoft.com...
Herb Martin
> now that you had mentioned it i tried the whole procedure again.. i
> noticed
> that when i pinged the machine with its name it showed an IP address
> aaa.bbb.ccc.ddd.. but when i did the same from another machine it showed
> as
> aaa.bbb.ccc.eee... So i tried the latter IP address from the local machine
> and was able to ping it... as far as 127.0.0.1 goes i am able to get a
> response for that ...
When working from the machine itself you should always be double checking
(what you think is) the IP by running IPConfig:
IPconfig /all
Herb Martin
"AJR" <ajr...@comcast.net> wrote in message
news:%23FP3%238hSH...@TK2MSFTNGP05.phx.gbl...
> To ping a computer "itself " from its keyboard- you ping 127.0.0.1 or ping
> localhost.
There is nothing wrong with also using the IP. They are almost precisely
equivalent in effect.
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)