Problems mapping the QDLS folder to Windows

SUCCESS!!!

Through a combination of things, we've hit upon what works for the QDLS access.

First, and this is a band-aid, but it tells us for sure what the problem was, we enabled the SMB1 client program on the user's Windows 10 configuration. Then we tried having the user connect. Access was denied. After a bit more research I read about the GO NETS menu. I was under the impression that just changing a user's profile, even if you don't change anything and just press Enter, resets the "User disabled for Windows Network Neighborhood" issue. I was WRONG! I found the option on the NETS menu that shows disabled users, found our new user that we were trying to get set up, reenabled him, and POW! It worked!

We will be upgrading to 7.3 of the OS within the next month or so, so we are hoping/assuming the problem will go away after that. Fingers crossed.

Thanks to everyone, especially Rob, for all your help on this one! The midrange.com group never lets me down!

Bill

Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.