Sometimes DNS lookups are cached (for faster subsequent lookups).
John Hinckley wrote: > Ok this is strange. Just to make sure I rechecked "Enable concurrent DNS > name resolution" and it loaded just as quickly. I also enabled name > resolution as well and it still loaded just as quickly. > > The only thing I can think of is that I rebooted inbetween the last time I > loaded the capture file and loading it this time around. > > Odd. > > John > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of John Hinckley > Sent: Wednesday, September 26, 2007 9:59 AM > To: 'Community support list for Wireshark' > Subject: Re: [Wireshark-users] slow loading cap file > > I actually had "Enable network name resolution" disabled but I had "Enable > concurrent DNS name resolution" checked; disabling this made the file load > in about 2 seconds. > > TY for the point in the right direction! > > John > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Morriss > Sent: Wednesday, September 26, 2007 8:28 AM > To: Community support list for Wireshark > Subject: Re: [Wireshark-users] slow loading cap file > > > > John Hinckley wrote: >> I have a relatively small capture file (2.2mb) and it takes approximately > 5 >> minutes to load this capture file. Is this normal? I'm using the latest >> version of wireshark for winxp and I have 1GB mem on a P4 system. > > Do you have name resolution (DNS resolution) turned on? Try turning it off: > > Edit->Preferences->Name Resolution > > and uncheck the "Enable network name resolution" box. _______________________________________________ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
