Thanks, I am hoping to capture traffic on the firewall level
where is suspect the problem is.
To confirm the log on page does not appear, as in stays
completely blank and the timer continues indicating it is loading- but never
does.
I’m also seeing problems with other protocols; SNMP is
intermittent to the NMS and ssh sessions to the device often drop. I notice the
exact packet when it dropped and wireshark revealed ‘TCP previous segment lost’
I’m not sure how to identify a too large MTU, would this be
configured on the interface on the firewall or connecting switch?
Regards,
Chris
From: wireshark-users-bounces@xxxxxxxxxxxxx
[mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Martin
Visser
Sent: 27 June 2010 08:42
To: Community support list for Wireshark
Subject: Re: [Wireshark-users] Https problem
You might need to be a little clearer in your problem
description. Are you saying the "login page does appear" or did you
really mean does *not* appear?
If you are getting RST packets when your browser is trying
to connect a new TCP session (this might be happening when your browser is
being redirected by the first HTTP/HTTPS session) then it is likely this second
site is being blocked by firewall or some other similar device enforcing
policy, possibly based on your IP address.
Lost segments are also an issue - they can occur because of
congestion or even something like packets being sent with a too large MTU, and
being dropped along the path back to you.
Regards, Martin
MartinVisser99@xxxxxxxxx
