Hi,
For basic connectivity, you don't need the static routes you've entered.
Nor do you need access-lists as they are used to restrict/filter traffic.
The router will know about them as they are directly connected. Just be sure
that your servers default gateway is192.168.110.6. Your client must use
default gateway of 172.24.245.1. If these are already configured, to
troubleshoot from the client, you want to ping loopback (127.0.0.1), client
172.24.100.1, local router interface 172.24.245.1, remote router interface
192.168.110.6, then server 192.168.110.5. Do the reverse from the server.
This way, you can isolate where the routing is breaking down. If loopback
fails, then you've got driver problems. If attached interface fails, then
you've got hardware/cabling problems, etc...
"show ip route" will display the routing table so you can verify. "debug ip
packet" will tell you what the router is doing with the ip packets it
receives.
Hope this helps.
----- Original Message -----
From: "GuidoB." <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 09, 2000 1:56 PM
Subject: Access list Cisco 2514
> Hi there,
>
> I'm new to the firewall & routing bussiness. Yesterday & today i spent a
> lot of time trying to figure out routing on a Cisco 2514. I have some
> books on my side (Cisco CCNA books) but can't figure out what i should
> do to get the thing routing.
> The situation is this:
> Eth0 -> 192.168.110.6 255.255.255.252 with a server 192.168.110.5
> 255.255.255.252 Ip broadcast 192.168.110.7 No ip direct broadcast
> Eth1 -> 172.24.245.1 255.255.0.0 with a client 172.24.100.1 255.255.0.0
> No ip direct broadcast
> Lo0 -> 192.168.0.1 255.255.255.0
> Rest of the Interfaces are shutdown
>
> Router RIP
> Network 172.24.0.0
> Network 192.168.0.0
>
> Ip route 172.24.100.0 255.255.255.0 Eth1
> Ip route 192.168.110.4 255.255.255.252 Eth0
>
> Can somebody give some hints how to get the client & server talking. I'm
> gonna take a course in this but there's no time now.
>
> Greetz,
>
> GuidoB.
> -
> [To unsubscribe, send mail to [EMAIL PROTECTED] with
> "unsubscribe firewalls" in the body of the message.]
>
>
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
