Is there a way to get the IP address of a computer object in AD? I guess it
would be based on the last known IP address. The only reason I am thinking
there may be hope is because there is a attribute called "iphostnumber".

What I would need to do is run a list of about 3000 IP addresses against the
domain to see which computer objects they match up with. A reverse DNS
lookup would not work because we aren't using Windows DNS and it's not truly
dynamic.

I guess one other possibility would be to run the IP list against reverse
netbios lookups, since the names would then mostly match the names of the
computer objects. If someone knows a way of doing that, it may be an
alternate solution. I am not a scripter, but I am guessing something like
"for each do nbtstat -A".

Thanks.

RE: Match IP Address List to Computer Objects by ZiadKChafi

ZiadKChafi
Fri Mar 28 00:43:00 PDT 2008

You can run a script that loops over all IPs and get their corresponding
computer names. I can provide you with a script that writes all computer
names to a small access database in one condition that all computers are
running a Windows version and joined to a domain, if you want it just let me
know.

--
Ziad K. Chafi
MCT, MCTS, MCDBA, MCSE: S, MCAS: S, MCDST, MCP
CompTIA A+, CompTIA N+,


"Baboon" wrote:

> Is there a way to get the IP address of a computer object in AD? I guess it
> would be based on the last known IP address. The only reason I am thinking
> there may be hope is because there is a attribute called "iphostnumber".
>
> What I would need to do is run a list of about 3000 IP addresses against the
> domain to see which computer objects they match up with. A reverse DNS
> lookup would not work because we aren't using Windows DNS and it's not truly
> dynamic.
>
> I guess one other possibility would be to run the IP list against reverse
> netbios lookups, since the names would then mostly match the names of the
> computer objects. If someone knows a way of doing that, it may be an
> alternate solution. I am not a scripter, but I am guessing something like
> "for each do nbtstat -A".
>
> Thanks.

RE: Match IP Address List to Computer Objects by laurazh

laurazh
Fri Mar 28 03:26:47 PDT 2008

1. Considering DNS reverse lookup is unavailable, you may check whether the
customer has WINS server in his environment. If so, Netbios names is
registered on WINS servers.
2. Otherwise, we will have to use Netbios name resolution to get the
Netbios name. However, please let the customer know that Netbios name may
be different from computer account name. To get netbios name, he can use
"ping -a <Ip address>" command.
3. If he would like to develop a script to complete the operation
automatically, he may post to MSDN forums for further help.

Best regards,

Laura Zhang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
====================================================
PLEASE NOTE: The partner managed newsgroups are provided to assist with
break/fix issues and simple how to questions.
We also love to hear your product feedback! Let us know what you think by
posting

from the web interface: Partner Feedback
from your newsreader:
microsoft.private.directaccess.partnerfeedback.

We look forward to hearing from you!
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
====================================================



RE: Match IP Address List to Computer Objects by v-jpzhu

v-jpzhu
Fri Mar 28 04:40:44 PDT 2008

Hello

Thanks for your post as well as to Ziad for the information sharing.

According to your description, my understanding is that you'd like to find
a solution to match all the computer accounts in AD with their IP
addresses. You don't use Windows DNS Server in your domain and DNS reverse
lookup could not be a solution. If there is any misunderstanding, please
let me know.

Analysis and Suggestions:
===================

As DNS reverse lookup would not work, I think the best solution now is to
use NetBIOS name resolution to achieve your requirement.

I am wondering whether you have a WINS Server in your domain?

If yes, you could just collect the data you want from the database on WINS
Server.

If not, you have to query the host name of each IP address in each LAN. If
the computer is turned off when the query is performed, you will not be
able to get its NetBIOS name. You could use 'ping -a IP address' command to
resolve IP address to hostname. Moreover, as the query is based on
broadcast packets, you have to do the query of all IP addresses in all of
your Network.

I also agree with Ziad that you could code a script and run the script to
loop over all IPs and get their corresponding computer names.

