Jump to content

Can't file browser server on new image but I can on the old one!


Recommended Posts

Posted

I've got an interesting problem here. I've created an image using MDT, rolled out to a new machine and I realised that folder redirection for the start menus and desktops aren't working.

 

After a bit more investigation, it looks like that although I can't file browse the server (a QNAP device) I can ping it and web browse it. Even if I try to map a drive in the command prompt, it errors with 'The specified network name is no longer available.'

 

Machines built with the old image work fine but this new image doesn't, I've tried building several different machines. It's a brand new image and I've done nothing more than install programs, update Windows and make a couple of unrelated tweaks.

 

I'm not really sure where to start with this, what would you do in my situation?

Posted

Thanks for the quick replies. Fixed it!

 

The QNAP device uses Samba. I needed to alter a setting on the Local Computer Policy. Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network client: Digitally sign communications (always) needed to be changed to Disabled. Makes sense as the QNAP device isn't digitally signed.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...