> Is there a work around to this issue ? Any ideas ?
Not really, unless you install some Java applet, ActiveX control, or other
client-side object that the user then agrees to allow inspect their machine
and relay their real IP address to you. ASP has no way of knowing this...
it runs on the *server* and only knows of the pieces of data that are told
to it through the Request.ServerVariables collection.
Still, not sure how that would be useful to you, because if they're going
through a proxy server, chances are you wouldn't be able to connect directly
to them anyway (often they would only relay an address internal to their
network, e.g. this machine would tell you 192.168.2.17).
The proxy server is usually there for a reason - to prevent people from
knowing / seeing / attacking the client's direct IP. IP is a horrible way
to identify people anyway... did you know that at any one time, as many as
half a million AOL users all look the same, because they all go through a
single IP address?