Wireshark-users: Re: [Wireshark-users] Slowdown after mounting DFS network drives
Hello Janos,
Possibly to answer the last question:
"Rephrasing my question, how can I use the capture file to show the DFS
admin that there is a problem here."
You might need a bit more detail here, before you can give this to your admin.
You said that you mount these drives with a script, and then you referenced the issue with Windows Scripting Host.
You might want to double check to see whether you get the same behavior when you mount the drives manually.
Looking at the service response times for SMB, everything looks fine, and as Bill stated, it looks like you connect, look for the DLL, then disconnect and try again.
It seems like you have your answer already, and there is not much else that Wireshark can do for you to prove your point.
Based on a quick google search for this file, it seems like it's a known issue.
The DLL doesn't exist, so you are going to have to try the workaround given in the link you referenced.
Once you have done that foot work, take it to your admin.
Remember, they should be able to follow your logic, so think of it as though someone were handing this issue to you and asking you to solve it.
Try to answer those questions ahead of time.
Hope that helps.
-- Mike
On Mon, Apr 5, 2010 at 2:35 PM, János Löbb
<janos.lobb@xxxxxxxx> wrote:
On Apr 5, 2010, at 4:18 PM, Bill Meier wrote:
> János Löbb wrote:
>>
>> What do you think the problem is ??
>>
>
>
> It looks to me like the PC is trying several times to find a DLL on
> the
> server, getting a 'not found' return and then timing out for 4 or 10
> secs and trying again.
>
> I suggest you open the capture file, filter on one of the TCP
> conversations (statistics ! conversations) and see for yourself. :)
>
> ___________________________________________________________________________
Hi Bill,
Yes, I saw that one, already three months ago in my wireshark
captures, and asked the DFS server admin if there is a timeout for
client access can it be set to a lower value and he said to me there
is no such thing.
That particular dll wshenu.dll - Windows Scripting Host English - does
not even exist on the client PC and it does not exist on the DFS
servers either. However Windows Exploder, IE and any script created
with Windows Scripting is looking for it.
http://forum.sysinternals.com/topic5696.html
Rephrasing my question, how can I use the capture file to show the DFS
admin that there is a problem here. I sent him similar captures 3
months ago.
Thanks ahead,
János
