Article ID: 121913 - Last Review: October 10, 2003 - Revision: 2.0

Err Msg: Error 59: An Unexpected Network Error Has Occurred

Retired KB ArticleRetired KB Content Disclaimer
View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
This article was previously published under Q121913
Expand all | Collapse all

SYMPTOMS

When you use the NET USE command to a server and share that does not exist, the following error message may appear:
Error 59: An Unexpected Network Error Has Occurred
In addition, attempting to connect to a nonexistent server and share using File Manager causes the system to stop responding (hang). To quit Windows for Workgroups version 3.11 and reboot the computer, press CTRL+ALT+DEL and press ENTER when the blue screen appears.
Back to the top

CAUSE

This problem occurs if the "DNS for Windows Name Resolution" option is enabled and the IP address for a DNS server is not specified in the DNS Server search list.
Back to the top

RESOLUTION

If a DNS Server is not available, disable the "DNS for Windows Name Resolution" option under Windows Networking Parameters in the Advanced Microsoft TCP/IP Configuration dialog box. If a DNS Server is available, make sure that its IP address is added to the DNS Server search list in the Microsoft TCP/IP - Connectivity Configuration dialog box.
Back to the top

MORE INFORMATION

When you attempt to connect to a nonexistent network server and share using the NET USE command, the expected error message is "Error 53: The computer name specified in the network path cannot be located." If the same operation is performed in File Manager, the same error message should appear in a STOP message dialog box without "Error 53."
Back to the top
APPLIES TO
  • Microsoft TCP/IP for Windows for Workgroups 3.11
  • Microsoft Windows for Workgroups 3.11
Back to the top
Keywords: 
KB121913
Back to the top
Retired KB ArticleRetired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Back to the top