Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
603
Views
0
Helpful
1
Replies

Dropped Connection from single server??

David Shearing
Level 1
Level 1

‎12-04-2012 04:57 AM - edited ‎03-11-2019 05:32 PM

Hi All,

I was hoping someone could help with a frustrating problem i am having. 

I have a remote VMware host that i want to manage from our head office.  I can connect to it happily from any machine in the office it seems, except the vCentre server (on server 2008 R2)  where it needs to be managed.  The server 172.19.2.5 seems to drop its connection as far as i tell and you then start seeing these ICMP packets between the ASAs outside interface and router.  Does anyone have any ideas i could try?  This is quite a frustrating problem.  It has to be the sever killing the connection but i have no idea why.

Thanks for the help.

  • 6|Dec 04 2012|12:37:31|302014|172.19.2.5|57133|172.20.1.10|443|Teardown TCP connection 232 for Outside:172.19.2.5/57133 to inside:172.20.1.10/443 duration 0:01:40 bytes 2308 TCP FINs
  • 6|Dec 04 2012|12:36:44|302014|172.19.2.5|57135|172.20.1.10|443|Teardown TCP connection 234 for Outside:172.19.2.5/57135 to inside:172.20.1.10/443 duration 0:00:48 bytes 18499 TCP Reset-O
  • 6|Dec 04 2012|12:36:26|302021|192.168.0.1|0|192.168.0.250|0|Teardown ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:36:26|302020|192.168.0.1|0|192.168.0.250|0|Built inbound ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:36:24|302021|192.168.0.1|0|192.168.0.250|0|Teardown ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:36:24|302020|192.168.0.1|0|192.168.0.250|0|Built inbound ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:36:11|302021|192.168.0.1|0|192.168.0.250|0|Teardown ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:36:11|302020|192.168.0.1|0|192.168.0.250|0|Built inbound ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:36:05|302021|192.168.0.1|0|192.168.0.250|0|Teardown ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:36:05|302020|192.168.0.1|0|192.168.0.250|0|Built inbound ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:36:01|302021|192.168.0.1|0|192.168.0.250|0|Teardown ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:36:01|302020|192.168.0.1|0|192.168.0.250|0|Built inbound ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:35:59|302021|192.168.0.1|0|192.168.0.250|0|Teardown ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:35:59|302020|192.168.0.1|0|192.168.0.250|0|Built inbound ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:35:57|302021|192.168.0.1|0|192.168.0.250|0|Teardown ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:35:57|302020|192.168.0.1|0|192.168.0.250|0|Built inbound ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:35:56|302021|192.168.0.1|0|192.168.0.250|0|Teardown ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:35:56|302020|192.168.0.1|0|192.168.0.250|0|Built inbound ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:35:56|302021|192.168.0.1|0|192.168.0.250|0|Teardown ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:35:56|302020|192.168.0.1|0|192.168.0.250|0|Built inbound ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:35:56|302021|192.168.0.1|0|192.168.0.250|0|Teardown ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:35:56|302020|192.168.0.1|0|192.168.0.250|0|Built inbound ICMP connection for faddr 192.168.0.1/0 gaddr 192.168.0.250/0 laddr 192.168.0.250/0
  • 6|Dec 04 2012|12:35:55|302013|172.19.2.5|57135|172.20.1.10|443|Built inbound TCP connection 234 for Outside:172.19.2.5/57135 (172.19.2.5/57135) to inside:172.20.1.10/443 (172.20.1.10/443)
  • 6|Dec 04 2012|12:35:55|302014|172.19.2.5|57134|172.20.1.10|443|Teardown TCP connection 233 for Outside:172.19.2.5/57134 to inside:172.20.1.10/443 duration 0:00:00 bytes 1589 TCP FINs
  • 6|Dec 04 2012|12:35:55|302013|172.19.2.5|57134|172.20.1.10|443|Built inbound TCP connection 233 for Outside:172.19.2.5/57134 (172.19.2.5/57134) to inside:172.20.1.10/443 (172.20.1.10/443)
  • 6|Dec 04 2012|12:35:51|302013|172.19.2.5|57133|172.20.1.10|443|Built inbound TCP connection 232 for Outside:172.19.2.5/57133 (172.19.2.5/57133) to inside:172.20.1.10/443 (172.20.1.10/443)
Labels:
0 Helpful
1 Reply 1

mwinnett
Level 3
Level 3

‎12-11-2012 03:29 AM

David, the most recent messages are at the top, so the icmp messages precede the reset. You will need to get a packet capture, but I would guess that something like mtu exceeded, df bit set type issues, The increasing time interval between the icmp messges would be consistent with one side resending tcp packets that are not being acknodledged. Matthew

0 Helpful
Customers Also Viewed These Support Documents
Review Cisco Networking for a $25 gift card