Excluding IP Addresses fron Analysis in WebTrends

Hi all,

Using WebTrends 7.0 to analyze IIS logfiles.  Trying to exclude internal IP addresses from the web activity reports to get more accurate reporting.  WT allows us to specify IP address masks.  But not all are working.  So do but others do not.  For example, you would think that 192.168.4.23 would be taken care of from 192.168.4.* but it is not.  It still shows up in the reporting.

This is what  WT allows us to do to exclude IP addresses:

"This filter will EXCLUDE log activity that matches at least one value from each of the following filter elements:
User Address = 192.168.3.* | 192.168.4.* | 192.168.4.23 | 192.168.5.* | 192.168.9.* | 10.126.2.* | 192.168.3.119 | 69.64.173.21 | 69.64.173.*"

Any ideas what we're doing wrong ?

Thanks,

John
trzesniakjAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

rama_krishna580Commented:
0
trzesniakjAuthor Commented:
Hi RK,

Thanks for taking the time to respond.  But I was not looking for marketing material on WebTrends or Funnel Web or a comparison between the two.  We use WebTrends and I was looking for an answer to the specific question above.

Meanwhile, we figured out the problem.  We needed to regenerate the report profile after we made the changes to exclude the IP address masks above.

Thanks,

John
0
trzesniakjAuthor Commented:
Actually, we found other problems with this.  The documentation said one thing and the window where you actually specify IP addresses to exclude, offers a different solution.  Also, it cannot use asterisks as IP address wildcards (*) either.  Instead of using pipe symbols as separators ( | ),  we needed to use a space and everything worked fine.  

So this...

"This filter will EXCLUDE log activity that matches at least one value from each of the following filter elements:
User Address = 192.168.3.* | 192.168.4.* | 192.168.4.23 | 192.168.5.* | 192.168.9.* | 10.126.2.* | 192.168.3.119 | 69.64.173.21 | 69.64.173.*"

became this...

"This filter will EXCLUDE log activity that matches at least one value from each of the following filter elements:
User Address = 192.168.3.0-255 192.168.4.0-255 192.168.5.0-255 192.168.9.0-255 10.126.2.0-255 69.64.173.0-255"

and it worked.

Thanks,

John
0
moduloCommented:
PAQed with points refunded (500)

modulo
Community Support Moderator
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Web Servers

From novice to tech pro — start learning today.