I think by default nvsniffer is simply a TCP port scanner, tell me if I
am wrong. It pings the port to see if it exist, then it adds it to the
database. I use it to discover services or applications where I know
exactly which TCP port it uses. If you application uses dynamic port as
some I have seen, I have to write a custom .DLL to detect them. I
found nvsniffer most useful during initial discovery. I found the
status check function to be somewhat inacurate, by default it checks
once every hour on the NT version. When a service goes Down, you have
to wait an hour before the system will try it again. If there's a easy
to launch nvsniffer against a particular service on demand, it may be
more helpful.
Xu He
Network Solutions, Inc
--- Don Davis <don-n-darla@WORLDNET.ATT.NET> wrote:
> Has anyone used the nvsniffer command
> successfully???
> I have not been able to make it function properly.
>
> It discovers all services on all nodes whether it
> actually is present or not!
>
>
> --
> ======================================================
>
> Don Davis - Instructor / Consultant
> Alliance Of Professionals and Consultants, Inc.
> Phone: 919-847-6056 Pager: 800-759-8888 PIN:
> 1462396
> Visit our Web site at: http://www.apc-services.com
>
_________________________________________________________
Do You Yahoo!?
Free instant messaging and more at http://messenger.yahoo.com
|