Wireshark · Ethereal-dev: Re: [Ethereal-dev] bug: ethereal 0.9.15 - win32 with mac name resolution hangs

[Lars Roland <Lars.Roland@xxxxxxx>]

Hello Dale,

I am sorry, my question wasn't precise enough.

I asked for ZoneAlarm, because I have seen your symptons with ZoneAlarm 
and the use of the ADNS library, which was introduced in ethereal 
version 0.9.12 or 13. In ethereal 0.9.15 the ADNS library is only used, 
if you enable "concurrent name resolution" in the preferences.

Because of a recent bug (see 
http://www.ethereal.com/lists/ethereal-dev/200311/msg00066.html ), 
ethereal could interpret your "enable transport name resolution" as 
"enable concurrent DNS name resolution".

So my question is, what happens, when you enable "concurrent name 
resolution" ? Although you don't have ZoneAlarm, another program running 
in the background may freeze ethereal as ZoneAlarm did on my PC.

Best Regards,

Lars Roland

Dale.Schaafsma@xxxxxxxxxx wrote:
> Hi Lars,
>  Guy had me do several different troubleshooting steps, changing around 
> which decoding was enabled (network transport, network name, mac name). 
> In doing so, we caused the problem to disappear....unfortunately this 
> means I can't reproduce the problem anymore.
>  As for your question on firewalls, no there aren't any firewalls that 
> are enabled on my system. So that should eliminate any packet blocking 
> further down in the stack.
> Regards,
>  Dale