Remember how sometimes and often recurrently we need to know what machine is doing something on the network, and we only have the IP address ?
Well this windows comandline command from a windows machine on that LAN will give you that very same info - so we can run this from the PDC:
nbstat -r -A
......as evidence by:
G:\>nbtstat -r -A 10.243.102.148
Local Area Connection:
Node IpAddress: [10.243.102.75] Scope Id: []
NetBIOS Remote Machine Name Table
Name Type Status
---------------------------------------------
DREW <00> UNIQUE Registered
GGG_IT <00> GROUP Registered
DREW <03> UNIQUE Registered
DREW$ <03> UNIQUE Registered
DREW <20> UNIQUE Registered
GGG_IT <1e> GROUP Registered
MAC Address = 00-16-E6-D9-06-B0
Given that it gives us some rather redundant information - but it does tell us the remote machine name and the MAC Address - which might be useful.
Well this windows comandline command from a windows machine on that LAN will give you that very same info - so we can run this from the PDC:
nbstat -r -A
......as evidence by:
G:\>nbtstat -r -A 10.243.102.148
Local Area Connection:
Node IpAddress: [10.243.102.75] Scope Id: []
NetBIOS Remote Machine Name Table
Name Type Status
---------------------------------------------
DREW <00> UNIQUE Registered
GGG_IT <00> GROUP Registered
DREW <03> UNIQUE Registered
DREW$ <03> UNIQUE Registered
DREW <20> UNIQUE Registered
GGG_IT <1e> GROUP Registered
MAC Address = 00-16-E6-D9-06-B0
Given that it gives us some rather redundant information - but it does tell us the remote machine name and the MAC Address - which might be useful.
No comments:
Post a Comment