2- If your station is in a Windows Active Directory domain, in this case check if you "ping" the remote machine by using its full name: ping (or remotecomputer is the name of the remote computer and pointdev.local the name of your Active Directory domain). This point should be considered because a good many functionalities of our products use the name resolution when trying to to access remot hosts. If the remote host does not answer when it is pingued by its hostname but answer when pingued with its IP address, please check on the remote host the DNS properties. 1 - Check that you can ping with the CMD prompt the remote host (by its IP address or by its physical NetBIOS name), and that the host answers without significant packet loss. To resolve this error, please verify the following points : The network path was not found" is a common native message of Microsoft Windows Operating System and is not directly related to Pointdev software The message " System error 53 has occurred. Try IDEAL Administration during 30 days on your network for free!Īctive Directory Management & Reporting Made Easy with IDEAL Administration (installed in 2 minutes) When i try to access a physical resource on my network (server or computer) with your software, I get sometimes the "System error 53 has occurred. The network path was not found" message ? What are the errors generally encountered by our software? How to troubleshoot the "System error 53 has occurred.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |