We become indebted to.

Currently, an Ubuntu virtual machine is created on Windows 10 and mounted using the following cifs command.

sudo mount -t cifs -o username = {user_name}, dir_mode = 0777, nolock, file_mode = 0777, uid = 1000, gid = 1000, vers = 2.1 // {windows IP address}/Users/{windows10 username }/mnt/windows

Until the morning, the mount was successful with this command, and I was able to see the files on the windows 10 side from the Ubuntu side, but I could not mount with the above command after the internet connection of the personal computer was interrupted around noon. I got the following error.

mount error (2): No such file or directory
Refer to the mount.cifs (8) manual page (e.g. man mount.cifs)

I didn't know the cause, so I restarted Windows 10 and started Ubuntu again, but the result was the same.
I also tried the following:
-Communication from windows10 cmd to both sides from ubuntu terminal with ping command is possible.
-The "// {windows IP address}/Users/{windows10 user name}" directory of the above command exists on the Windows 10 side.
-The "/ mnt/windows" directory of the above command exists on the Ubuntu side.

It seems that the reason why it could not be mounted was that the net connection was once cut off.
Also, the command is executed on the same directory as when the previous mount was successful.
I understand the content of the error message because there are directories on both Windows 10 side and Ubuntu side, and I do not remember performing any file operations between the time when the mount was possible and the time when it was not possible. It's not done ...

I'm a complete beginner when it comes to building an environment, so I'm sorry if you ask a fairly rudimentary question.
I would appreciate it if you could tell me who knows the cause.

For installing Ubuntu on windows10, I referred to the following site and proceeded almost according to the procedure.
The final virtual machine created will be Ubuntu 64-bit on Linux.
Reference URL

  • Answer # 1

    I'm sorry, this is a self-solve.
    I mentioned in the question that I couldn't mount after the network was disconnected, but at that time the IP address assigned to Windows 10 changed and I couldn't connect ...

    This time, I made a lot of noise due to my lack of confirmation. I would like to be careful in the future.