bug#50399: TRAMP can't connect to Win 2000 (smb, ftp, telnet)

[Bad Blue Bull]

yes, it certainly matters.

 

 

11.09.2021, 16:51, "Michael Albinus" <michael.albinus@gmx.de>:

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

Hi,
 

 sorry for late response. can you try this link please:
 https://drive.google.com/file/d/1xY5xMS-QzMcWYwG1ATXEUzhlk4M1F0hC/view?usp=sharing

Thanks. This tells us more:

13:08:08.822916 tramp-send-command (6) # exec telnet 192.168.0.141 2>/dev/null
13:08:08.828755 tramp-action-login (6) #
Trying 192.168.0.141...
Connected to 192.168.0.141.
Escape character is '^]'.
Microsoft (R) Windows (TM) Version 5.00 (Build 2195)
Welcome to Microsoft Telnet Service
Telnet Server Build 5.00.99206.1
login:
13:08:08.828990 tramp-action-login (3) # Sending login name €nicolas€

Well, this calls telnet, and sends also your login name. After one
minute, this times out, as specified in Tramp.

13:09:08.908391 tramp-process-actions (10) #
  backtrace()
  tramp-error((tramp-file-name "telnet" "nicolas" nil "192.168.0.141" nil "" nil) file-error "Timeout reached, see buffer €*tramp/telnet nicolas...")

Hmm. Not clear why this happens here. I've just tested locally, and
telnet still works (yes, I had also to remove the "%n" argument from the
"telnet" entry in tramp-methods).

Perhaps a problem with CR/LF handling on your MS Windows telnet server?
What happens, if you set tramp-rsh-end-of-line to "\r\n" ?

Best regards, Michael.

Yes, CR/LF certainly matters.  Now I need only fix tramp-shell-prompt-pattern

(string-match-p tramp-shell-prompt-pattern "smb: \\>")

returns 0, and smb works

(string-match-p tramp-shell-prompt-pattern "C:\\> ")

also returns 0 but tramp doesn't recognize telnet prompt.... (see telnet screenshot)

 

2021-09-12-011905_804x484_scrot.png
Description: PNG image