Wireshark mailing list archives
Network Name resolution
From: ketzal devims <ketzaldevims () gmail com>
Date: Tue, 2 Feb 2010 17:22:25 +0100
Hi all, I'm using Microsoft Windows XP and Wireshark 1.2.5 which is the latest stable version. I have a problem with name resolution for network layer. I put a hosts file in both place (%USERPROFILE%\Application Data\Wireshark\ and c:\WINDOWS\system32\drivers\etc\) I activated Network Layer Name Resolution, with concurrent DNS (500) as default parameter, and then, name resolution works (almost) perfectly. That mean that wireshark search correctly the ip/name association: - first in the hosts files - and then I guess to DNS servers. The issue is the following: When I disconnect my network cable, that mean that I'm not able to reach a DNS server, and I open a wireshark trace, wireshark is freezing, and I need to stop the processus by hand. Looks like threading for DNS request is associated with trace display... and if one fails, the other too. Is it a bug or a misconfiguration from my part? Does someone know how to solve that problem? Thanks a lot in advance. Best Regards ketzaldev
___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org?subject=unsubscribe
Current thread:
- Network Name resolution ketzal devims (Feb 02)
- Re: Network Name resolution Anders Broman (Feb 02)
- Re: Network Name resolution ketzal devims (Feb 02)
- Re: Network Name resolution Anders Broman (Feb 02)