On Wed, Jul 13, 2011 at 3:58 PM, Tracy Pearson <[email protected]> wrote:
> Anybody know what I can look for to a PING response of: > Ping request could not find host boxname. Please check the name and try > again. I'd Google that message. There seem to be some worthwhile suggestions. Windows name resolution can be tricky. Was "boxname" a NetBIOs / Windows PC name, or was it a Fully-Qualified Domain Name (FQDN)? If the former, a Windows name might be resolved by WINS, while a FQDN is resolved using a different set of resources. Each can/may use: locally cached names, WINS, hosts file, arp cache, and/or DNS. You'll want to check if any changes were made to your local network/firewall, or the remote one. And, of course, the #1 advice when running Windows: turn your machine off and back on, and see if it happens again. A disturbing number of issues are cleared, if not resolved, that way. One of our machines in the office is often used for remote VPN work into many clients machines. If we're not careful to turn off all of the software we used to access the remote client (each has their own scheme/VPN provider), we'll get weird name resolution issues, like not being able to find local resources, because the VPN is acting like a network overlaid on top of the actual one, hence, Virtual Private Network. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cacw6n4ve_tsb41g8ppkcdvl_hg+h+xydup59do+35hv7z1x...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
