Hi,
Couple of things which I want to confirm.
Are you able to ping the server on the ethernet segment in Paris after
getting into the Paris router?
What kind of host/server is on the ethernet segment? Is it a Unix host or NT
?
In any case, the host needs to have the network address of the Tempe network
configured inside. Otherwise the host will not know where to send the ICMP
packets which it recd.
You need to have static route inside the server as well.
Kindly clarify.
Cheers
Sriram
----- Original Message -----
From: "Georg Pauwen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 17, 2000 6:19 AM
Subject: Can't PIN server on Ethernet segment
> Hi there colleagues,
>
> I have the following problem:
>
> I have a router in Tempe and a router in Paris. From the router in Tempe I
> can ping the router in Paris, but I cannot ping a server on the Ethernet
> segment in Paris.
> The IP address of the router in Tempe is 10.230.13.18/30, the IP address
of
> the router in Paris is 10.230.13.17/30 ; the IP address of the server on
the
> Ethernet segment in Paris is 10.100.0.1.
> I can ping the server in Paris from the router in Paris, the IP address on
> the Ethernet interface on the router in Paris is 10.100.3.4/16
> I have also included the route table from the router in Tempe:
>
> Gateway of last resort is 10.230.13.17 to network 0.0.0.0
>
> 205.223.99.0/27 is subnetted, 1 subnets
> S 205.223.99.64 [1/0] via 10.230.13.17
> 10.0.0.0/8 is variably subnetted, 5 subnets, 3 masks
> S 10.0.0.0/8 [1/0] via 10.230.13.17
> C 10.88.0.0/16 is directly connected, Ethernet0
> S 10.83.0.0/16 [1/0] via 10.230.13.17
> C 10.230.13.52/30 is directly connected, Ethernet0
> C 10.230.13.16/30 is directly connected, Serial0.1
> S* 0.0.0.0/0 [1/0] via 10.230.13.17
>
> There are no routing protocols configured on both routers, only static
> routes (forget about the BGP route, that's just for our management
circuit);
> I have also completed the route table of the router in Paris:
>
> Gateway of last resort is 10.100.3.3 to network 0.0.0.0
>
> 205.223.99.0/27 is subnetted, 1 subnets
> B 205.223.99.64 [20/100] via 10.230.13.30, 2w4d
> 10.0.0.0/8 is variably subnetted, 19 subnets, 3 masks
> S 10.74.0.0/16 [1/0] via 10.230.13.14
> S 10.72.0.0/16 [1/0] via 10.230.13.26
> S 10.77.0.0/16 [1/0] via 10.230.13.2
> S 10.88.0.0/16 [1/0] via 10.230.13.18
> S 10.82.0.0/16 [1/0] via 10.230.13.22
> S 10.83.0.0/16 [1/0] via 10.230.13.22
> S 10.104.0.0/16 [1/0] via 10.230.13.10
> S 10.105.0.0/16 [1/0] via 10.230.13.6
> C 10.100.0.0/16 is directly connected, Ethernet0/0
> C 10.230.13.32/30 is directly connected, Ethernet0/0
> C 10.230.13.0/30 is directly connected, Serial1/0:1.1
> S 10.230.13.0/24 is directly connected, Null0
> C 10.230.13.4/30 is directly connected, Serial1/0:1.2
> C 10.230.13.8/30 is directly connected, Serial1/0:1.3
> C 10.230.13.12/30 is directly connected, Serial1/0:1.4
> C 10.230.13.16/30 is directly connected, Serial1/0:1.5
> C 10.230.13.20/30 is directly connected, Serial1/0:1.6
> C 10.230.13.24/30 is directly connected, Serial1/0:1.7
> C 10.230.13.28/30 is directly connected, Serial1/0:1.983
> S* 0.0.0.0/0 [1/0] via 10.100.3.3
>
> Does anybody have an idea of why I cannot ping the server in Paris from
the
> router in Tempe ? There is an access list active on the Ethernet interface
> in Paris, but it only denies ICMP redirects, so it shouldn't have any
> influence on the ICMP echoes.
> Thanks for your help in avance !
>
> Regards,
>
> Georg Pauwen
>
> ________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
>
> ___________________________________
> UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
> FAQ, list archives, and subscription info: http://www.groupstudy.com
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
