5 replies
by icb's corner
If your network has a WINS server, use nbtstat command like: nbtstat -A IP.ADD.RE.SS and will return a table. Also you can try with reverse DNS lookup but not every network node has a PTR.
Check with nslookup IP for Windows or dig -x IP for Linux.
by icb's corner
by rrbabbitt
Actually, this has nothing to do with weather or not the network is configured with a WINS server. NBTSTAT -A queries the remote machine's NetBIOS name table (given it's IP address) Of course if you were using the NBTSTAT -a command to query a machine using its name (and that computer were on a different subnet of a multi-tiered network) then perhaps a WINS server would be necessary so that the NBTSTAT command could initiate a connection with the remote computer before it could ask it for its NetBIOS name table.
Therefore (going back to what ICB was saying) the requirement for using the NBTSTAT command in the prescribed method is that the printer itself be able to support NetBIOS. The usefulness of this hostname name, however, will be determined by the complexity of the network. This is when the use of WINS and/or DNS servers become necessary. Which goes back to what ICB was mentioning.. DNS can also be used to match names to IP addresses. In order for this to work, the DNS server must have an entry for the printer. You can use the nslookup command to see if there is a pointer record. In windows, open a command prompt and type:
nslookup .
Then set your query type to PTR:
set q=ptr
and enter the IP.ADD.RE.SS in reverse, attaching the .in-addr.arpa suffix:
SS.RE.ADD.IP.in-addr.arpa
This will display the PTR record if present. You can also try using the following ping command you windows command shell:
PING -A
Good luck :)
by dustyd
by rrbabbitt
Incorrect. Most network printers now support SMB / NetBIOS names. They can register themselves with WINS as well as Microsoft DNS. This has many advantages. In our company, the facilities people own the printer and manage the contracts with the vendor. The people who support the printers are different from the group that supports the servers and network environment. This means moving a printer involved many different people and use to be a pain. The business side would email the facilities people, requesting a printer move. The facilities person would open a ticket with IT. Then the desk-side support tech would move the printer and interface with the other IT groups if required. If the printer?s new location was on a different VLAN, then he would involve the network guys to change the port config so that it could be on the same VLAN and have the same IP as before. Alternately, the support tech would involve the group that manages the Microsoft environment and get them to change the IP / port config on the print server queue.
That is now a thing of the past. The printers now DHCP an address and register themselves in WINS. Our print servers map to them by name, which means that the business can now move printers around as they please without (most of the time) having to involve IT at all.
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending