From: Chris Fellows on
Can someone tell me how to look up the machine name of the client's browser
in Classic ASP? I want to do it without having to install any third party
DLLs. I can get the client's IP address but I don't know which object to use
to do a DNS lookup.

From: Evertjan. on
Chris Fellows wrote on 06 jul 2010 in
microsoft.public.inetserver.asp.general:

> Can someone tell me how to look up the machine name of the client's
> browser in Classic ASP? I want to do it without having to install any
> third party DLLs. I can get the client's IP address but I don't know
> which object to use to do a DNS lookup.

Not available, as that would be a breach of security.

Google is your friend:

http://blogs.msdn.com/b/ericlippert/archive/2005/05/09/how-to-obtain-the-
name-of-the-client-from-the-asp-server.aspx

--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)
From: Dan on

"Chris Fellows" <nospam(a)hotmail.co.uk> wrote in message
news:#Nqf22MHLHA.5700(a)TK2MSFTNGP04.phx.gbl...
> Can someone tell me how to look up the machine name of the client's
> browser in Classic ASP? I want to do it without having to install any
> third party DLLs. I can get the client's IP address but I don't know which
> object to use to do a DNS lookup.

You can't even get this when the user is authenticated to the site using
NTLM, so no there is no way to get it without a DLL installed in the
*browser*.

You might be able to do a reverse DNS lookup to get the public FQDN of the
connecting IP, but that is very rarely the machine name of the browser. You
would need to install a 3rd party DLL on the *server* for this though, there
is no standard object that provides this functionality. You might be able to
code something up using the ServerXMLHTTP object passing the IP address to
web server on another system that does the lookup for you, but it's not
something I'd recommend, especially as it will significantly slow down your
scripts while the lookup is being done.

Why do you need this information? If it's for some sort of additional
authentication step, have you considered looking into client side
certificates for per-machine proof of "identity"?

--
Dan