Typo......

On Tue, Sep 8, 2009 at 4:52 PM, Kingsley Charles <[email protected]
> wrote:

> Hi Stu
>
> I am running firewall (ASA) in routed mode.
>
> I have disabled (ip routing) on the 1841 not on the firewall.
>
> There are two 1841s. One 1841 is host from where I initiate the traffic to
> outside world and the other 1841 is the switch (disabled routing by no ip
> routing command). The 1841 inter-connects the other 1841 and ASA.
>
>
> With regards
> Kings
>
>   On Tue, Sep 8, 2009 at 4:29 PM, Stuart Hare 
> <[email protected]>wrote:
>
>> Kings,
>>
>> What firewall mode are you running in?
>>
>> When you say you have disabled ip routing on the firewall what exactly
>> have you done?
>>
>> As per your topology, do you have 2 1841 rtrs or just one?
>>
>> If you have 1 rtr, for your L2 1841 are you using it as a bridge, or do
>> you have 1 interface layer 3 and the other layer 2?
>>
>> Stu
>>
>> 2009/9/8 Kingsley Charles <[email protected]>
>>
>>>   Hi
>>>
>>> I have a host routerA connected to a switch port of 1841 (access vlan 6)
>>> and other port (access vlan 6) is connected to the ASA (inside g0/1). The
>>> ASA is connected to the outside world
>>> through g0/0 (outside).
>>>
>>> I have configured PAT on the ASA.
>>>
>>> I have disabled "ip routing" on the ASA, such that it has switching
>>> functionality alone.
>>>
>>> Now I am trying to make telnet connection from the  host routerA to a
>>> host in the outside world but I get the following error message on the
>>> router.
>>>
>>> % Connection refused by remote host
>>>
>>>
>>> I am able to ping the inside interface of the ASA from the host routerA.
>>>
>>>
>>> The PAT is not happening and the ASA is refusing the connection.
>>>
>>> If I remove the switch (1841) and connect the host routerA (from L3
>>> interface) directly to ASA inside interface, the PAT is happening and I am
>>> to telnet.
>>>
>>>
>>> I am observing that when I use L2 ports, the connectivity doesn't go
>>> through the ASA.
>>>
>>> I even tried converting the ASA inside interfaace to a trunk and making
>>> the switch port into a trunk but still I see the same problem.
>>>
>>> For both cases using inside interface in access mode and trunk mode, ASA
>>> refuses the connection.
>>>
>>> What could be the problem?
>>>
>>>
>>>
>>>
>>> With regards
>>> Kings
>>>
>>> _______________________________________________
>>> For more information regarding industry leading CCIE Lab training, please
>>> visit www.ipexpert.com
>>>
>>>
>>
>
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Reply via email to