I need to really block someone out... Need advise

[Quarterbore]

OK, I have been trying to block out via IP address but frigen AOL has made this all but impossible...

WHen I go on the "Whosonline Page I get this info under IP address:

cache-mtc-ab07.proxy.aol.com

If I go to "detailed info" I get this:

cache-mtc-ab07.proxy.aol.com
Mozilla/4.0 (compatible; MSIE 6.0; CS 2000 6.0; NS Connect 6.0; Windows NT 5.1)

I have blocked close to a dozen AOL IPs for this same "guest" but they still keep getting to see he content as they just seem to dial in and get a different connection and hence a different IP address.

I want to be able to recode my hack here:

https://vborg.vbsupport.ru/showthread.php?t=127288

To BLOCK ALL AOL PROXY viewing using the "cache-mtc-ab07.proxy.aol.com" or similar problem AOL Proxy accounts of guests... in fact, I am starting to hate AOL to the point that I would like to be able to identify just the "proxy.aol.com" in the IP and I am ready to just lock out all AOL guests.

I hate how AOL makes it so easy for PITA individuals to just dial in again and they get a new IP...

So, I know that this can be done because the who's online page resolves this... I just need some help getting the info from the browser of the user and get it in the format like we see on the who's online page and then I can code the block as a Rev 2 of my hack...

Thanks for any advise!
Ken

[Paul M]

You want to block everyone using AOL because of one person ?

[Quarterbore]

Well, my hack blocks guests from seeing threads and posts... They can see the forums, they can log in and see the site, they can even register...

I have contacted AOL but they don't seem to be able to get to the problem... I have tools to detect multiple IDs (cookie level and IP level as well as E-mail) but because of the way AOL handles IP addresses I really can't lock them out... I can easily lock them back out after they are a problem....

So, what I plan to do is require AOL users to be logged in to see the forums... Too many problems with AOL anymore... Perhaps I am looking too hard for a fix that is overkill but it really is what I am after at this time...

After a few months, I can turn it back off as they should have moved on by then....

LAST EDIT -

This has now been incorporated into my IP_NoView! product for vB 3.5.x and 3.6.x. and you can find it here:

https://vborg.vbsupport.ru/showthread.php?p=1080839