By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,077 Members | 1,309 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,077 IT Pros & Developers. It's quick & easy.

How to retrieve, in a Intranet, the name of the client computer that connects to IIS 6.0

P: n/a
Hello,

I have a big intranet that I run with IIS 6.0.

I need to log the client's machine names, and I found on the web istruction
on how to use REMOTE_HOST server variable while enabling Reverse DNS on IIS.

Using also a query to the DNS retrieves only the names of machine that are
registered in the DNS (like servers).

Any idea (both server and client side)? Apparently it worked a time on a
client, but actually I keep getting only the IP on the various machine I'm
using.

Thanks Alot

DevX


Nov 22 '07 #1
Share this Question
Share on Google+
6 Replies


P: n/a
"Michael Nemtsev [MVP]" <ne*****@msn.comwrote in message
news:3d**************************@msnews.microsoft .com...
Don't forget that u need to change security settings for intranet
And be using IE...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net

Nov 23 '07 #2

P: n/a
IIS returns the IP address by default to increase performance. If you want
to set your site or server to do reverse lookups to get the actual hostname,
you'll have to modify your IIS settings. See
http://support.microsoft.com/kb/245574 for details on how to do this.

In your case, the reverse lookup seems to be failing, as is the NetBIOS call
that is executed afterwards. The IIS server returns the IP address as a last
resort.

There is no server-sided script to fix this. You need to look at your
Intranet and server settings to determine why both DNS reverse lookup and
NetBIOS are failing.

HTH

Steve

"DevX" <i.****@esp.amwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...
Hello,

I have a big intranet that I run with IIS 6.0.

I need to log the client's machine names, and I found on the web
istruction on how to use REMOTE_HOST server variable while enabling
Reverse DNS on IIS.

Using also a query to the DNS retrieves only the names of machine that are
registered in the DNS (like servers).

Any idea (both server and client side)? Apparently it worked a time on a
client, but actually I keep getting only the IP on the various machine I'm
using.

Thanks Alot

DevX




Nov 23 '07 #3

P: n/a
Thank to both of you. Luckily we have standardized machines all running IE6.

"Mark Rae [MVP]" <ma**@markNOSPAMrae.netha scritto nel messaggio
news:OB**************@TK2MSFTNGP05.phx.gbl...
"Michael Nemtsev [MVP]" <ne*****@msn.comwrote in message
news:3d**************************@msnews.microsoft .com...
>Don't forget that u need to change security settings for intranet

And be using IE...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net

Nov 23 '07 #4

P: n/a
I have already done the Reverse DNS configuration. Just while I am writing
this, a colleague reports that on his client the server-side stuff works. On
many other clients it did not. (For client I am referring to standard Active
Directory pc connected, not server with a DNS entry).

Can you provide me some link to explore better why the Reverse DNS is
failing? I want to know more about this, NetBIOS et al.

In any case, Many thanks for you time

DevX

"Steve" <ze*************@zen.co.ukha scritto nel messaggio
news:OD**************@TK2MSFTNGP06.phx.gbl...
IIS returns the IP address by default to increase performance. If you want
to set your site or server to do reverse lookups to get the actual
hostname, you'll have to modify your IIS settings. See
http://support.microsoft.com/kb/245574 for details on how to do this.

In your case, the reverse lookup seems to be failing, as is the NetBIOS
call that is executed afterwards. The IIS server returns the IP address as
a last resort.

There is no server-sided script to fix this. You need to look at your
Intranet and server settings to determine why both DNS reverse lookup and
NetBIOS are failing.

HTH

Steve

"DevX" <i.****@esp.amwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...
>Hello,

I have a big intranet that I run with IIS 6.0.

I need to log the client's machine names, and I found on the web
istruction on how to use REMOTE_HOST server variable while enabling
Reverse DNS on IIS.

Using also a query to the DNS retrieves only the names of machine that
are registered in the DNS (like servers).

Any idea (both server and client side)? Apparently it worked a time on a
client, but actually I keep getting only the IP on the various machine
I'm using.

Thanks Alot

DevX





Nov 23 '07 #5

P: n/a
DevX,

I'm not a Windows expert, but imagine that there is some sort of interaction
between Windows DNS and DHCP for the clients that isn't configured
correctly. I would need to know which clients you are running, which
browser, which DHCP, and which DNS.

As I understand it, when a DHCP lease is issued to a client, the DHCP server
updates the DNS server dynamically. So the reverse lookup should work. But
some of the clients or the DHCP server may be configured so that DNS is not
updated. Does this make sense?

