> There was a fix in version 1.6.5 to correct the “Closing file” issue. I
have some servers running Windows 2003 Server SP 2 on
> which I connect with Remote Desktop, when I capture into file on them and I
disconnect the next morning when I arrive I have
> many “closing file” windows opened and my server become less responsive… When
I do “end task” on a couple of them
> they all disappear and Wireshark stop. Is there any option on my remote
desktop server settings or should I open a trouble?
> It’s not happening when locking the session, only when disconnecting.
>I don't know of any remote desktop option that could help you, although there
>certainly might be. It's probably worth opening a new bug report for this.
>By the way, are you able to use ALT+F4 to close the "Closing file" dialog,
>instead of doing an "end task", as suggested by Ian Eales in comment 10 of
>bug 3046?
>https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3046#c10
>I will try the ALT-F4
>Thanks.
I just tried and the ALT-F4 close the "closing file" dialog without crashing wireshark.
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
