|
Home > Archive > alt.certification.cisco > July 2002 > a little help
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| DEAN MCDANIEL 2002-07-17, 3:25 pm |
| I have hit a roadblock on setting up a netowork.
I have a 2514 with E0 assigned the address provided by ISP, mapped a
static route to the default gateway, and also added the ISP's ip name
server. The router can ping, telnet and tracroute perfectly.
On the E1 interface, the internal network can ping the E0 address but
not ping the gateway or name server.
The networks are added in the conf file under RIP, and the IP host
line in teh config file has the correct interfaces.
Windows desktops on the internal network cannot ping the gateway and
of course cannot get to the internet.
Any ideas would be appreciated.
| |
| George.Georgiou1 2002-07-17, 4:25 pm |
| Hi Dean,
I know exactly how ya feel!!
I've spent, well...alot of money doing the CCNA course at college, and am
about to take the BIG exam in a couple of weeks.
Now, you would think that the content of this course would be pretty much
spot on, right?.....No chance. Being new to the networking industry, I find
that as I read the stuff, quite often it contradicts itself...and that's
Cisco!!
Half the time I sit there staring at the words thinking I've read it wrong.
Whadya supposed to do....I certainly don't know!
Happy studies.
G!
"DEAN MCDANIEL" <deano@ont.com> wrote in message
news:83sbju4b0tlv0qk7f45pu60is
ieh3iiclh@4ax.com...
> I have hit a roadblock on setting up a netowork.
>
> I have a 2514 with E0 assigned the address provided by ISP, mapped a
> static route to the default gateway, and also added the ISP's ip name
> server. The router can ping, telnet and tracroute perfectly.
>
> On the E1 interface, the internal network can ping the E0 address but
> not ping the gateway or name server.
>
> The networks are added in the conf file under RIP, and the IP host
> line in teh config file has the correct interfaces.
>
> Windows desktops on the internal network cannot ping the gateway and
> of course cannot get to the internet.
>
> Any ideas would be appreciated.
| |
|
| On Wed, 17 Jul 2002 15:36:01 -0700, DEAN MCDANIEL <deano@ont.com>
wrote:
>I have hit a roadblock on setting up a netowork.
>
>I have a 2514 with E0 assigned the address provided by ISP, mapped a
>static route to the default gateway, and also added the ISP's ip name
>server. The router can ping, telnet and tracroute perfectly.
>
>On the E1 interface, the internal network can ping the E0 address but
>not ping the gateway or name server.
>
>The networks are added in the conf file under RIP, and the IP host
>line in teh config file has the correct interfaces.
>
>Windows desktops on the internal network cannot ping the gateway and
>of course cannot get to the internet.
>
>Any ideas would be appreciated.
Show us your config
| |
| David Beecken 2002-07-17, 4:25 pm |
| Hi, I might be able to help. I did something similar through a cable modem.
What is the ethernet 0 going into? I know you said the ISP, but what device on
your end? Anyhow, if you want you can message me via AIM and I can try to help
a little more. I had a few problems but was able to eventually get it.
www.Ciscotrack.com
Fourm, papers, study guides, etc
No Ads
| |
| Jennyfer 2002-07-17, 9:25 pm |
|
"DEAN MCDANIEL" <deano@ont.com> wrote in message
news:83sbju4b0tlv0qk7f45pu60is
ieh3iiclh@4ax.com...
> I have hit a roadblock on setting up a netowork.
>
> I have a 2514 with E0 assigned the address provided by ISP, mapped a
> static route to the default gateway, and also added the ISP's ip name
> server. The router can ping, telnet and tracroute perfectly.
>
> On the E1 interface, the internal network can ping the E0 address but
> not ping the gateway or name server.
>
> The networks are added in the conf file under RIP, and the IP host
> line in teh config file has the correct interfaces.
>
> Windows desktops on the internal network cannot ping the gateway and
> of course cannot get to the internet.
>
> Any ideas would be appreciated.
Do you have a default route?
If the client machines can't ping their side of the router, then you need to
fix that first... The clients and E1 should be on the same subnet... If not,
you may want to fix that first...
Wait.
You are routing between E1 and E0... how are you getting to the ISP? You
probably do not have an ethernet connection to the internet, it is probably
ISDN, Frame, ATM, X.25, etc... Which means you should have either a BRI or a
Serial interface to them...
My guess is that you mapped a yucky IP to your internal interface and didn't
configure your interface to the internet...
Jenns
| |
|
| 2514(config)#ip route 0.0.0.0 0.0.0.0 e0
e0 being the cable modem or ADSL modem
more information on the type of service as the last comment stated
Jennyfer wrote:
> "DEAN MCDANIEL" <deano@ont.com> wrote in message
> news:83sbju4b0tlv0qk7f45pu60is
ieh3iiclh@4ax.com...
>
>>I have hit a roadblock on setting up a netowork.
>>
>>I have a 2514 with E0 assigned the address provided by ISP, mapped a
>>static route to the default gateway, and also added the ISP's ip name
>>server. The router can ping, telnet and tracroute perfectly.
>>
>>On the E1 interface, the internal network can ping the E0 address but
>>not ping the gateway or name server.
>>
>>The networks are added in the conf file under RIP, and the IP host
>>line in teh config file has the correct interfaces.
>>
>>Windows desktops on the internal network cannot ping the gateway and
>>of course cannot get to the internet.
>>
>>Any ideas would be appreciated.
>
>
> Do you have a default route?
> If the client machines can't ping their side of the router, then you need to
> fix that first... The clients and E1 should be on the same subnet... If not,
> you may want to fix that first...
> Wait.
> You are routing between E1 and E0... how are you getting to the ISP? You
> probably do not have an ethernet connection to the internet, it is probably
> ISDN, Frame, ATM, X.25, etc... Which means you should have either a BRI or a
> Serial interface to them...
>
> My guess is that you mapped a yucky IP to your internal interface and didn't
> configure your interface to the internet...
>
>
>
> Jenns
>
>
>
>
>
>
>
>
|
|
|
|
|