Dos Error 58
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring
Dos Error 5
developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ dos error 64 Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's
Dos Error 4
how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top System error 58 while accessing shares on Windows 7 from XP up vote 14 down vote favorite dos error level 13 I get the following error message while accessing Windows 7 shares from XP. System error 58 has occurred. The specified server cannot perform the requested operation. Both machines are in same domain. Windows XP machine can view and access all other shares except Windows 7. Neither machines have a firewall. windows-7 share|improve this question edited Sep 17 '13 at 16:25 Hennes 50.9k776120 asked Sep 27 '09 at 1:28 nysingh 5501510 Have you checked windows 7 shares and dos error code 1 confirmed they are allowing access to your username or usergroup? –A Dwarf Sep 27 '09 at 1:57 yes. same users is logged onto both machines. not even net view works. –nysingh Sep 27 '09 at 3:22 1 Restarting the Server service in Windows 7 was enough to fix my problem. –user79246 May 1 '11 at 17:08 1 Stopping and restarting the sever service on the Win 7 x64 box allowed the XP machine to connect to the share hosted by the Win 7 x64 box. This was definitely less traumatic than any other fix. This problem seems to come and go, supporting the thesis that there is some kind bug that can be eliminated temporarily, but always comes back eventually. –user240389 Jul 24 '13 at 13:29 add a comment| 6 Answers 6 active oldest votes up vote 19 down vote Changing the NTLM settings in the Local Policies did not work for me. What did work is mentioned here: link text ...you need to tell Windows that you want to use the machine as a file server and that it should allocate resources accordingly. Set the following registry key to ‘1′: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache and set the following registry key to ‘3′: HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size After changing the two registry settings, I simply restarted the "Server" service in Windows 7 and now the sharing is working fine. share|improve this answer edited Oct 7 '10 at 17:4
Invalid environment 11. Invalid format 12. Invalid access code 13.
Dos Error 53
Invalid data 14. Reserved 15. Invalid drive was specified dos error 2 16. Attempt to remove the current directory 17. Not same device 18. No more files
Dos Error Handling
19. Attempt to write on write-protected diskette 20. Unknown unit 21. Drive not ready 22. Unknown command 23. Data error (CRC) 24. Bad request http://superuser.com/questions/47382/system-error-58-while-accessing-shares-on-windows-7-from-xp/146437 structure length 25. Seek Error 26. Unknown media type 27. Sector not found 28. Printer out of paper 29. Write fault 30. Read fault 31. General failure 32. Sharing violation 33. Lock violation 34. Invalid disk change 35. FCB unavailable 36. Sharing buffer overflow 37-49 Reserved 50. Network request http://www.itlnet.net/programming/program/Reference/Doserr.htm not supported 51. Remote computer not listening 52. Duplicate name on network 53. Network name not found 54. Network busy 55. Network device no longer exists 56. Network BIOS command limit exceeded 57. Network adapter hardware error 58. Incorrect response from network 59. Unexpected network error 60. Incompatible remote adapter 61. Print queue full. 62. Not enough space for print file 63. Print file deleted (not enough space) 64. Network name deleted 65. Access denied 66. Network device type incorrect 67. Network name not found 68. Network name limit exceeded 69. Network BIOS session limit exceeded 70. Temporarily paused 71. Network request not accepted 72. Print of disk redirection paused 73-79 Reserved 80. File already exists 81. Reserved 82. Cannot make directory entry 83. Fail on INT 24H 84. Too may redirection 85. Duplicate redirection 86. Invalid password 87. Invalid parameter 88. Network device fault
Studio 2015 products Visual Studio Team Services Visual Studio Code Visual Studio Dev Essentials Office Office Word/Excel/PowerPoint Microsoft Graph Outlook OneDrive/Sharepoint Skype Services Store Cortana Bing Application Insights Languages & platforms https://msdn.microsoft.com/en-us/library/windows/desktop/ms681382(v=vs.85).aspx Xamarin ASP.NET C++ TypeScript .NET - VB, C#, F# Server Windows Server https://lists.samba.org/archive/samba/2004-August/090624.html SQL Server BizTalk Server SharePoint Dynamics Programs & communities Students Startups Forums MSDN Subscriber downloads Sign in Search Microsoft Search Windows Dev Center Windows Dev Center Explore What’s new for Windows 10 Intro to Universal Windows Platform Coding challenges Develop for accessibility Build for enterprise Windows Store opportunities Docs Windows apps dos error Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Why Windows Dashboard Explore What’s new for Windows 10 Intro to Universal Windows Platform Coding challenges Develop for accessibility Build for enterprise Windows Store opportunities Docs dos error 5 Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Why Windows Dashboard Error Handling Error Handling Reference System Error Codes System Error Codes System Error Codes (0-499) System Error Codes (0-499) System Error Codes (0-499) System Error Codes (0-499) System Error Codes (500-999) System Error Codes (1000-1299) System Error Codes (1300-1699) System Error Codes (1700-3999) System Error Codes (4000-5999) System Error Codes (6000-8199) System Error Codes (8200-8999) System Error Codes (9000-11999) System Error Codes (12000-15999) TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. System Error Codes (0-499) Note The information on this page is intended to be used by programmers so that the software they write can better deal with errors. If you are an end-user that is experiencing difficulty with an application you are installing or running, contact customer support for the software that is displaying the
] [ thread ] [ subject ] [ author ] Hi all, yesterday i switched from Samba 3.0.5 to 3.0.6 RC2 because we want to upgrade our Windows XP clients to SP2 which seems to cause printing problems with all older versions of Samba. Unfortunately this reintroduced a problem regarding DOS ( please see http://lists.samba.org/archive/samba/2004-July/089609.html ) which i already had experienced when i switched from Samba 3.0.4 to 3.0.5RC1. After the next update to Samba 3.0.5 DOS was working fine again. Is there something special to consider when using LanMan with Samba 3.0.6 ? regards, Ulf Previous message: [Samba] adding users to smb pdc smb3 backend Next message: [Samba] DOS error 58 is back Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the samba mailing list