Home / server / Questions / 794996
Accepted
ColLeslieHapHapablap
Asked: 2016-08-05 23:08:39 +0800 CST

Windows 10 PE Unable to map network drive anonymously

  • 772

I'm trying to set up a imaging environment. The idea is to use DISM to apply WIM images (Windows 10 Pro) over the network.

I am able to boot into Windows 10 PE. I have network connectivity via DHCP.

When I try to map the network share using net use i: \\server\share I get: 

System error 58 has occurred. 
The specified server cannot perform the requested operation.

If I try to map it with net use i: \\server\share /user:user password where user is a system user, it works.

The share is is completely public. I am able to map the share with no credentials on 4 other Windows machines. (2x Win7, 2x Win8).

The server is Ubuntu 14.04 running Samba. 4.3.9-Ubuntu.

My /etc/samba/smb.conf looks like this:

[global]
    workgroup = WORKGROUP
    security = user
    server string = Imaging Server
    dns proxy = no
    follow symlinks = yes
    wide links = yes
    unix extensions = no
    log file = /var/log/samba/log.%m
    max log size = 1000
    guest account = nobody
    encrypt passwords = true
    map to guest = bad user

[share]
    comment = images
    path = /share
    browsable = yes
    guest only = yes
    read only = no
    writable = yes
    public = yes
    create mask = 0664
    directory mask = 0775

/share is owned by nobody:nogroup

Any ideas would be appreciated.

network-share samba samba4 net-use windows-pe

3 Answers

  1. Best Answer

    That's just how Windows 10 connects to anonymous shares: it checks some username and password to see if it is able to log in, and if so it allows an anonymous connection.

    Apparently whatever part hides this from the user didn't make it into the PE build, so just specify a dummy username and password, like /user:user pass.

    If you need to provide actual credentials you can specify a user and password like this: /user:DOMAIN\user *. The star will make sure you are prompted for your password instead of having to specify it on the command line.

    • 8

  2. Doesn't seem to be a Linux issue, seems to be Windows 10 as I have the same issue. The fix I have researched seems to be this... example... net use z: //192.168.02/tftp \root: 192.168.0.2 /root password

    I have not tried this will be attempting it at work tomorrow.

    • 1

  3. I tried the same on a number of occasions. I actually never made it work using a completely anonymous connection but just supplying any user / pass combination seems to work out with shares that are configured the way yours are.

    • 1