Can the server initiate a tcp connection to you? Have you checked the NAT mapping to ensure you are allowed to initiate connections to that server? It sounds like when the server pings you, it opens a "hole" through NAT allowing you to then initiate a connection to it through that "hole". This doesn't sound like it is in keeping with the proper function of stateful NAT, which should just allow ICMP back throught the translation it created, unless the NAT implementation isn't using stateful inspection. If you can contact all the servers except that one, I would look for the difference between the configuration for the other servers and that one.
-----Original Message----- From: Drew [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 01, 2002 5:13 PM To: [EMAIL PROTECTED] Subject: Very odd problem [7:50459] Hello all, I have a problem that I can barely describe, let alone quantify. I seek the assistance of the masters, and suspect this might be an interesting thing for those of us in the student role. Here goes: I have an internal network seperated from a partner network via a 6500 switch/router which is also running NAT. There is also a Raptor firewall between my network and the border switch. There are some servers in the partner network that are accessed from my network. The 6500 has static NAT entries for those servers. The firwall rulebase is set to allow the connections. The problem is, I can not connect to a specific server in the partner network.. that is, until that server pings my workstation. After that, I can connect to them. What could be the cause of this? Could it be a NAT issue? Where might I start troubleshooting? -Ds Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=50473&t=50459 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
