Urgent (question lab 2)!!!

[gopal]

Hi,

I was not able to resolve the name even I created all the host names in all the routers. Any body has any idea why this is not working?

For ex. I tried pinging from a PC as ping R1. But it cannot ping.

One router has the table as follolws:

Host Port Flags Age Type Address(es)
R1 None (perm, OK) 0 IP 192.168.10.17
192.168.10.14
192.168.10.25
R2 None (perm, OK) 0 IP 192.168.10.1
192.168.10.13
192.168.10.9
Core(config)#

[Ltat42a]

Are you able to post your config for the Corp router?

[gopal]

Originally Posted by Ltat42a

Are you able to post your config for the Corp router?

corp_rout_Lab_2.txt

Hi,
Here is the attachment for my corp-config.

[Ltat42a]

Mine is pretty close to yours, check out mine. With all the configurations, my answers work according to the objectives in the PDF Guide.

[gopal]

Originally Posted by Ltat42a

Mine is pretty close to yours, check out mine. With all the configurations, my answers work according to the objectives in the PDF Guide.

Did you try adding multiple ip addresses for the same host? Do they work also? Here I can see you added only one interface add per router.

[Ltat42a]

I've never seen the ip host command configured with multiple addresses, just the one.

[gopal]

Originally Posted by Ltat42a

I've never seen the ip host command configured with multiple addresses, just the one.

Even with single address added for every router, cannot resolve the hostname. Can ping the ip but not with the name. Still could not figure out what is wrong.But this is from PC client only.

Now I am able to ping router to router, using the host entries.

[Ltat42a]

Here's what I got -
Core#p1r1

Trying 192.168.10.2 ...Open You are at the P1R1 Router


User Access Verification

Password:
% Password: timeout expired!

[Connection to 192.168.10.2 closed by foreign host]
Core#
Core#
Core#p1r2

Trying 192.168.10.6 ...Open You are at the P1R2 Router


User Access Verification

Password:
% Password: timeout expired!

[Connection to 192.168.10.6 closed by foreign host]
Core#

Here's the config I have for all three routers, the PC, & the laptop.

[lammle]

it is asking for your telnet password on the p1r1 router. I dont' see the problem.
TL

[gopal]

Originally Posted by lammle

it is asking for your telnet password on the p1r1 router. I dont' see the problem.
TL

I also can ping or telnet from one router to another by name ( name resolution using the host entries).

But, I could not get the name resolution while trying from host PC.

Should I add also the PC ip in the host table in every router??

[wilder7bc]

I used the commands from your config file and they worked fine on my router going from router 1 to router 2:

--------------------------------------------------------------------------
r1-PxR3(config)#ip host r2 192.168.235.1 ?
A.B.C.D Host IP address
<cr>

r1-PxR3(config)#ip host r2 192.168.235.1
r1-PxR3(config)#end
r1-PxR3#
*Jul 6 05:34:40.523: %SYS-5-CONFIG_I: Configured from console by console
r1-PxR3#r2
Trying r2 (192.168.235.1)... Open
This is my R2 router

User Access Verification

Password:
---------------------------------------------------------------------------

As Mr Lammle said asking for the Password is normal. Make sure you setup your VTY telnet on R1, and R2 and have it enabled for login.

Your not really following the lab with your config file your venturing out on your own trying different things. This is great, and you learn alot doing this but you also dont have the safety net of the labs as your kind of doing your own thing.


Next you speak also about pinging from a computer to a router? is that correct? to trouble shoot this we would need more information the exact steps you perform from what device to what device with the details.

For example if your pinging from a router to your PC and the pings die it could be a number of things:

1. Your PC is not on the same network as your router
2. Your PC has firewall turned on
3. Your PC has virus or third party software that is stopping it
4. something may be wrong on the path.

You can follow Cisco Trouble shooting steps which I think Mr Lammle also points out.

Choose one device lets say computer.

ping 127.0.0.1 (checks tcp/ip stack)
ping nic card
ping default gateway
ping remote server your trying to reach


You can run traceroute as well. When doing this start with the IP address if that works but the name does not work then you know you have DNS problem.

I also check the physical layer 1 stuff very quickly if I cannot get out as well. so make sure if you cannot ping a DG or something you check cables, and also make sure you have the right type of cables. Remember if your connected to a router directly you need a cross over connection as routers and NIC cards have same interface type as far as cable connection.

As I type all this stuff you start to see how broad it is and how really detailed information is called for because it could be many different issues and problems based on configuration, equiptment, and how they are setup.

When you have a problem start from the beginning remove every layer and start adding things back one at a time as you add them back you eliminate what works. You will eventually find your problem and then be able to ask better and more specific questions.

I hope this helps stimulate you into some logical and creative trouble shooting ideas.

Respectfully,

Brian

[wilder7bc]

Originally Posted by Ltat42a

A spark of encouragement can ignite great endeavors

Hi Ltat42a


I love your little signature and I could not agree more =)

[Ltat42a]

Thanx Wilder....I got that from Our Daily Bread years ago, thought it was pretty cool.

Hey gopal...I don't know that you could use host names on a PC to telnet into a router or switch. You wouldn't be able to do it in Packet Tracer, but maybe you could edit your host or lmhost table on your PC in a real lab. We used to edit those at work to get to different services.

Also, in this lab, the ACL on p1r1 prevents the PC from telnetting into the Core router, but you can telnet from any of the laptops.

P1R1
access-list 110 deny tcp host 192.168.10.14 host 192.168.10.1 eq 23

does this help?