使用 DHCP 从 IP 获取 MAC 地址？

发布于 2024-08-12 07:00:18 字数 227 浏览 6 评论 0原文

我正在尝试创建允许通过 WOL 唤醒 Windows 域中的 PC 的脚本/服务。现在我想让用户选择一个 AD 容器作为唤醒其中包含的 PC 的起点。我最初的想法是使用 DHCP 作为存储库来查询给定主机名的 MAC 地址（给定容器，我可以轻松地从 AD 中提取主机名）。

有没有办法以编程方式查询 DHCP 服务/服务器、传递主机名并恢复关联的 MAC 地址？

或者，有更好/更简单的方法来解决我的问题吗？

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

心是晴朗的。 2024-08-19 07:00:19

尝试 dhcpexim。 exe 来自微软。

或者，如果您更喜欢使用纯 C。 DhcpEnumSubnetClientsV4

回复收藏 0 原文

放我走吧 2024-08-19 07:00:19

没问题;因为所有计算机都在您的域中，所以您可以编写一个 VBScript，该脚本将从本地计算机获取 MAC 地址并将其作为计算机对象的属性存储在 Active Directory 中。

以下是有关如何执行此操作的快速技巧（将其另存为 .vbs 文件）：

Option Explicit

Const ADS_PROPERTY_UPDATE = 2
Const COMPUTERLOCATION = "ou=Member Servers,dc=yourdomain,dc=com"
Const ATTRIBUTETOUSE = "otherTelephone"

Dim wshNetwork, strComputerName
Set wshNetwork = WScript.CreateObject("WScript.Network")
strComputerName = wshNetwork.ComputerName

Dim objWMIService, colNetCards, objComputer, objNetCard
Set objWMIService = GetObject("winmgmts:\\" & strComputerName & "\root\cimv2")
Set colNetCards = objWMIService.ExecQuery("Select * From Win32_NetworkAdapterConfiguration Where IPEnabled = True")
Set objComputer = GetObject("LDAP://cn=" & strComputerName & "," & COMPUTERLOCATION) 
For Each objNetCard in colNetCards
    objComputer.PutEx ADS_PROPERTY_APPEND, ATTRIBUTETOUSE, Array(objNetCard.MACAddress)
    objComputer.SetInfo
Next

因为您的客户端并不全部位于上面的“成员服务器”OU 中，所以您需要修改上面的脚本以包含目录搜索 strComputerName< /code> 获取COMPUTERLOCATION。

当您有一个工作脚本时，请您的域管理员将该脚本作为针对您需要监视的计算机的启动脚本；这样它就会在计算机启动时执行。您还可以将脚本作为计划任务运行，以从任何尚未重新启动的客户端获取数据或使用 psexec 或您可以想到的其他方式来立即获取数据。或者，您可以完全重写脚本以远程连接到所有计算机并以这种方式获取数据（由于本地防火墙，这可能无法实现）。或者您可以编写一个小型 .NET 控制台应用程序来执行相同的操作，这取决于您...

此外，尽管为计算机对象定义了一个 networkAddress 属性；但默认情况下，计算机对象本身无权写入此属性。因为启动脚本在特定计算机上的 SYSTEM 帐户上下文中运行，所以最简单的事情是使用计算机对象 (SELF) 具有写入访问权限的属性。 otherTelephone 属性是多值的，并且是个人信息属性集，默认情况下所有计算机对象都具有写入权限。如果您想使用 networkAddress 属性，您需要为所有计算机设置对该属性的显式写入访问权限。

此外，您还需要记住，将 MAC 地址存储在 Active Directory 中意味着您域中的所有用户都将具有对其的读取访问权限，这反过来可能（取决于您的环境）造成较小的安全风险。

No problem; because all of the machines are in your domain you can put together a VBScript that will get the MACAddress(es) from the local machine and store it as an attribute of the computer object in Active Directory.

Here's a quick hack on how to do that (save this as a .vbs-file):

Option Explicit

Const ADS_PROPERTY_UPDATE = 2
Const COMPUTERLOCATION = "ou=Member Servers,dc=yourdomain,dc=com"
Const ATTRIBUTETOUSE = "otherTelephone"

Dim wshNetwork, strComputerName
Set wshNetwork = WScript.CreateObject("WScript.Network")
strComputerName = wshNetwork.ComputerName

Dim objWMIService, colNetCards, objComputer, objNetCard
Set objWMIService = GetObject("winmgmts:\\" & strComputerName & "\root\cimv2")
Set colNetCards = objWMIService.ExecQuery("Select * From Win32_NetworkAdapterConfiguration Where IPEnabled = True")
Set objComputer = GetObject("LDAP://cn=" & strComputerName & "," & COMPUTERLOCATION) 
For Each objNetCard in colNetCards
    objComputer.PutEx ADS_PROPERTY_APPEND, ATTRIBUTETOUSE, Array(objNetCard.MACAddress)
    objComputer.SetInfo
Next

Because your clients aren't all in the "Member Servers" OU above you'll need to modify the above script to include a directory search for the strComputerName do get the COMPUTERLOCATION.

When you have a working script, ask your domain administrator to put the script as a start-up script targetting the computers you need to monitor; that way it'll execute whenever a computer boots up. You can also run the script as a scheduled task to get your data from any clients that haven't rebooted or use psexec or some other way you can think of to get the data immediately. Or you can rewrite the script entirely to remote connect to all of your machines and get the data that way (which might not be possible due to local firewalls). Or you could write a small .NET console application which does the same thing, it's up to you...

Also, although there is a networkAddress-attribute defined for computer objects; by default the computer object itself does not have access to write to this property. Because start up-scripts run in the context of the SYSTEM account on the particular machine the easiest thing is to use an attribute that the computer object (SELF) has write access to. The otherTelephone-attribute is multivalued and part of the Personal-Information Property Set which all computer objects has write access to by default. If you want to use the networkAddress-attribute you need to set explicit write access to that attribute for all of your computers.

Also you need to bear in mind that storing the the MAC address in Active Directory means that all of the users in your domain will have read access to it which in turn might possibly (depending on your environment) pose a small security risk.

回复收藏 0 原文