Need advice on why cannot connect second Eth/Fa to the router

in CCNA & CCENT
Hi All,
can someone please shed some light why I'm not able to connect second Fasteth/eth to any of the 2620/2621 or 2811 routers. Here is what I get:
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 192.168.4.1 YES manual up up
FastEthernet0/1 192.168.3.3 YES manual up down
I have also attached a screenshoot of my lab in packet tracer.
Any comments appreciated.
Thank you
can someone please shed some light why I'm not able to connect second Fasteth/eth to any of the 2620/2621 or 2811 routers. Here is what I get:
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 192.168.4.1 YES manual up up
FastEthernet0/1 192.168.3.3 YES manual up down
I have also attached a screenshoot of my lab in packet tracer.
Any comments appreciated.
Thank you
Long term plan:
2011: CCNA (70%), CCNA: Security, MCITP:Messaging
2012: VCP, CEH, Linux+, start RHCA/E
2013: finish RHCA/E, CCNP
2011: CCNA (70%), CCNA: Security, MCITP:Messaging
2012: VCP, CEH, Linux+, start RHCA/E
2013: finish RHCA/E, CCNP
Comments
-
jwashington1981 Member Posts: 137
Hi All,
can someone please shed some light why I'm not able to connect second Fasteth/eth to any of the 2620/2621 or 2811 routers. Here is what I get:
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 192.168.4.1 YES manual up up
FastEthernet0/1 192.168.3.3 YES manual up down
I have also attached a screenshoot of my lab in packet tracer.
Any comments appreciated.
Thank you
Is that the full diagram? The part where I see the red it shows Eth 1/0 instead of FaE 1/0. Also, which device does that Eth 1/0 belong to? The switch or the router? You have the text right between the two devices so I can't tell.
Also, the IP addresses you listed in this problem, where are the supposed to be on the diagram because I don't see them. -
mikesz Member Posts: 115
jwashington1981 wrote: »Is that the full diagram?
Yes it is.jwashington1981 wrote: »Also, which device does that Eth 1/0 belong to? The switch or the router?
Fa0/1 belongs to router.jwashington1981 wrote: »Also, the IP addresses you listed in this problem, where are the supposed to be on the diagram because I don't see them.
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 192.168.4.1 YES manual up up - connects SW1
FastEthernet0/1 192.168.3.3 YES manual up down - connects switch 2950-24 (the disconnected one).
ThanksLong term plan:
2011: CCNA (70%), CCNA: Security, MCITP:Messaging
2012: VCP, CEH, Linux+, start RHCA/E
2013: finish RHCA/E, CCNP -
jwashington1981 Member Posts: 137
Yes it is.
Fa0/1 belongs to router.
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 192.168.4.1 YES manual up up - connects SW1
FastEthernet0/1 192.168.3.3 YES manual up down - connects switch 2950-24 (the disconnected one).
Thanks
Ok, looking at what you just put in your post and what you have in your diagram, I see you have 192.168.3.1 listed on your diagram for that Fa0/1 interface but you say here in your post that the IP address is 192.168.3.3? Which is it? Also, what subnet mask are you using for that link?
Also wondering, you have FastEthernet0/1 is up, line protocol is down. Did you perform a no shutdown on the router interface and also on the switch's vlan 1 interface since you applied an IP address to the switch? -
mikesz Member Posts: 115
I have figured it out!
I knew it was going to be something stupid. Here is what I thought:
Dissimilar devices: (example:computer and router) straight-through cable
similar devices: (example: router to router or switch to switch) crossover cable.
It looks that I was wrong and you have to use crossover cable when connecting to ethernet port on the router.
Can someone actually confirm this, please?
Thank youLong term plan:
2011: CCNA (70%), CCNA: Security, MCITP:Messaging
2012: VCP, CEH, Linux+, start RHCA/E
2013: finish RHCA/E, CCNP -
millworx Member Posts: 290
Dissimilar devices: (example:computer and router) straight-through cable
similar devices: (example: router to router or switch to switch) crossover cable.
This is correct, however you would not need to use a crossover cable to go from the sw to the router interface. Straight through is fine.Currently Reading:
CCIE: Network Security Principals and Practices
CCIE: Routing and Switching Exam Certification Guide -
mikesz Member Posts: 115
Can anyone explain why I would need to use crossover to connect PC to router?
Is this by default?
Apologies if this is a stupid question, I always thought that you can use straight-through to do this.
MLong term plan:
2011: CCNA (70%), CCNA: Security, MCITP:Messaging
2012: VCP, CEH, Linux+, start RHCA/E
2013: finish RHCA/E, CCNP -
MosGuy Member Posts: 195
Can anyone explain why I would need to use crossover to connect PC to router?
Is this by default?
Apologies if this is a stupid question, I always thought that you can use straight-through to do this.
M
A router ethernet port is effectively a NIC. So connecting a PC directly they would receive and transmit using the same wire pairs and collide. Therefore a cross-over should be used. For exam purposes a cross over is the default yes. In the real world, especially with consumer level routers. The ports will auto-sense the cable type. So you can plug in a straight through and it will automatically "cross" the wires. A cross over is technically the proper cable to use. With auto-sensing ports these days, many don't bother---
XPS 15: i7-6700HQ, 256 pcie ssd, 32 GB RAM, 2 GB Nvidia GTX 960m, windows 10 Pro
Cert in progress: CCNA (2016 revision) -
MickQ Member Posts: 628 ■■■■□□□□□□
Can anyone explain why I would need to use crossover to connect PC to router?
Is this by default?
Apologies if this is a stupid question, I always thought that you can use straight-through to do this.
M
DTE - DTE, or DCE - DCE = crossover.
DTE - DCE, or DCE - DTE = straight through.
Another way to remember:
PCs & routers have IPs, switches and hubs don't.
PCs - routers = crossover, switches - hubs = crossover.
PC/router - switch/hub = straight through. -
mikesz Member Posts: 115
Thank you very much for clarifying it.
MLong term plan:
2011: CCNA (70%), CCNA: Security, MCITP:Messaging
2012: VCP, CEH, Linux+, start RHCA/E
2013: finish RHCA/E, CCNP