Bug 8839 - "smbclient -M" leads to "NT_STATUS_PIPE_BROKEN"
Summary: "smbclient -M" leads to "NT_STATUS_PIPE_BROKEN"
Status: RESOLVED WONTFIX
Alias: None
Product: Samba 3.5
Classification: Unclassified
Component: libsmbclient (show other bugs)
Version: 3.5.11
Hardware: x64 Linux
: P5 normal
Target Milestone: ---
Assignee: Derrell Lipman
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-04 11:09 UTC by Yann Ormanns
Modified: 2020-12-19 21:39 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yann Ormanns 2012-04-04 11:09:14 UTC
I'd like to send a message from a Linux system (Gentoo) to Windows 7 
Ultimate by using "smbclient -NM vm_windows7 -I 10.0.0.19". 
Unfortunately, I only get "NT_STATUS_PIPE_BROKEN" and no message is sent.

Here is the complete output:
--------
Atlas ~ # smbclient -NM vm_windows7 -I 10.0.0.19 -d11
smbclient: /usr/lib64/libtdb.so.1: no version information available 
(required by smbclient)
smbclient: /usr/lib64/libtdb.so.1: no version information available 
(required by smbclient)
INFO: Current debug levels:
   all: True/11
   tdb: False/0
   printdrivers: False/0
   lanman: False/0
   smb: False/0
   rpc_parse: False/0
   rpc_srv: False/0
   rpc_cli: False/0
   passdb: False/0
   sam: False/0
   auth: False/0
   winbind: False/0
   vfs: False/0
   idmap: False/0
   quota: False/0
   acls: False/0
   locking: False/0
   msdfs: False/0
   dmapi: False/0
   registry: False/0
lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"
doing parameter max protocol = smb2
Processing section "[global]"
doing parameter workgroup = Workgroup
doing parameter server string = Atlas
doing parameter security = share
doing parameter hosts allow = 10.0.0.12 10.0.0.13 10.0.0.19 10.0.0.20
doing parameter load printers = yes
doing parameter log file = /var/log/samba/log.%m
doing parameter syslog = 6
doing parameter max log size = 100
doing parameter interfaces = 10.0.0.2
doing parameter dns proxy = no
pm_process() returned Yes
lp_servicenumber: couldn't find homes
set_server_role: role = ROLE_STANDALONE
Attempting to register new charset UCS-2LE
Registered charset UCS-2LE
Attempting to register new charset UTF-16LE
Registered charset UTF-16LE
Attempting to register new charset UCS-2BE
Registered charset UCS-2BE
Attempting to register new charset UTF-16BE
Registered charset UTF-16BE
Attempting to register new charset UTF8
Registered charset UTF8
Attempting to register new charset UTF-8
Registered charset UTF-8
Attempting to register new charset ASCII
Registered charset ASCII
Attempting to register new charset 646
Registered charset 646
Attempting to register new charset ISO-8859-1
Registered charset ISO-8859-1
Attempting to register new charset UCS2-HEX
Registered charset UCS2-HEX
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
added interface eth0 ip=10.0.0.2 bcast=10.0.0.255 netmask=255.255.255.0
Netbios name list:-
my_netbios_names[0]="ATLAS"
Client started (version 3.5.11).
s3_event: Added timed event "tevent_req_timedout": 0x7fa3a6806990
Connecting to 10.0.0.19 at port 139
s3_event: Added timed event "tevent_req_timedout": 0x7fa3a6806eb0
s3_event: Destroying timer event 0x7fa3a6806eb0 "tevent_req_timedout"
s3_event: Destroying timer event 0x7fa3a6806990 "tevent_req_timedout"
Socket options:
         SO_KEEPALIVE = 0
         SO_REUSEADDR = 0
         SO_BROADCAST = 0
         TCP_NODELAY = 1
         TCP_KEEPCNT = 9
         TCP_KEEPIDLE = 7200
         TCP_KEEPINTVL = 75
         IPTOS_LOWDELAY = 0
         IPTOS_THROUGHPUT = 0
         SO_SNDBUF = 16384
         SO_RCVBUF = 87380
         SO_SNDLOWAT = 1
         SO_RCVLOWAT = 1
         SO_SNDTIMEO = 0
         SO_RCVTIMEO = 0
         TCP_QUICKACK = 1
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
Substituting charset 'UTF-8' for LOCALE
write_socket(4,72)
write_socket(4,72) wrote 72
Sent session request
got smb length of 0
size=0
smb_com=0x0
smb_rcls=0
smb_reh=0
smb_err=0
smb_flg=0
smb_flg2=0
smb_tid=0
smb_pid=0
smb_uid=0
smb_mid=0
smt_wct=0
smb_bcc=0
lang_tdb_init: /usr/lib64/samba/de_DE.utf8.msg: Datei oder Verzeichnis 
nicht gefunden
Type your message, ending it with a Control-D
this is a message test
s3_event: Added timed event "tevent_req_timedout": 0x7fa3a6808fb0
s3_event: Schedule immediate event "tevent_queue_immediate_trigger": 
0x7fa3a67e4cf0
s3_event: Run immediate event "tevent_queue_immediate_trigger": 
0x7fa3a67e4cf0
s3_event: Destroying timer event 0x7fa3a6808fb0 "tevent_req_timedout"
cli_message returned NT_STATUS_PIPE_BROKEN
--------

Sending messages to a Windows XP system works fine. The two Windows 
systems can also send messages to each other.
Regarding Bug 7635 ( https://bugzilla.samba.org/show_bug.cgi?id=7635 ), 
this problem should have been fixed, but I tried 3.5.11, 3.5.12 and 
3.6.3 without success.
Firewalls between the systems are deactivated. All Windows systems are 
patched.

Best regards,
Yann
Comment 1 Björn Jacke 2020-12-19 21:39:54 UTC
the windows messanging service has been disabled ever sinve XP SP2. Similar Messages are now implemented via Remote Desktop Services, see https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc732332(v=ws.11)
Samba will probably not implement this.