Compare cert salaries and plan your next career move
Slowhand wrote: you can even use Windows Network Monitor.
sprkymrk wrote: Slowhand wrote: The free version of netmonitor only sniffs packets originated from or destined to the host on which it is running. You probably knew but I thought I would mention it anyway. I'd actually forgotten that it was only able to pick up traffic on its own NIC, (the free version, at least). Still, it should be able to analyze traffic that's being sent over a hub, since it's one big collision domain. You're right, though, TCPDump/WinDump is a good way to go.
Slowhand wrote: The free version of netmonitor only sniffs packets originated from or destined to the host on which it is running. You probably knew but I thought I would mention it anyway.
kenny504 wrote: Thanks alot buddy i have heard of snort I'll try it now. yeah i edited the question i really meant a good sniffer.
Slowhand wrote: sprkymrk wrote: Slowhand wrote: The free version of netmonitor only sniffs packets originated from or destined to the host on which it is running. You probably knew but I thought I would mention it anyway. I'd actually forgotten that it was only able to pick up traffic on its own NIC, (the free version, at least). Still, it should be able to analyze traffic that's being sent over a hub, since it's one big collision domain. Unfortunately, collision domain or not, it only shows you packets that originated on your host, or packets that have your host as the destination address. Nice of MS to make a nice tool and then castrate it, huh?
sprkymrk wrote: Slowhand wrote: The free version of netmonitor only sniffs packets originated from or destined to the host on which it is running. You probably knew but I thought I would mention it anyway. I'd actually forgotten that it was only able to pick up traffic on its own NIC, (the free version, at least). Still, it should be able to analyze traffic that's being sent over a hub, since it's one big collision domain.
sprkymrk wrote: Unfortunately, collision domain or not, it only shows you packets that originated on your host, or packets that have your host as the destination address. Nice of MS to make a nice tool and then castrate it, huh?
Slowhand wrote: sprkymrk wrote: Unfortunately, collision domain or not, it only shows you packets that originated on your host, or packets that have your host as the destination address. Nice of MS to make a nice tool and then castrate it, huh? That's because Microsoft loves us. . . the way a kid with a magnifying glass loves ants.
seuss_ssues wrote: kenny504 wrote: Thanks alot buddy i have heard of snort I'll try it now. yeah i edited the question i really meant a good sniffer. Im not really one to come on here and disagree with people, but you might take another look at ethereal/wireshark. It is one of the best sniffers out there.http://sectools.org/ < It was listed as #2 on the top 100 security tools of 2006. The survey was answered by 3,243 hackers/security professionals through insecure's nmap-hacker's mailing list. edit Additionally snort is a full fledged IDS. It would be more of a hassle to use if you are only trying to sniff traffic.
Compare salaries for top cybersecurity certifications. Free download for TechExams community.