Re: TCP/IP Question

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Neil (neilmcse_at_nospamforyou.com)
Date: 09/17/04


Date: Thu, 16 Sep 2004 19:59:06 -0700

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: TCP/IP Question
    ... What is the gateway and interface if you ping the local address as ... there is nothing in the question about network connectivity. ... Only that the protocol installation succeeded. ... > proper procedure is to ping the remote host - nay to access a remote ...
    (microsoft.public.cert.exam.mcse)
  • Re: unable to ping by name
    ... But i am able ping by ip addresss ... Open the Network Connections folder. ... Double click Internet Protocol (TCP/IP). ... TCP/IP and NBT Configuration Parameters for Windows XP ...
    (microsoft.public.windowsxp.network_web)
  • Re: Ping IP OK, Ping Name Not OK, Internet OK, Internetwork not
    ... >>conected via the network to the switch. ... >>*It can IP ping all other computers OK ... >>computer, either manually in the properties of TCP/IP, or by automatic ... If DNS server addresses are listed when you type the ipconfig ...
    (microsoft.public.windowsxp.network_web)
  • Re: TCP/IP Question
    ... >> anything about being able to connect to a network device. ... >proper procedure is to ping the remote host - nay to access a remote ... this idea of installing network protocols implies a network card - ... >why not ping the local address. ...
    (microsoft.public.cert.exam.mcse)
  • Re: is this a operating system problem?
    ... If not then TCP/IP is broke. ... Can you ping any other IP address on your network? ... > rebooting the alpha, it is unable to connect to the LAN. ...
    (microsoft.public.win2000.file_system)