NetBT can issue a NetBIOS adapter status request (also called a NetBIOS node
status request) to the destination IP address, and then parse the returned
name table for the name registered by the server service
(<computername>[0x20]) - eg nbtstat -a IPaddress.
This will also work with Windows sockets applications through the
gethostbyaddr() call using the following sequence:
1.Check local computer host name.
2.Check the HOSTS file for a matching address entry.
3.If a DNS server is configured, query it.
4.If no match is found, send a NetBIOS Adapter Status Request to the IP
address being queried, and if it responds with a list of NetBIOS names
registered for the adapter, parse it for the computer name.
Doug Sherman
MCSE, MCSA, MCP+I, MVP
<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> Hi,
>
> I have a box doing reverse IP lookups, and I dont know how.
>
> We have no reverse DNS set up.
>
> We have no WINS/NBNS server set up.
>
> Nothing in LMHOSTS.
>
> Despite this it is reverse resolving the IP address (that it knows) to
> the Netbios/NBT name (that it shouldnt know).
>
> The devices are on routed subnets so are not within the broadcast
> domain for normal Netbios/NBT.
>
>
>
> If the normal reverse lookup methods fail, does the windows resolver
> unicast to the box and lookup the name ala nbtstat?
>
>
>
> Thanks,
> Lauren
>
|