Title: Application error when trying to save capture
Folks,
I have Ethereal installed on two XP workstations - one works, one doesn't :-(. When I run a capture on the good machine, it collects data as expected, I click Stop and the information is displayed in the Ethereal window. On the bad machine, when I click Stop, it ( depending on my timing ) comes up with another dialog saying it is loading etherXXXX…. ( the last part changes - I assume it is loading data from a temp file into the window ), I see some of the info being loaded into the Ethereal window, then I get the standard Microsoft blurb that tells me that 'Ethereal has encountered a problem and needs to close' and that Microsoft are sorry for the inconvenience - would I like to send a log file to Microsoft? When I click on 'Don’t Send', the Ethereal window closes. Event Viewer shows an event id 1000 - Source Application Error and a Category of None, with a description "Faulting application ethereal.exe, version 0.10.3.0, faulting module adns_dll.dll, version 1.0.0.0, fault address 0x00001279.
I am hoping that someone can point me in the right direction for troubleshooting. Help->About shows the following details…….
Ethereal - Network Protocol Analyzer
Version 0.10.3
Compiled with GTK+ 1.3.0, with Glib 2.2.3
With libz 1.2.1, with libpcre 4.4, with Net-SNMP 5.1, with ADNS.
Running with WinPcap version 3.1 beta3 (packet.dll version 3, 1, 0, 23), based on libpcap version 0.8.1 on Windows XP Service Pack 1, build 2600.
I have upgraded Ethereal from 0.10.3 to 0.10.6 - same problem. The version details change to GTK+ 2.4.4 and GLib 2.4.5.
After going through the archives, I also downloaded the latest ADNS_DLL.DLL file from the web site ( extracted from adsn-1.0-win32-03.zip ), but it hasn't fixed the problem - the faulting address in the event for module adns_dll.dll changes to 0x0000127a.
I downloaded Windump and used that and it is quite happy to collect data on the NIC, so I would assume that that is not the problem ( there are different NICs on the two machines ).
I am definitely a newbie in this sort of area ( my expertise lies in the Microsoft Exchange arena - go figure! ) so please be kind. I just don't know where else to look to try and work out why one machine works and the other doesn't. Any help / assistance / pointers / sympathy would be appreciated.
Thanks,
Paul.