|
|
|
| Here is the question, please help,
You want to connect to a remote server but you get a response saying destination unreachable, to determine the problem you do
some pings.
127.0.0.1 - Unsuccessful
10.2.2.0 Default Gatewayeway - unsuccesful
66.8.8.1 Remote server - unsuccesful
Answers:
a. TCP/IP is not properly installed
b. NIC is not fuctioning properly
c. Problem with remote server
d. Something else | |
|
| quote:
I`m writing before the end of the month.
eeer sorry. if you can not answer this question based on your study, you need to reschedule this exam...
this should be answered in any book. if they did not answer it directly, they would mention what a loopback addy is. this should also be apparent to anyone who should've work on some type of network prior to ccna pursuit.
combine this with your previous posts, my suggestion for you is... grab a book, spend time reading it. skip the question/answer study. | |
| pomerol82 2002-07-09, 8:55 pm |
| For studying purpose but not only for exam.,
not directly give you answer but hint that let you find out the answer on your own:
If you can't make a phone call with your phone set. What will you do?
1) Check whether you phone set works;
2) Check jack & socket;
3) Check your friend's no.
Equ. to computer:-
For 1) NIC, ping localhost
For 2) Gateway, ping gateway (router)
For 3) Remote node, ping its address.
Solve the source problem at first. | |
|
| add dial tone to match gateway and push the two (phone, jack/line) up and it would be more accurate comparision what a loopback address test. | |
| pomerol82 2002-07-09, 9:18 pm |
| Oh! much details. | |
| 100114 2002-07-10, 4:41 am |
| To Cut it short...
You can use the TCP/IP ping 127.0.0.1 command to ensure that TCP/IP is functioning on your machine . If it is not it gives you a unsuccessful Message. | |
| 100114 2002-07-10, 4:45 am |
| to add to it..
If this fails, check that all network card parameters have been correctly configured, and that the card is correct connected to the LAN. | |
| makan007 2002-07-11, 6:59 am |
| B,C & D are correct answers. | |
| makan007 2002-07-11, 7:01 am |
| quote:
Originally posted by 100114
To Cut it short...
You can use the TCP/IP ping 127.0.0.1 command to ensure that TCP/IP is functioning on your machine . If it is not it gives you a unsuccessful Message.
Perfect! You can type ping localhost too. | |
| Taqwus 2002-07-11, 7:19 am |
| I would have to go with B.
I have never seen an installation of TCP go bad. Unless it was not installed and you tried to use the ping command
You can also "ping loopback" to test it | |
| makan007 2002-07-11, 7:23 am |
| Ya. B will be the best answer. When NIC is down. No matter where you ping, you will receive unsuccessfull message. | |
| nyriavo 2002-07-11, 1:18 pm |
| Make sure you don't have any firewall installed in your local machine.
Since you are not able to ping the local machine with 127.0.0.1, don't expect to ping successfuly other devices. The echo requests might pass through the firewall but not the echo replies. | |
| Imation2k 2002-07-12, 12:51 pm |
| quote:
Originally posted by 100114
To Cut it short...
You can use the TCP/IP ping 127.0.0.1 command to ensure that TCP/IP is functioning on your machine . If it is not it gives you a unsuccessful Message.
Wouldn't it be a problem with the NIC though? I'm a little skeptical on TCP being improperly installed, but a nonfunctioning NIC is not unheard of for me. |
|
|
|