Cheers,

Steve

"DevX" <i.****@esp.amwrote in message
news:uT**************@TK2MSFTNGP02.phx.gbl...
>I have already done the Reverse DNS configuration. Just while I am writing
this, a colleague reports that on his client the server-side stuff works.
On many other clients it did not. (For client I am referring to standard
Active Directory pc connected, not server with a DNS entry).

Can you provide me some link to explore better why the Reverse DNS is
failing? I want to know more about this, NetBIOS et al.

In any case, Many thanks for you time

DevX

"Steve" <ze*************@zen.co.ukha scritto nel messaggio
news:OD**************@TK2MSFTNGP06.phx.gbl...
>IIS returns the IP address by default to increase performance. If you
want to set your site or server to do reverse lookups to get the actual
hostname, you'll have to modify your IIS settings. See
http://support.microsoft.com/kb/245574 for details on how to do this.

In your case, the reverse lookup seems to be failing, as is the NetBIOS
call that is executed afterwards. The IIS server returns the IP address
as a last resort.

There is no server-sided script to fix this. You need to look at your
Intranet and server settings to determine why both DNS reverse lookup and
NetBIOS are failing.

HTH

Steve

"DevX" <i.****@esp.amwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...
>>Hello,

I have a big intranet that I run with IIS 6.0.

I need to log the client's machine names, and I found on the web
istruction on how to use REMOTE_HOST server variable while enabling
Reverse DNS on IIS.

Using also a query to the DNS retrieves only the names of machine that
are registered in the DNS (like servers).

Any idea (both server and client side)? Apparently it worked a time on a
client, but actually I keep getting only the IP on the various machine
I'm using.

Thanks Alot

DevX






Nov 23 '07 #6

P: n/a
Thanks,

I think I must work closely to the sys admins of the customer to know better
how the intanet is configured.
For know I know that they use mainly Win 2000 client but the server
architecture is very intricated and I don't know it very well.

I will investigate about the relation between DNS, DHCP and client
configuration.

Bye
DevX
"Steve" <ze*************@zen.co.ukha scritto nel messaggio
news:uI**************@TK2MSFTNGP05.phx.gbl...
DevX,

I'm not a Windows expert, but imagine that there is some sort of
interaction between Windows DNS and DHCP for the clients that isn't
configured correctly. I would need to know which clients you are running,
which browser, which DHCP, and which DNS.

As I understand it, when a DHCP lease is issued to a client, the DHCP
server updates the DNS server dynamically. So the reverse lookup should
work. But some of the clients or the DHCP server may be configured so that
DNS is not updated. Does this make sense?

Cheers,

Steve

"DevX" <i.****@esp.amwrote in message
news:uT**************@TK2MSFTNGP02.phx.gbl...
>>I have already done the Reverse DNS configuration. Just while I am writing
this, a colleague reports that on his client the server-side stuff works.
On many other clients it did not. (For client I am referring to standard
Active Directory pc connected, not server with a DNS entry).

Can you provide me some link to explore better why the Reverse DNS is
failing? I want to know more about this, NetBIOS et al.

In any case, Many thanks for you time

DevX

"Steve" <ze*************@zen.co.ukha scritto nel messaggio
news:OD**************@TK2MSFTNGP06.phx.gbl...
>>IIS returns the IP address by default to increase performance. If you
want to set your site or server to do reverse lookups to get the actual
hostname, you'll have to modify your IIS settings. See
http://support.microsoft.com/kb/245574 for details on how to do this.

In your case, the reverse lookup seems to be failing, as is the NetBIOS
call that is executed afterwards. The IIS server returns the IP address
as a last resort.

There is no server-sided script to fix this. You need to look at your
Intranet and server settings to determine why both DNS reverse lookup
and NetBIOS are failing.

HTH

Steve

"DevX" <i.****@esp.amwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl.. .
Hello,

I have a big intranet that I run with IIS 6.0.

I need to log the client's machine names, and I found on the web
istruction on how to use REMOTE_HOST server variable while enabling
Reverse DNS on IIS.

Using also a query to the DNS retrieves only the names of machine that
are registered in the DNS (like servers).

Any idea (both server and client side)? Apparently it worked a time on
a client, but actually I keep getting only the IP on the various
machine I'm using.

Thanks Alot

DevX






Nov 26 '07 #7

This discussion thread is closed

Replies have been disabled for this discussion.