> First the access to share "C$", then access to the shares "scripts"

> and "src"

Yes, I noticed it. C:\scripts doesn't even exist.

the instance of smbclient running according to ps -aux is

/usr/bin/smbclient //win2k/C$ -U nicolas -s /dev/null --option client min protocol=NT1

before I enter password. Then I enter password and then half minute after:

/usr/bin/smbclient //win2k/src -U nicolas -s /dev/null --option client min protocol=NT1

I've no idea about these scripts and src 'shares'.

Why am I prompted for password every time? It's empty password saved many times into ~/.authinfo.

*Messages*:

----

Tramp: Opening connection for //nicolas@win2k/C$...done

Tramp: Inserting ‘/smb:nicolas@win2k:/C$/boot.ini’...done

File error: NT_STATUS_OBJECT_NAME_NOT_FOUND ‘/smb:nicolas@win2k:/C$/scripts/’

Tramp: Opening connection for //nicolas@win2k/scripts...

Tramp failed to connect. If this happens repeatedly, try

‘M-x tramp-cleanup-this-connection’

Tramp: Opening connection for //nicolas@win2k/scripts...failed

Tramp: Opening connection for //nicolas@win2k/src...done

----

17.09.2021, 19:55, "Michael Albinus" <michael.albinus@gmx.de>:

Bad Blue Bull <ibmbull@yandex.ru> writes:

Hi,

I downloaded this archive
http://git.savannah.gnu.org/cgit/emacs.git/snapshot/emacs-f29abc3db6abf6a9ef54106990b749a12fc53211.tar.gz

Btw, it would be much easier if you install git locally, and clone the repository.

It's pretty like what happened yesterday. I get thet tramp/smb
process killed window, then half minute after boot.ini file is opened,
sometimes successfully sometimes not (I get empty buffer called
boot.ini then).
*debug* buffer attached (boot.ini was opened successfully)

So at least my fix has worked, calling "emacs --eval '(setq
tramp-verbose 6)' /smb:nicolas@win2k:/C$/boot.ini" opens the file
boot.ini. Progress!

But then, you haven't tested as I have asked you. There are changes in
the shares:

--8<---------------cut here---------------start------------->8---
18:52:21.852272 tramp-smb-maybe-open-connection (6) # smbclient //win2k/C$ -U nicolas -s /dev/null --option client min protocol=NT1
18:52:26.507803 tramp-smb-maybe-open-connection (6) # smbclient //win2k/scripts -U nicolas -s /dev/null --option client min protocol=NT1
18:52:30.838004 tramp-smb-maybe-open-connection (6) # smbclient //win2k/src -U nicolas -s /dev/null --option client min protocol=NT1
--8<---------------cut here---------------end--------------->8---

First the access to share "C$", then access to the shares "scripts" and
"src". We know already that this causes problems. Therefore, I would
like to ensure that navigating on the same share "C$" doesn't cause
problems. Could you pls test accordingly?

Thanks, and best regards, Michael.