Bit of a long shot really, but does anyone have anything to do with Cisco packet tracer?

I have just started using it as part of a Cisco qualification and degree, but have got stuck pretty much straight away.

I think I just need to setup a v-lan between routers, but can I manage this? Of course not. Any help gratefully recieved!

Thanks, Joe.

I use packet tracer, as to what you are trying to achieve, are you following one of the template exercises or just a network from scratch?

+1 - If you need any help please do send me a PM.

Not used packet tracer, but explain what you're trying to do and I'll help if I can.

Cheers guys.

I have only just been introduced to the software, and need to have a basic topology that is the basis of all the other activities I will be given.

We have a diagram (which I only have on paper unfortunatly) and list of IP's etc for all the devices , but after setting it up I still can't get it to work. I think it's due to not knowing how to assign a vlan or IP to a switch.

The link below goes to the routing table of what I need to have and attached is what I have so far (all IP's are done, except for the switch).

http://cis.mhcc.edu/pm/CIS151/Chap%2003/Packet%20Tracer%20Activity%203.5.1.pdf

What I need to do is be able to send a ping from one of the PC's to the server, but I can't get any data to go beyond the routers, and have no idea why. It's propably really simple, but I can't figure it out, and google and the help files didn't get me anywhere.

Thanks,

Joe

Hi Joe, from the topo attached above I needed to update some of the configs: -

1. add clock rate to one of the routers serial interfaces

2. add static routes on both routers for the other networks

3. add the dns server name to the pc 1b

you should be able to carry out the simulation exercises now?

not sure what version of packet tracer you are using but I have the latest ver 5.2 so hope the config loads OK?

Topology-1.zip

Thats fantasic, thank you! I really appreciate you doing that, thank again.

It all works fine now. If you don't mind, can I just confirm a couple more things;

1) with the clock rate, is that basiclly just telling the port to communicate (at different speeds). It's something I fiddled with on another file, but still couldn't get working.

2) Static routes, again, something fiddled with, but got nothing. Are you telling it to route to the ethernet port on the next router? Also, on the "r2" router it routes to serial. How did you make it say that, and which router is it going to? As whenever we tried it says it can't route to itself, and typing in the ip of the other router doesn't work.

Thanks again, Joe

Edited 16 October, 200916 yr by TriggerFish

Thats fantasic, thank you! I really appreciate you doing that, thank again.

It all works fine now. If you don't mind, can I just confirm a couple more things;

1) with the clock rate, is that basiclly just telling the port to communicate (at different speeds). It's something I fiddled with on another file, but still couldn't get working.

2) Static routes, again, something fiddled with, but got nothing. Are you telling it to route to the ethernet port on the next router? Also, on the "r2" router it routes to serial. How did you make it say that, and which router is it going to? As whenever we tried it says it can't route to itself, and typing in the ip of the other router doesn't work.

Thanks again, Joe

1. you have in the lab, connected 2 routers with a serial link, one will be DCE (with the clock rate) the other is the DTE.

Normally these would be connected to a CSU/DSU which regulates the speed.

2. you are telling the router that any traffic going to the 192.168.254.0 network needs to go via the serial interface that is connected to the other router, you could also set the serial interface as the default gateway?

Router#conf t

Enter configuration commands, one per line. End with CNTL/Z.

Router(config)#ip ro 192.168.254.0 255.255.255.0 Serial0/0/0

Cheers. Rebuilt it again, and got it working via static routing.

Thanks again for your help, have had none of that explained to us yet!