1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Dismiss Notice

Welcome To SNBForums

SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.

If you'd like to post a question, simply register and have at it!

While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!

Asus RT-AC68U Mapped Drives Windows 10 error/disconnects constant Error 0x8007010B

Discussion in 'Asuswrt-Merlin' started by xbones, Feb 22, 2019.

  1. xbones

    xbones New Around Here

    Joined:
    Feb 22, 2019
    Messages:
    3
    So ever since the latest Windows 10 update and the lastest Merlin firmware 384.9, there have been more and more reports of users getting error 0x8007010B when transferring or trying to connect to their mapped drives via Asus router usb.

    I'm not that technical with all the jiber jaber of what is the cause but I did find a solution and I was hoping you could implement it in the next version of your Amazing Asuswrt-Merlin firmware.

    The error is when you try transferring a folder to a mapped drive:

    "An unexpected error is keeping you from moving the folder. If you continue to receive this error, you can use the error code to search for help with this problem.
    Error 0x8007010B: The directory name is invalid."

    I click Try again and it works fine. But every folder I receive this error.

    The fix is here!!

    https://www.snbforums.com/threads/error-0x8007010b-on-rt-ax88u.54205/

    Can you implement to next firmware or is this something the end user has to do manually?

    Thank you for all your work!
     
    Last edited: Feb 28, 2019
    Vexira likes this.
  2. xbones

    xbones New Around Here

    Joined:
    Feb 22, 2019
    Messages:
    3
    BUMP any word on a fix for this? I reverted back to 384.7 and the problem went away, definitely firmware issue.
     
  3. Jack Yaz

    Jack Yaz Very Senior Member

    Joined:
    Apr 20, 2017
    Messages:
    1,616
  4. L&LD

    L&LD Part of the Furniture

    Joined:
    Dec 9, 2013
    Messages:
    7,523
  5. EmeraldDeer

    EmeraldDeer Senior Member

    Joined:
    Dec 22, 2017
    Messages:
    257
    Location:
    Massachusetts
    I am using Windows 10 to access ext4 filesystems via Samba version 2 only. The smb defaults have worked flawlessly for me.

    I infer that the original poster wants the smb.conf firmware default to change as if their circumstance is universal. The default in question might be changing "store dos attributes = yes" to "no".

    I suspect that changing the default from yes to no may cause as many problems as it may solve. However, after hours of web searches, I have not found informed, concrete arguments either way. Whether it is an SMBv1 (deprecated), NTFS issue or something else, who knows.
     
    L&LD likes this.
  6. ColinTaylor

    ColinTaylor Part of the Furniture

    Joined:
    Mar 31, 2014
    Messages:
    7,759
    Location:
    UK
    I'd agree with this. I was also curious as to why this change has suddenly become necessary. I spent probably more hours than was sensible trying to get to the bottom of it but never did.

    It appears to be an NTFS-only issue. It doesn't appear to be related to the SMB protocol particularly. The current setting for "store dos attributes" appears to be correct, and has been working for many years without problem. So I'd be reluctant to change the router's default as that would be a"work around" to an unidentified problem rather than a fix.

    I suspect it's a compatibility problem with the NTFS driver on the router, but I can't prove that as I can't reproduce the problem. If anybody can reproduce it that might help.
     
    L&LD likes this.
  7. xbones

    xbones New Around Here

    Joined:
    Feb 22, 2019
    Messages:
    3
    Indeed, my drives are formatted with NTFS. Thanks for taking the time for the above replies, appreciate the efforts!
     
  8. ColinTaylor

    ColinTaylor Part of the Furniture

    Joined:
    Mar 31, 2014
    Messages:
    7,759
    Location:
    UK
    @RMerlin I think this problem is connected to an update of the Tuxera NTFS driver (tntfs.ko).

    Reports of this problem on the RT-AC68U started appearing after release of 384.8_0. This coincides with a change from the old driver (3015.1.29.8_1) to 3018.6.22d.

    Reports of the problem on the RT-AC86U go back as far as the initial commit of GPL 3.0.0.3.382_15098. The driver back then was 3016.7.1.2.3 and has subsequently also been updated to 3018.6.22d.

    So my guess is the problem was introduced somewhere between versions 3015.1.29.8_1 and 3016.7.1.2.3.

    Do you have any thoughts? I know these are binary blobs so you can't fix them. Does your crystal ball see any updated drivers appearing in the near future? Perhaps it's a problem with Samba. I see that Tuxera ship a modified version of smbd, but it's not used as far as I can tell.

    To anyone else with this problem: Have you tried the current stock Asus firmware? Does that have the same problem?

    Disclaimer: This is all speculation on my part as I don't run any of the effected firmware versions.
     
  9. RMerlin

    RMerlin Super Moderator

    Joined:
    Apr 14, 2012
    Messages:
    29,305
    Location:
    Canada
    I don't. I have no info regarding the Tuxera drivers.
     
  10. ColinTaylor

    ColinTaylor Part of the Furniture

    Joined:
    Mar 31, 2014
    Messages:
    7,759
    Location:
    UK
    OK Thanks anyway.

    I wonder how "stand alone" the driver is? I'm wondering whether it's possible to rmmod the current driver and insmod the old one, for testing purposes. Then again, presumably there's a reason Tuxera updated the driver, bug fixes etc.