Burton, The IP's that should resolve and don't do show an [IP] flag. The ones that do resolve have no flag and are correctly named (netbios name shown?) Brian
________________________________ From: [EMAIL PROTECTED] on behalf of Burton Strauss Sent: Fri 6/24/2005 12:27 PM To: [email protected] Subject: RE: [Ntop] NTOP latest Win32 Snapshot - DNS question Check - on the ntop host - that these names are really resolvable via nslookup. But first read the docs/FAQ stuff and the back traffic on DNS sniffing. You can turn on the debug flag and - in the host name windows - will be able to see the flags for the resolution state. That will tell you how far ntop has been able to take name res, e.g.: 216.148.226.29 [IP] <http://tigger.burtonstrauss.local:13000/216.148.226.29.html> ^^^ says that this is a numeric IP address Unless it's reached a terminal state, there should be a flag in []s. -----Burton ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ROBERSON, Brian Sent: Friday, June 24, 2005 11:07 AM To: [email protected] Subject: [Ntop] NTOP latest Win32 Snapshot - DNS question I'm noticing that NTOP is not resolving a lot of our internal addresses. This isn't a big problem but mildly irritating having to resolve the address manually. Is there a way to check the configuration to enhance discovery of DNS names? Our environment is Windows 2003 Active Directory. Brian
<<winmail.dat>>
_______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
