sounds like from b > a you dont have an nat xlate established. when you go from a > b it creates the xlate so that b > a starts working.
We had a problem after upgrading from 6.1.1 to 6.3 where one of our vpn partners couldn't get in til we pinged a host on their side. Error in the syslog was a deny due to no xlate. We were also losing NAT to arbitrary addresses on port 80. We rolled back to 6.1.4 (the latest GD and all is well). What version are you on? -----Original Message----- From: Vajira Wijesinghe [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 15, 2003 3:23 PM To: [EMAIL PROTECTED] Subject: do you know why? [7:72352] I have a pix firewall and i have a strange problem. If any one of you have come across this pls let me know the solution. I have few servers at both sides of the PIX. eg. Server-A at Outside zone and Server-B at Inside zone. 1. When I ping from Server-B to Server-A, I get request timeout. 2. Now I go to Server-A and start a ping to Server-B. It works fine. 3. Then again I go back to Server-B to ping to Server-A, and now it starts pinging!!! Can anyone of you explain this??? I need to get this thing resloved and straight away ping from B to A. Thanks. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=72357&t=72352 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
