Re: TCP/IP Question

From: Kurt (kurtl_at_olypen.com)
Date: 09/17/04


Date: Thu, 16 Sep 2004 21:30:58 -0700


There, in your own reply you've listed every conceivable falacy in your
position.

>". . .regardless of the question . . ."

The question is what this is all about.

> . . ."this idea of installing network protocols implies a network card -
> why not ping the local address . . . "

You're looking for implications. There is no room for this in test taking.
Besides, do a "route print" from the command line and find your local
address. What is the gateway and interface if you ping the local address as
you state? Yep, they're both 127.0.0.1!

> . . ."In most real world scenario's . . ."

This is not the real world, this is a test question.

> ". . .In the old TCP/IP
> course MS would actually tell you that if you wanted to test TCP/IP
> conectivity you should:"

Once again, there is nothing in the question about network connectivity.
Only that the protocol installation succeeded.

> ". . . ok newer courseware such as that in 2276 DOES tell you (chapter 5
pg26/27)
> to start with the loopback but they are also looking at it from a position
> of you have a problem and want to find out were it dies."

You're still answering the wrong question. There is nothing in the question
dealing with connection problems. Only that the protocol got installed
correctly.

> ". . . and the question be damned ..."

The question is what this is all about.

...kurt

"Neil" <neilmcse@nospamforyou.com> wrote in message
news:Xns9566E9CF165B4neilmcsehotmailcom@207.46.248.16...
> babbling on and on again "Kurt" <kurtl@olypen.com> spewed in
> news:10kkhvdoun118c6@corp.supernews.com:
>
> >
> > Why is it wrong? There is no other answer that can positively identify
> > whether TCP/IP is installed correctly, regardless of success or failure,
> > without the possibiity of having to take more steps. The argument that
> > pinging a remote host is the best step implies that you are testing for
> > network connectivity. There's not any part of the question that says
> > anything about being able to connect to a network device. Only that you
> > determine if TCP/IP is installed correctly. The fact is if the question
> > asked, "What is the first step she should take to determine if she is
> > properly configured for the network", D would absolutely be the right
> > answer. But that's not what's being asked. _Only_ whether TCP/IP is
> > installed.
>
> I am going to stand my ground and say, regardless of the question, the
> proper procedure is to ping the remote host - nay to access a remote
> system. this idea of installing network protocols implies a network card -
> why not ping the local address. In most real world scenario's a NIC is
> attached to a cable which is attached to a router which is attached to
some
> remote systems (that internet thingy is a common one). In the old TCP/IP
> course MS would actually tell you that if you wanted to test TCP/IP
> conectivity you should:
>
> 1) verify your ip configuration using IPCONFIG
> 2) Ping 127.0.0.1
> 3) Ping your address
> 4) ping the defualt gateway
> 5) ping a remote host
>
> and then there was the statement over the page that promptly told you that
> if you start with step 5 the others are good by default. Should we take it
> to the step of following MS direction and check the output of IPCONFIG
> first? pinging the loopback only tells you that the stack is installed,
not
> that it is configured correctly. at the least, to test proper connectivity
> with IP you should be able to ping another device on your subnet.
>
> ok newer courseware such as that in 2276 DOES tell you (chapter 5 pg26/27)
> to start with the loopback but they are also looking at it from a position
> of you have a problem and want to find out were it dies.
>
> nope sorry, I will still say (even on an exam) that you start with the
> remote host. in real life and the question be damned...
>
> --
> Neil MCNGP #30
> the "curious" hair on the soap of society



Relevant Pages

  • Re: Configuring hostname, domainname, and IP address
    ... solved by tweaking the hosts file. ... Why the installation missed them, ... I'm sure that this one node network can be tweaked ... a ping will return that IP address. ...
    (comp.os.linux.networking)
  • Re: Configuring hostname, domainname, and IP address
    ... solved by tweaking the hosts file. ... Why the installation missed them, ... I'm sure that this one node network can be tweaked ... a ping will return that IP address. ...
    (linux.redhat.install)
  • Re: Configuring hostname, domainname, and IP address
    ... solved by tweaking the hosts file. ... Why the installation missed them, ... I'm sure that this one node network can be tweaked ... a ping will return that IP address. ...
    (comp.os.linux.setup)
  • Re: Configuring hostname, domainname, and IP address
    ... solved by tweaking the hosts file. ... Why the installation missed them, ... I'm sure that this one node network can be tweaked ... a ping will return that IP address. ...
    (alt.os.linux)
  • Re: TCP/IP Question
    ... > anything about being able to connect to a network device. ... > determine if TCP/IP is installed correctly. ... proper procedure is to ping the remote host - nay to access a remote ... why not ping the local address. ...
    (microsoft.public.cert.exam.mcse)

Loading