Packet sniffing problems

From: Dom W. (dom_at_aconcagua.zzn.com)
Date: 03/28/04 

Date: 28 Mar 2004 08:47:21 -0800

Recently, due to the dreaded "inappropriate surfing" problem, my boss
asked me to set up a way to monitor employee surfing habits on our
Windows 2000 server network. I tried out several freeware, shareware,
and trialware packet sniffers and finally settled on one. The problem
is they all seem to be lacking in one thing. I don't know if it's a
problem with the way our network is set up or a problem with the way
I'm using the packet sniffer.

All the programs I tried log the standard: URL, time accessed, time at
site, date, and terminal used. The problem is that at my job we have
about 40 employees using only 4 different terminals. Thus, knowing
only the terminal used isn't much help. Each user has to enter a
login/password to access the system. Is it just not possible for a
packet sniffer to log this user info?