So, I've browsed the web for a similar problem (and solution) as I have but nothing really comes close.
I have started to experience failure while trying to map network shares. This does only seem to apply to linux based servers (Synology and Equallogic) and only from clients/servers deployed via our MDT/WDS solution. I could have two "identical" servers (2008 r2) or clients (Windows 7), one installed from DVD and one from MDT/WDS image, and the DVD installed one would work while the custom deployed would not. I do not have any special security settings (as far as I know) in the deployment, the images are fairly basic.
When trying to map the shares via cmd and "net use" I receive either: "System error 58" or "System error 64". The DNS resolution works since I can ping the servers without problem. However, I cannot map with net use using the IP either. Other network shares from other Windows machines are working great, it's just these Linux based storage machines that I'm having trouble with.
Again, the only thing I find that they "problem machines" have in common is that they are custom deployments and not installed straight from DVD.
Am I missing something super easy?
- Changed type Vincent Wang-MCSCMicrosoft contingent staff, Moderator Thursday, April 25, 2013 9:22 AM
Please check what have you changed in this custom image.
In addition, here is a tip about access Linux Partitions From Windows.
Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
TechNet Community Support
Thanks for your reply, Vincent!
The only thing I can think of is that both the client and the server image are created in a VM in VMware.
Could there be something "missing" or anything like that since they're not made from physical machines?
I've also done some Wireshark tracing, comparing a functioning, manually installed pc with a custom image deployed one. The functioning PC gives about 7 packet rows in Wireshark while the failing one throws over 25 before stopping. In the last couple of rows it also seems to be trying http and getting a 405 error. What's that about?
Ok, I've done a small breakthrough in the troubleshooting. Instead of using my automated solution via MDT, I've taken the custom .WIM file and added it to WDS directly and then installed it "manually" via standard WinPE for Windows 7, using the guide. No Task Sequence or Unattend.xml has been used. After manually joining the computer to the domain I had no trouble mapping the CIFS share.
The error thus seems to be lying somwhere in ts.xml or Unattend.xml and not in the .wim itself?
I realize this is probably the wrong forum for this issue now. Could it be moved to the Deployment forums?
For Setup Deployment forum, you can refer to the following link:
TechNet Community Support