On Jul 12, 2011, at 9:35 PM, Jacob L. Leifman wrote: >> FWIW, I'm guessing that the problem is at the router. The packet trace is >> showing a TCP SYN coming from the client, followed correctly by a SYN-ACK >> going back from the server. The client should send an ACK packet back, but >> instead it waits several seconds (i.e., timeout) then sends another TCP SYN, >> which would be what happens when the client does not receive the SYN-ACK from >> the server. Can you get a packet trace from the outside interface of the >> router? > > I believe you are right; or at the very least it is some kind of weird > interaction with the router. Unfortunately, this is a consumer DSL > device with no packet capture/trace capability.
Jacob, Just to confirm this, can you get a packet trace from the client showing whether it's receiving the SYN-ACK, and/or if it's sending an ACK back? Also, check to see if the router is expecting to be managed from the outside via https on port 443, so that it is listening on port 443 from the outside but the redirect rule on port 443 is then causing all kinds of weirdness inside the router. --Paul [demime 1.01d removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
