Re: TCP/IP Question
From: The Poster Formerly Known as Kline Sphere (.)
Date: 09/17/04
- Next message: The Poster Formerly Known as Kline Sphere: "Re: TCP/IP Question"
- Previous message: Neil: "Re: Job interview, Good news, Bad news"
- In reply to: Neil: "Re: TCP/IP Question"
- Next in thread: Neil: "Re: TCP/IP Question"
- Reply: Neil: "Re: TCP/IP Question"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 17 Sep 2004 17:58:53 +0100
Honest Neil, this not me posting in disguise....
On Thu, 16 Sep 2004 19:59:06 -0700, Neil <neilmcse@nospamforyou.com>
wrote:
>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...
Kline Sphere (Chalk) MCNGP #3
- Next message: The Poster Formerly Known as Kline Sphere: "Re: TCP/IP Question"
- Previous message: Neil: "Re: Job interview, Good news, Bad news"
- In reply to: Neil: "Re: TCP/IP Question"
- Next in thread: Neil: "Re: TCP/IP Question"
- Reply: Neil: "Re: TCP/IP Question"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
