similar to: smbclient -M to windows 7 workstation problem

Hi. First, sorry by my bad english :) I had a samba 3.0 and use a script with smbclient to send messages to 30 computers in my laboratory. I upgrade to debian squeeze and samba 3.5 and now i dont use the script command. root at escort:~# echo "Testando" | smbclient -NM LAB5-01 -I 192.168.3.200 Type your message, ending it with a Control-D cli_message returned NT_STATUS_PIPE_BROKEN I

My customer has a Centos Linux 5.10 server running Samba 3. (Samba version 3.0.33-3.40.el5_10) The machine is about three years old. I suggested that they should consider replacing it with a Centos 6 machine and Samba 4, but they decided as it was doing its job without any issues to keep it as is. I also suggested updating to samba3x but they decided not to do this. I recently installed a centos

Time skew........ <kicks self> > -----Original Message----- > From: samba-bounces+allen=gist.net.au@lists.samba.org [mailto:samba- > bounces+allen=gist.net.au@lists.samba.org] On Behalf Of Allen Bolderoff > Sent: Thursday, 20 October 2005 12:22 PM > To: samba@lists.samba.org > Subject: [Samba] Can auth with smbclient, but not workstation. > > We have a setup (that

Greetings all, I'm trying to connect to the default shares Windows NT workstation enables for "administration" purposes but I'm not having any luck. smbclient can see the shares: [esisler@shaun esisler]$ smbclient -L ghost added interface ip=198.243.2.206 bcast=198.243.2.255 nmask=255.255.255.0 Got a positive name query response from 198.243.2.200 ( 198.243.2.150 ) Password:

Greetings list, I just upgraded to samba 3.6.0 trying SMB2. Though Windows 2008 R2 can work with SMB2 shares just fine, I'm unable to access SMB2 shares with mount.cifs or smbclient, even with "-m smb2" specified -- I get this "Unrecognised protocol level smb2", whereas smbclient comes with samba-client-3.6.0-63.1.rpm. So is this supported yet (from client side) or I

I'm trying to do the winpopup emulation thing to an IP address instead of NetBIOS name. The following don't seem to work: smbclient -I 172.16.0.43 -M smbclient -M -I 172.16.0.43 The bottom one tries to interpret -I as the host name. What's up?... and don't say my head!!!! ;-) Thanks in advance, sorry if it's been asked before -Vickers

Has anyone modified smbclient to send winpopup-style message broadcasts to Win95 workgroups/WinNT domains? If not, any tips on how I could go about doing it? What section of the SMB RFCs (1001, 1002, 1003) would be likely to talk about it? (I'm not sufficiently versed in low-level SMB, so most of the RFCs are still Greek to me. So if someone kindly points me in the right direction I think

Hello, Is there a way to broadcast a message with smbclient -M? Also, is there some utility out there with user interface where I can select which machines should receive the message and then send it out? Thanks, Tomas

Hi Folks! I try to send a popup via "smbclient -M" from a sun (SunOS 5.8, Samba 2.0.7, hostname "sonne") to a WinXP (hostname "dezntmneubeck_x") but it fails. Both machines are in the same physical network. All I get are the following lines: root@sonne(1017)/> smbclient -s /usr/local/samba/lib/smb.conf -M dezntmneubeck_x added interface ip=193.102.105.71

Hi All, When I try to do "cat message.txt | smbclient -M <machinename>" or "smbclient -M <machinename>", I get: added interface ip=192.168.0.100 bcast=192.168.0.255 nmask=255.255.255.0 <snip all other interfaces; about 25 more> Got a positive name query response from 192.168.0.12 ( 192.168.0.12 ) session request failed What does "session request

I've gotten smb-wall to work with Samba v3. If there's a better way, please let me know. If not, what's the chances this could be included in a future release? #!/usr/bin/perl # #@(#) smb-wall.pl Description: #@(#) A perl script which allows you to announce whatever you choose to #@(#) every PC client currently connected to a Samba Server... #@(#) ...using "smbclient -M"

Hello, I've been trying to get the smbclient -M to work but I'm running into some troubles. I want from a Linux box to display one of those popups, I can get a few command to work fine which is where my issue is: The windows machine I'm trying to send it to is 10.10.10.168 (or ENGS1004 NetBIOS name). When I do: smbclient -U fling%password -L ENGS1004.switchnet.nv

Hello *, I've fileserver with Debian Lenny and Samba 3.2.5 from the distro. I want the server to notify clients on some events with a popup. # smbclient -M Client01 Connection to Client01 failed. Error NT_STATUS_BAD_NETWORK_NAME but: # smbclient -L Client01 -U myuser Enter myuser's password: Domain=[MYDOMAIN] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Sharename Type

Hi I use messages (net send...., smbclient -M ....) to let a server dial to my provider, or to let him fetch my mial. This worked until I switched to 1.9.18p3. My server is named FGP, my group FGP_GROUP. One of the nt-clients is named SAUSCHNELL - and one of the users on SAUSCHNELL is names fgp - like the server. Since I use 1.9.18p3 all the messages sent to FGP from a NT-computer are actually

Greetings- We use smbclient -M to send a Message of the Day to clients every once in a while. The clients are NT4 (SP3), and the server is Samba 1.9.19-prealpha. However, the same problem appears with version 2.0.0. The issue is: once the file to be sent exceeds approximately 675 bytes (smbclient reports sending 975 bytes, presumably including some overhead), the message turns up blank on the

Peter: Thanks! It now works fine on Solaris 2.6. Now I just need to remember how to manipulate source RPMs so I can fix the Linux (RedHat 6.x) version. :-) pete > From peter@cadcamlab.org Sun Jul 16 16:41:17 2000 > Cc: <samba@samba.org> > Subject: [PATCH] `smbclient -M' ignores `-p port' > > [Pete Peterson <petersonp@genrad.com>] > > It appears

I have a script that is attempting to notify a user that a job has finished however, when called from within the script nothing is received by the user. ----- cut from script ----- #!/usr/bin/sh : : MESSAGE="$WINNAME, your job $_3GJOB\nhas successfully completed" echo "$MESSAGE" | /path/to/smbclient -M trout > /dev/null 2>&1 echo

Hi, I've been a Samba user/admin for about a decade with relative success, but now I'm stumped. I'm hoping someone might be a solution to this, or at least a solid answer. I'm looking to send out winpopup messages to our XP clients when one of our Samba fileshare servers needs to be rebooted. So I'm trying to sending the messages from a Linux/Samba server, which is not a

We have a setup (that has worked since samba 3 was released), where we have a windows 2000 ADC, and a debian sarge based (running all current patches and only Debian packages (nothing related to samba/winbind is compiled by us) samba 3.0.xx server set up with winbind/pam to act as a domain member serving files, whilst authenticating from our Windows ADC. - so what happens is... Ctrl-alt-del,

Hello everybody, I am trying to keep my samba pdc working with windows 7 pro clients. After my upgrade: 2016-12-15 15:10:16 upgrade samba:amd64 2:3.6.6-6+deb7u7 2:3.6.6-6+deb7u10 Some of the Windows 7 client can not login anymore and respond with: The trust relationship between this workstation and the primary domain failed Changing the setting client use spnego = no will make the Windows