How about a good old ping?
ping -n 1 test10
If you are looking to write code use Powershell.
(Test-NetConnection test10).RemoteAddress.IPAddressToString
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi All,
Windows 10, pro and home
In Windows Explorer (not IE), when I click on Network in the left column, I get a list of computer CIFS broadcast names in the right pane. Well, after a bit.
I know how to add the IP column in Windows explorer, but ..
Is there a way to translate CIFS NETBIOS broadcast names into IP addresses from the command line?
Many thanks,
-T
How about a good old ping?
ping -n 1 test10
If you are looking to write code use Powershell.
(Test-NetConnection test10).RemoteAddress.IPAddressToString
I brought up a Win10 test VM and changed the NIC from DHCP to use a hardcoded IP address that had no DNS entry. I pinged the machine and got back an IPV6 address. I removed IPV6 from the network on the VM and then ping was able to see the IPV4 address.
I just tried it again and ping failed. But the Windows Explorer also failed. On the VM I tried to use the Windows Explorer to see what it saw in the Network folder and it reported that network discovery was not started. I ran my PS script from the below link and rebooted.
Both Ping and Explorer now work.
This site says that ping uses the Netbios name.
https://www.cbfive.com/ping-vs-nslookup/
If ping fails for you, does Explorer still work?
except for the home edition,
I'm running Win10 Home 2H1 and I can add the IP address column.
Check your network settings on both machines to see if Netbios is enabled.
The local network computer are not in DNS.
There are two problems
1) folks naming their workstations the same name as the server
2) the add columns on a few computers is missing half the view section. So I never know when I can use Windows Explorer to find IP's.
So I am looking for a command line way to do a WDS lookup. I can write it myself if I can find the correct api call.
The local network computer are not in DNS.
Why not? Is there some network limitation? Who "owns" the network? Is this a home environment? A business environment?
1) folks naming their workstations the same name as the server
Who "owns" the desktop support? If you have a business environment, then end users should not get to pick their own workstation name. And it certainly should not be the same name as the server. What kind of server is this? Are you using Windows Server Essentials? What about Active Directory? Who supports/owns DNS?
the add columns on a few computers is missing half the view section. So I never know when I can use Windows Explorer to find IP's.
If you need to get IP's, then all machines should be registered in DNS. That's what it's there for.
So I am looking for a command line way to do a WDS lookup. I can write it myself if I can find the correct api call.
No, this is an XY problem.