Recommended Posts

It's easy to find the computer name - go to a command prompt and type nslookup <ip>

There are instances where this won't work but without going into detail as to why, give it a shot. If the server is a Windows domain controller and the client PCs are members of the domain it should work fine since they'll have the domain controller specified as the primary DNS server.

if the computer registered with your dns, then yes nslookup will work.. If not are you running dhcp on the server, then look at the leases.

Or you could always just used nbtstat -A ipaddress

C:\>nbtstat -?

Displays protocol statistics and current TCP/IP connections using NBT

(NetBIOS over TCP/IP).

NBTSTAT [ [-a RemoteName] [-A IP address] [-c] [-n]

[-r] [-R] [-RR] [-s] [-S] [interval] ]

-a (adapter status) Lists the remote machine's name table given its name

-A (Adapter status) Lists the remote machine's name table given its

IP address.

-c (cache) Lists NBT's cache of remote [machine] names and their IP addresses

-n (names) Lists local NetBIOS names.

-r (resolved) Lists names resolved by broadcast and via WINS

-R (Reload) Purges and reloads the remote cache name table

-S (Sessions) Lists sessions table with the destination IP addresses

-s (sessions) Lists sessions table converting destination IP

addresses to computer NETBIOS names.

-RR (ReleaseRefresh) Sends Name Release packets to WINS and then, starts Refresh

RemoteName Remote host machine name.

IP address Dotted decimal representation of the IP address.

interval Redisplays selected statistics, pausing interval seconds

between each display. Press Ctrl+C to stop redisplaying

statistics.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.