The following Script Repository website contains good samples which might
be helpful to you:

Script Repository>Client-Side Printing
http://www.microsoft.com/technet/scriptcenter/scripts/printing/default.mspx?
mfr=true

Please also note that the newsgroups are provided for specific break/fix
issues. For assistance with this coding/development issue, please consider
these resources:

1. MSDN newsgroups
http://msdn.microsoft.com/newsgroups/default.asp

2. Public newsgroups for peer experiences and recommendations:

microsoft.public.windows.server.scripting

http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/defaul
t.mspx?dg=microsoft.public.scripting.vbscript

I hope this helps. Thanks.

Sincerely,
Neo Zhu,
Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


RE: Match IP Address List to Computer Objects by baboon

baboon
Fri Mar 28 13:56:01 PDT 2008

I realized after I posted that NBTStat will not be dependable because most of
the machines will have the Windows Firewall enabled with no NetBIOS
exception. However, getting the data directly from the WINS DB may be a
possibility.

Thanks.

""Laura Zhang[MSFT]"" wrote:

> 1. Considering DNS reverse lookup is unavailable, you may check whether the
> customer has WINS server in his environment. If so, Netbios names is
> registered on WINS servers.
> 2. Otherwise, we will have to use Netbios name resolution to get the
> Netbios name. However, please let the customer know that Netbios name may
> be different from computer account name. To get netbios name, he can use
> "ping -a <Ip address>" command.
> 3. If he would like to develop a script to complete the operation
> automatically, he may post to MSDN forums for further help.
>
> Best regards,
>
> Laura Zhang
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
> ====================================================
> PLEASE NOTE: The partner managed newsgroups are provided to assist with
> break/fix issues and simple how to questions.
> We also love to hear your product feedback! Let us know what you think by
> posting
>
> from the web interface: Partner Feedback
> from your newsreader:
> microsoft.private.directaccess.partnerfeedback.
>
> We look forward to hearing from you!
> ====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from this issue.
> ====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ====================================================
>
>
>

RE: Match IP Address List to Computer Objects by baboon

baboon
Fri Mar 28 14:02:01 PDT 2008

Yes, that would be excellent. Nearly 100% of the computers would be running
XP with SP2 and belong to the same AD domain. They would be spread across
many subnets, but all on the same site, and all connected by Ethernet.

Let me know if you need anything else from me.

Thanks much.

"Ziad K. Chafi" wrote:

> You can run a script that loops over all IPs and get their corresponding
> computer names. I can provide you with a script that writes all computer
> names to a small access database in one condition that all computers are
> running a Windows version and joined to a domain, if you want it just let me
> know.
>
> --
> Ziad K. Chafi
> MCT, MCTS, MCDBA, MCSE: S, MCAS: S, MCDST, MCP
> CompTIA A+, CompTIA N+,
>
>
> "Baboon" wrote:
>
> > Is there a way to get the IP address of a computer object in AD? I guess it
> > would be based on the last known IP address. The only reason I am thinking
> > there may be hope is because there is a attribute called "iphostnumber".
> >
> > What I would need to do is run a list of about 3000 IP addresses against the
> > domain to see which computer objects they match up with. A reverse DNS
> > lookup would not work because we aren't using Windows DNS and it's not truly
> > dynamic.
> >
> > I guess one other possibility would be to run the IP list against reverse
> > netbios lookups, since the names would then mostly match the names of the
> > computer objects. If someone knows a way of doing that, it may be an
> > alternate solution. I am not a scripter, but I am guessing something like
> > "for each do nbtstat -A".
> >
> > Thanks.

RE: Match IP Address List to Computer Objects by v-jpzhu

v-jpzhu
Mon Mar 31 03:08:08 PDT 2008

Hello,

Thank you for the feedback.

I hope the suggestion will be helpful.

If you need any further assistance, please feel free to post back.

Sincerely,
Neo Zhu,
Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.