• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 655
  • Last Modified:

Cisco WIC-1ENET Problem

Hello All,

I currently have two cisco 1760 routers that I would like to set up in a lab environment.  All I have is two Cisco WIC-1ENET cards.  I tried to configure them butno matter what I did, it didn't seem to work.  I put routes in, added a default gateway, ect.  I could ping both interfaces from each router but when I did a SHOW IP ROUTES the routes weren't there.  When I did a WRITE TERMINAL, it showed that the routes were added but it still didn't work.  Thanks everyone for your help.
  • 2
2 Solutions
Could you post the configuration?  It's most probably a small typo somewhere...
Music_Man608Author Commented:
Not right at the moment, I erased the configuration to do a different one.  I'll have to do it again and post it which will take a while, thanks.
OK, I'll try to list possible issues that could be faulty.  But I first need to make sure that I understand your problem:  It seems that you configure static routes, but these routes does not show in your routing table.  This will usually be caused by incorrect next-hop addresses.  If the next-hop address is not in the routing table, the static route will not be added to the routing table.  Also note that, with Ethernet interfaces, you cannot use the interface (Ethernet0) as a next hop; you must use an IP address.

I assume that from one router you could ping the Ethernet IP address of Router B from Router A, and that the interface is "up/up"?  This IP address (of Router B's interface, that you can ping) should be the next-hop address in the static route on Router A.

If I do not get your question, please post any clarifying comments...
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now