7 doesDirectory/media/autofs/HDESKTOPGO8801 not exist

[druidz]

Since reinstalling windows 10 and a complete set of updates I can no longer connect to my media drives on my desk top of which there are three (H,I,and J) This message haunts me every time (Directory/media/autofs/HDESKTOPGO88017 does not exist)

I can not resolve this issue after having tried many options on the forum.
I am network connected and running properly.
Windows 10 home version fully updated all drives shared with Everyone.
All Networks Shared with Everyone and password protection is off.
I have run this T4 without many issues since it's inception until the past three weeks and now I am frustrated
I have reinstalled firmware 17.5 to no avail.
Please review the attachments below as I am really hopeful that someone has experienced this problem and may have a simple solution. Hoping you can assist so I can again view all my video media

[MrQuade]

I can not resolve this issue after having tried many options on the forum.

It would help to list the options you have tried so that we don't cover old ground then.



Do the mounts on your T4 include the "vers=2.1" option? This is a requirement for connecting to Windows 10 shares.

Prior to your re-installation, you may have force enabled SMB version 1 on your Windows box? This is normally disabled by default for security reasons.

You will also need to enter a username and password when setting up the mount on the T4, though I suspect you have done that since you can see the share names.

[druidz]

Thank you for your reply I have checked PowerShell and SMB v 2.1 exists and shows true.

[Paul_oz53]

Thank you for your reply I have checked PowerShell and SMB v 2.1 exists and shows true.

I believe MrQuade was referring to the mount options field in the mount manager on the T4 for each share on your windows pc. Win10 now requires that vers=2.1 or higher be present or that you reenable SMB1.

I use:

Code: Select all

rw,utf8,vers=3.0

as my mount option for the Win10 folders. I also added a Windows 10 user account and password in the mount manager because Win10 was playing hardball without it.

[druidz]

Thank you Paul I have looked at both options offered by yourself and Mr McQuade but neither have resolved my issue. My mount is set as yours (rw,utf8) and I have user name and passwords in each mount. I can see all mounts but windows will not play ball. It must be some thing simple I have used it for a few years until recently. My user name has changed since I did a fresh install of windows 10 as I did it in haste and did not pay attention when setting up. Frustrated in the small hours of the morning, but nothing else has changed.

[druidz]

Hi Paul I revisited your recommendation and added (,vers=3.0) in my mount and eureka the door was opened thank you very much I would never have found that on my own I am an ageing proficient computer user but no more than that. Once again thank you kindly.

[raymondjpg]

I also added a Windows 10 user account and password in the mount manager because Win10 was playing hardball without it.

I think you'll find that it has to be a Win 10 non-administrative Local account to work. I've been caught out a couple of times trying to connect (unsuccessfully) using an administrator account. I don't know the reason why.

[MrQuade]

Hi Paul I revisited your recommendation and added (,vers=3.0) in my mount and eureka the door was opened thank you very much I would never have found that on my own I am an ageing proficient computer user but no more than that. Once again thank you kindly.

Glad that is sorted now.

You should consider updating to firmware 19.1. it is due for public release very very shortly, and includes many fixed and enhancements, particularly in light of this case, the vers=2.1 option is now included by default.

[druidz]

I will thanks. I always keep an eye out for updates but thanks for the information. I have a question given you seem knowledgeable why is it that the Beyonwiz updates are not updateable automatically as in the settings. The last two had to be downloaded manually and installed by USB.

Once again thanks for taking the time to assist me I am so pleased with your help I am up and running.

[MrQuade]

The online updates apply incremental changes to a known stable base of firmware.

Sometimes, the firmware needs a big rebuild with lots of new fundamental components, or it is merged with improvements from similar PVR models. In this case it is often nearly impossible to reconcile all the changes between versions, so a format and USB unstsllation is required.

In some cases, the changes are so dramatic, that it would be unsafe to even restore your saved settings on the new version because all the options have been tweaked and changed. In that instance, a USB installation and setup from scratch is required.

Any time a USB update is required, the major version number of the firmware will change. For example, v the T4 firmware major revision has changed from 4.4 to 16.1 to 17.5 and view to 19.1. Since 16.1, the version number actually represented the date on which it was first built (19.1 means it was originally built in January 2019).

If you register to the beta updates, you will find that you will get incremental online updates more often, though at the cost of potentially hitting a couple of speed bumps along the way.

[prl]

Any time a USB update is required, the major version number of the firmware will change. For example, v the T4 firmware major revision has changed from 4.4 to 16.1 to 17.5 and view to 19.1. Since 16.1, the version number actually represented the date on which it was first built (19.1 means it was originally built in January 2019).

I think that you have that a bit the wrong way around. If the major firmware number (or firmware series number) changes, then a USB update is required.

However, it can also be the case that a USB upgrade is required, or at least strongly recommended, in other circumstances, mostly when a large number of firmware packages have changed in an upgrade that does not change the firmware series version. This is particularly true if you are following the beta releases, as you are suggesting that druidz does.

[Paul_oz53]

I also added a Windows 10 user account and password in the mount manager because Win10 was playing hardball without it.

I think you'll find that it has to be a Win 10 non-administrative Local account to work. I've been caught out a couple of times trying to connect (unsuccessfully) using an administrator account. I don't know the reason why.

Indeed it is a Local account in my case too. Like you, no idea why an administrator account wouldn't work.

Glad that the problem is resolved.

Just being pedantic but, if peteru's news is realized, the next official firmware is based on 19.3 and may come out this weekend. I only mention this to (edit) save others confusion over the version number.

[druidz]

Thanks to everyone for your help and input much appreciated.

[MrQuade]

Indeed it is a Local account in my case too. Like you, no idea why an administrator account wouldn't work.

Most probably a policy of Microsoft to help you from shooting yourself in the foot. If you give a share administrative access, then you are opening your entire computer up to potential intrusion and possible exploitation.

Rule of thumb is to only ever grant the minimum permissions for something to work, and no more than that. It is also why you shouldn't regularly log in as a user with full administrative access. Even if it is unlikely to be exploited, it helps ensure you don't do anything dumb by accident.

[raymondjpg]

Most probably a policy of Microsoft to help you from shooting yourself in the foot. If you give a share administrative access, then you are opening your entire computer up to potential intrusion and possible exploitation.

Rule of thumb is to only ever grant the minimum permissions for something to work, and no more than that. It is also why you shouldn't regularly log in as a user with full administrative access. Even if it is unlikely to be exploited, it helps ensure you don't do anything dumb by accident.

Heaven preserve me from Microsoft's control over how I use my PC. Looking at it more logically, I'd say such a restriction was more likely to be in Microsoft's interest in not being accused of lax security, something that has been on foot for years.

I quite knowingly log in as a user with full administrative access, fully aware of the risks and what precautions need to be taken. I take the point, though, that many people who do this will be blissfully unaware. Such people, according to some gurus, could not be trusted to keep their systems patched, so we'll have MS do it for them, like it or not.