Tally wrote:
>I have a issue going on with NT box, which is
>acting
>as a router. It is a Ethernet based LAN.
>
>This is the configuration.
>
> Cisco Router
> |
> |
> Interface 1
> |
> |
> NT BOX
> |
> |
> Interface2
> |
> |
> PC A
>
>>From cisco router I can successfully ping Interface
>1.
>PC A can successfully ping Interface 2. Problem is
>that
>from cisco router i cannot ping Interface 2.
>However
>from PC A i can successfully ping Interface 1 and
>2.
>Ofcourse IP forwarding has been enabled on the NT
>Box.
As Interface 1 is in the same subnet as one of the router's interfaces - no
problem. But what does the Cisco when you try to ping Interface 2?
It checks in its routing table for a route to the subnet containing that
interface.
Does such a route exist? (Check by 'show ip route' on the Cisco).
If not the router takes its default route probably directing the other way
(to the Internet at the other side of the router, I suppose).
So just add a route to the subnet with Interface 2 to the routers routing
table.
May I ask a further question? Why, in your configuration, does the NT box
have routing functionality? If the NT box contains only the Interfaces 1 and
2 its routing is useless. Connect the subnet of PC A directly to the Cisco.
If you are using RRAS to reduce the load arriving at the Cisco, consider
that the packet filtering of RRAS is not very professional (no ACK-bit, no
ranges of ports etc.).
And by the way: talking about routing with Win NT, read KB articles Q
217336 and Q 238453. And never think that an NT box is routing only because
you can see both interfaces from one side. That's some kind of (in my
opinion:) erroneous behaviour of Windows NT even if forwarding is disabled.
Regards,
Enno
[EMAIL PROTECTED]
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
