[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 536
  • Last Modified:

net use //unixserver password user:root --> error 5 Access is Denied

We are using the below listed command to connect to a UNIX server from a Windows 2003 server.

net use  //unixserver  password  user:root

At some point recently the command has stopped working, and is producing the error "System Error 5 has occurred. Access is denied."

We suspect that sometime recently Windows changed its method of authentication. We are using VisionFS 3.10.905 to map drives. This product may or may not have anything to do with the issue at hand.

1. Does anyone have a solution to this issue. Please do not reply unless you have tried the solution and it works.

2. Who currently supports VisionFS, and do you have a number at which they may be contacted.
0
gbm33
Asked:
gbm33
  • 5
  • 4
1 Solution
 
gheistCommented:
Roll back windows service pack or use registry to allow NTLMv1
0
 
gbm33Author Commented:
gheist: Thank you for the information. I don't think I want to tackle rolling back Windows 2003 SP2 just yet. Can you tell me how to alter the registry to allow NTLMv1?
0
 
gheistCommented:
http://support.microsoft.com/kb/954387

Another option to consider is using Samba from skunkware instead of visionfs, or updating visionfs.
0
 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

 
gbm33Author Commented:
gheist: Thanks for the article. The setting for LMCompalibilityLevel was at 2. I tried each of the other settings, but with no change in behavior. It seems to me that 1 should be the setting that would give the widest authentication allowance. We have yet been unable to find who supports visionFS and/or if there is a new version available. It would seem to me that there is some setting somewhere within Windows, similar to the one you suggested, that could be changed to roll back the compatibility. Until now visionFS has served us well. Only as a last resort do we want to move to Samba  
0
 
gheistCommented:
VisionFS is SCO product. You have to disable it completely for samba to succeed. Can you repeat problem from different client?
0
 
gbm33Author Commented:
gheist:

I have been working with Microsoft for several days on this issue without a solution. The issue, we have determined, is not with visionFS. The problem only occurs from the Windows 2003 server.  When connecting from a Windows XP client there is not a problem. If I get a solution from Microsoft I will  post it here. Regardless, I am open to any other suggestions you might have.
0
 
gheistCommented:
Try removing saved drive mapping and recreate it - maybe that is the case.
0
 
gbm33Author Commented:
All: Thank you for your assistance. We spent many hours, to include a session opened with Microsoft, and were not able to solve the issue. As a result we abandoned visionFS and installed Samba. I still feel the disruption was caused by Microsoft. But visionFS was not able to handle it, and Samba was.

As a result, unless there is an objection, I will be accepting this Comment as the solution.
0
 
gheistCommented:
Then accept Samba suggestion.
0

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now