![]() ![]() ![]() If you are looking for a quick fix, this can help you get the ip address you really want to remote into. If you are looking for a long term fix, something like this will help you see what ip addresses machines are actually using, and you can compare that to what the dns/dhcp servers think, and you can clean them manually if necessary, correct dhcp address pools, move static IPs, whatever. It has also been pretty handy to just scan the network. For me, it is faster than going onto the server, and has been more accurate in these cases. It can scan an IP (or range), and it gives you the actual hostname on that address. PCFinder ( Opens a new window) comes to mind, though there are likely many other packages that can do the same. I have found some tools can help by returning the hostname of the ip address. If you don't know the correct IP, then pinging only tells you what the DNS table has listed as the right address for the machine. And pinging only helps when you know what PC1's IP really is (basically sitting at the machine and doing an ipconfig). In these situations (which are basically all the ones I have run into), using the FQDN didn't help because they were due to DNS table issues. This one is the most random, but seems to be the most common that isn't first discovered first in other ways (like most of the above). Or, the tables just didn't update at some point. These usually present themselves with errors on the machines though. Various address conflicts particularly with DHCP. Someone moved a static ip address (from an old to new machine for example), may take a while to update on it's own. Usually, you have one of the following will be going on:Ī change in the machine name (takes time for the issue to resolve naturally, or you can go into the dns/dhcp server and delete the bad listings) The ipconfig /flushdns may well take care of it as well, I have mainly learned by doing, so quite often have missed the simplest ways :) Generally, you have the DNS/DHCP server thinking that the Hostname of PC1 goes to IP "X", even when it's IP address is really "Y". ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |