From: Michael Albinus <michael.albinus@gmx.de>
To: Bad Blue Bull <ibmbull@yandex.ru>
Cc: "50399@debbugs.gnu.org" <50399@debbugs.gnu.org>
Subject: bug#50399: TRAMP can't connect to Win 2000 (smb, ftp, telnet)
Date: Wed, 15 Sep 2021 08:55:04 +0200 [thread overview]
Message-ID: <87o88upbuf.fsf@gmx.de> (raw)
In-Reply-To: <16141631658657@mail.yandex.ru> (Bad Blue Bull's message of "Wed, 15 Sep 2021 01:45:03 +0300")
Bad Blue Bull <ibmbull@yandex.ru> writes:
Hi,
> My bad, I didn't know root for FTP is C:\Inetpub\ftproot (was empty
> ofc).
So I guess the FTP access is working now? Good.
> Also I have problems with dired & smb:
>
> dired-get-file-for-visit: File no longer exists; type ‘g’ to update
> Dired buffer [2 times]
>
> I get these "File no longer exists" msgs when browse the shares.
There's a bell ringing in my head with this error message, but I don't
remember when it was fixed. Could you pls pull the recent Emacs git, and
recompile? Your are using
;; Emacs: 28.0.50 Tramp: 2.5.0-pre
which is quite old. Tramp version is 2.5.2-pre these days. If this
doesn't help, pls apply the usual reporting steps:
- Call "emacs -Q --eval '(setq tramp-verbose 6)'"
- Run your test
- Report the steps you have applied, the result, and what you would
expect instead.
- Add the Tramp debug buffer.
Best regards, Michael.
next prev parent reply other threads:[~2021-09-15 6:55 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 9:43 bug#50399: TRAMP can't connect to Win 2000 (smb, ftp, telnet) Bad Blue Bull
2021-09-05 17:46 ` Michael Albinus
[not found] ` <1053251630945528@mail.yandex.ru>
[not found] ` <87lf49ehaa.fsf@gmx.de>
[not found] ` <1059951630951424@mail.yandex.ru>
2021-09-06 19:16 ` Michael Albinus
[not found] ` <1058271630967079@mail.yandex.ru>
2021-09-07 11:48 ` Michael Albinus
2021-09-07 20:44 ` Bad Blue Bull
2021-09-08 7:13 ` Michael Albinus
2021-09-08 10:13 ` Bad Blue Bull
2021-09-08 14:35 ` Michael Albinus
2021-09-10 8:32 ` Bad Blue Bull
2021-09-11 13:50 ` Michael Albinus
2021-09-11 22:52 ` Bad Blue Bull
2021-09-11 23:34 ` Bad Blue Bull
2021-09-12 15:44 ` Michael Albinus
[not found] ` <261061631470250@mail.yandex.ru>
2021-09-13 7:38 ` Michael Albinus
2021-09-13 15:58 ` Bad Blue Bull
2021-09-14 7:13 ` Michael Albinus
2021-09-14 12:55 ` Bad Blue Bull
2021-09-14 17:59 ` Michael Albinus
2021-09-14 18:18 ` Bad Blue Bull
2021-09-14 18:24 ` Michael Albinus
2021-09-14 22:45 ` Bad Blue Bull
2021-09-15 6:55 ` Michael Albinus [this message]
2021-09-15 13:42 ` Bad Blue Bull
2021-09-15 14:42 ` Michael Albinus
2021-09-15 16:09 ` Bad Blue Bull
2021-09-15 16:18 ` Michael Albinus
2021-09-15 16:28 ` Bad Blue Bull
2021-09-15 16:34 ` Michael Albinus
[not found] ` <243411631724679@mail.yandex.ru>
2021-09-15 17:35 ` Michael Albinus
2021-09-15 18:30 ` Bad Blue Bull
2021-09-15 18:56 ` Michael Albinus
2021-09-15 19:26 ` Bad Blue Bull
2021-09-15 19:46 ` Bad Blue Bull
2021-09-16 15:28 ` Michael Albinus
2021-09-16 15:30 ` Michael Albinus
2021-09-16 16:24 ` Bad Blue Bull
2021-09-16 16:33 ` Bad Blue Bull
2021-09-16 16:35 ` Bad Blue Bull
2021-09-16 17:33 ` Michael Albinus
[not found] ` <26141631830717@mail.yandex.ru>
2021-09-16 22:47 ` Bad Blue Bull
2021-09-17 5:36 ` Michael Albinus
2021-09-17 16:02 ` Bad Blue Bull
2021-09-17 16:55 ` Michael Albinus
2021-09-17 18:12 ` Bad Blue Bull
2021-09-17 18:19 ` Michael Albinus
2021-09-17 18:49 ` Bad Blue Bull
2021-09-17 18:54 ` Bad Blue Bull
2021-09-18 7:54 ` Michael Albinus
2021-09-18 8:01 ` Michael Albinus
2021-09-18 9:10 ` Bad Blue Bull
2021-09-18 11:09 ` Michael Albinus
2021-09-18 15:27 ` Bad Blue Bull
2021-09-18 17:02 ` Michael Albinus
2021-09-17 19:03 ` Bad Blue Bull
2021-09-18 7:57 ` Michael Albinus
2021-09-19 18:36 ` Michael Albinus
2021-10-18 8:27 ` Lars Ingebrigtsen
2021-09-16 15:37 ` Michael Albinus
2021-09-15 13:44 ` Bad Blue Bull
2021-09-12 15:37 ` Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o88upbuf.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=50399@debbugs.gnu.org \
--cc=ibmbull@yandex.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).