CompTIA A+ 220-701: 3.2 – Command Line Utilities

| February 23, 2010 | 13 Comments


There is a wealth of Windows utilities that can be run directly from the command line or launched from the Start menu. In this video, we’ll examine utilities like telnet, ping, msconfig, dxdiag, and many more.


<< Previous Video: The Windows User InterfaceNext: Directories and Files >>

Tags: , , , , , , , , , ,

Category: CompTIA A+ 220-701

  • Jeff

    If you create a restore point before you screw up the registry with regedit, can you use System Restore to restore the registry? Or does System Restore have nothing to do with the registry?

  • john frogue

    when are you going to talk about windows 7 OS? Is ther much difference from Vista or the ne Win7?

    • JDG

      Win7 is not in the Comptia 220-701 objectives… So he won’t be talking about it.

  • April

    I’m on Vista the telnet setting was off. You have to turn it on for telnet to work. So if your on Vista and your having trouble with telnet that is the reason. Not hard to turn it on. Go to Control Panel, Programs, Turn Windows features on/off then just scroll down tell you find tell net and just check the box to turn it on. A permission box will pop up and you have to click continue. It will take a few min for the computer to configure it.

  • Sergey

    Video 1 at 5:58. Professor, please correct your statement about TTL field in the PING command output. It is not accurate.

    • The comments about TTL in this video are accurate, although I don’t go into details about TTL or how it works (I describe TTL in the networking section and in the Network+ videos). nnWhat part of the TTL description do you find inaccurate?

      • Sergey

        nnYou stating in the above video: “and the time tonlive was 64 hops, so this is really close to me”. It is just does not makensense. You running PING from 192.168.0.10 host which is in the same subnet thatnis your router (192.168.0.1). In fact you just 1 hop away from your own routern(not 64 hops). What TTL field really is that what value responding device setsnin IP header’s TTL field when it sends packets out.nnn

        • I’m actually zero hops away from the local device that I initially pinged, which is why the TTL remained at 64; this device was so close that I didn’t need to traverse a router in order to receive a ping response from it.nnTTL is a countdown timer; it starts at a particular number and decreases by one each time it goes through a router. When the time to live reaches zero, a router discards the packet.

          • jdannett

            Curious: what would happen if it required more than 64 hops?

          • Once the packet went through the 64th hop and the TTL reached zero, the router would drop the packet and notify the source device via ICMP that the time to live was exceeded.

          • jdannett

            But what if there are actually 64+ routers between the local PC and the PC being pinged? Thanks.

          • If the TTL gets to 0, the packet is dropped. Fortunately, you’ll rarely get beyond 20 hops when communicating to devices across the Internet.

X