Skip to main content

Get hostname from an IP in Windows

Get hostname from an IP in Windows


Method 1 - Using built-in ping. This only works if a working DNS server has reverse look-up configured.
c:\>ping -a 8.8.8.8

The hostname for 8.8.8.8 was returned as dns.google, below shows the output details.
Pinging dns.google [8.8.8.8] with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=52ms TTL=112
Reply from 8.8.8.8: bytes=32 time=56ms TTL=112
Reply from 8.8.8.8: bytes=32 time=59ms TTL=112
Reply from 8.8.8.8: bytes=32 time=56ms TTL=112

Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 52ms, Maximum = 59ms, Average = 55ms

Method 2 - Using nslookup
c:\>nslookup 8.8.8.8

This is the same as method 1, it needs a working DNS to provide the information
Server:  somedc.com
Address:  some_ip_here

Name:    dns.google
Address:  8.8.8.8

Method 3 - Using nbtstat
c:\>nbtstat -a 192.168.1.101

With the added bonus that it also shows the MAC address and name M1. Limitiation is that this only works on network that supports NetBIOS and on the same collision domain.
vEthernet (nat):
Node IpAddress: [172.20.64.1] Scope Id: []

    Host not found.

Ethernet:
Node IpAddress: [192.168.1.100] Scope Id: []

           NetBIOS Remote Machine Name Table

       Name               Type         Status
    ---------------------------------------------
    WORKGROUP     	<00>  GROUP       Registered
    M1			  	<00>  UNIQUE      Registered
    M1     		  	<20>  UNIQUE      Registered

    MAC Address = 00-15-5D-0E-53-54

Method 4 - Using psexec
c:\>psexec \\192.168.1.101 -u administrator -p p@$$w0rd hostname

This is using psexec to run hostname command remotely. Note that it shows the hostname (M1), IP, and exit code of the command hostname.
PsExec v2.2 - Execute processes remotely
Copyright (C) 2001-2016 Mark Russinovich
Sysinternals - www.sysinternals.com


M1
hostname exited on 192.168.1.101 with error code 0.

Comments

Popular posts from this blog

The following add-ins could not be started MonoDevelop.GnomePlatform

Installing MonoDevelop in OpenSUSE 12.2 from its repository was very easy. When running it for the first time though I got the message: The following add-ins could not be started: The root of the trace shows MonoDevelop.GnomePlatform,2.8 A quick search shows that MonoDevelop depends on libgnomeui . This should have been part of dependencies when installing the application but well.... Below is the screen shot of the error message. References: http://software.1713.n2.nabble.com/MonoDevelop-and-openSUSE-12-1-td7462957.html [2013/04/09] - Same issue observed in OpenSUSE 12.3 and also the same fix. [2014/11/02] - Same issue observed in OpenSUSE 13.3, mondevelop 3.0.6 and the same fix.

Error! Could not locate dkms.conf file install VirtualBox 4.1.8 on Ubuntu 11.10

Tried to update my Ubuntu host today and it did pickup that new version of VirtualBox is available (4.1.8). All other packages installed properly except that VirtualBox installation was complaining about missing dkms.conf file, see error message below. $: sudo /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel modules [ OK ] * Uninstalling old VirtualBox DKMS kernel modules Error! Could not locate dkms.conf file. File: does not exist. [ OK ] * Trying to register the VirtualBox kernel modules using DKMS [ OK ] * Starting VirtualBox kernel modules [ OK ] Though it looks like installation was fine but I am concerned about its effects to VirtualBox functionality. To fix this, do: $: cd /var/lib/dkms/vboxhost $: sudo rm -r 4.1.4 $: sudo /etc/init.d/vboxdrv setup Of course you have to re