similar to: Winpopup Broadcast? (smbclient -M to workgroup)?

Hey, Happy New Year. I've searched the web for a while and can't get an answer to a question: I can send a message (using WinPopUp, net send, or smbclient -NM) to Windows and Linux PC's. But, when I send a message to the whole workgroup "net send /domain Hello" Only the Windows PC's respond to it (with the Windows message service). Samba does not see it. My question

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

Hi, I have a linux (redhat 6.0) print server and I am running samba 2.0.3-8 serving win95 machines. I would like the print server to send a message to the win95 when a print job is completed. To do that, I run winpopup on win95. However, if win95 users close winpopup, they do not receive any message. Is there any more realiable method to communicate with win95 machines? I would appreciate any

Before I start I should say that I will pay $2000US to get the information or code I seek. I need code or protocol specs to be able to send winpopup messages. It cannot be done via mail slots because it has to work over the internet at large. If you type in "net send x.x.x.x hello" on any windows nt or xp machines it will send a winpopup using UDP ports 137 and then 135 (also 1031 and

I want to use smbclient -M to send new mail notification to unix users. I have some of our workstations running smbd from inetd and am using the "message command" option quite successfully. What I was wondering is, has someone implemented the winpopup reception end in a form that would be more efficient than using full blown smbd? Am I making myself clear? Perhaps if someone could

Can Samba be used to generated WinPopUp RPC calls on TCP port 135? I am familiar with using the "smbclient -M" command to send messages using the Win Popup protocol, otherwise known as Windows Messenger Service, or what a Microsoft user does from a DOS prompt as a "net send" command. WinPopup can be generated either via Microsoft file sharing protocols, using the

Hi! I updated my Samba from 2.0.7 to 2.2.2. Now the command "smbclient -M <username>" doesn't work anymore. Even <username>#3 doesn't work (where nmblookup finds the correct IP). I know that you have to give a hostname, but I will send messages to users whereever they're logged on. Any hints? Thanx! Jan

Listers, Is the a way to tell SMBCLIENT to broadcast to the entire workgroup instead of having to send to all the individual clients? I've tried smbclient -M workgroup and it failed to resolve anything (which was expected). What Im ultimately wanting to do is set up the proper line in the PPP script to alert the users when the line status changes. Can this be done without to much trouble?

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

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"

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

Just wondering if there is a way to send a WinPopup message to a user (using username). I have had a look at smbclient but it appears to only allow sending messages to a computer name. Thanks in advance, Russell Kliese

Hello i am sending winpopup messages throught (smbclient -M) and it seem to work fine but i dont recieve anything at my w98 machines. For example, i do: ---------------------- jorge@tagoror:~> smbclient -M ALFA added interface ip=192.201.11.67 bcast=192.201.11.255 nmask=255.255.255.0 added interface ip=192.201.11.1 bcast=192.201.11.255 nmask=255.255.255.0 Got a positive name query response

Greetings- Perhaps slightly OT, but still involving the SMB/CIFS protocol: I am searching for an application which would allow a Linux client (Ubuntu) to send/receive WinPopup messages. The only one I have located thus far is LinPopup. However, it depends on the Samba (server) package. I do not want to deploy a bazillion Samba servers! TIA! -- Michael Lueck Lueck Data Systems

Hi there. how do I send a winpopup message to a machine knowing its IP only? I tryed witch 'smbclient -M ' but I need the netbios for that machine... -- Enrique Iglesias Rodriguez System Administrator http://www.intelideas.net Madrid, Spain -- CtrInt

OK, yesterday I was asked abut moving an existing Python program from an NT machine to a Unix machine. This involves sending a message to winpopup. So, after some digging I found smbclient's -M option. Well, it works fine when I send it to a machine that is not part of the site domain. When I send it to a machine that is logged in to the domain, I get "session request invalid". Any

Hello All, Does anyone know how one could send the same Winpopup message to all Win-clients on a network? I need it for building a fail-over system, in case our primary server goes down, I need a way to automate the process of informing all clients that they need to log-off the network, wait a few minutes and then log back on, while the back-up server switches a few configuration files and

Hi all, I have network with few win 95/xp machines and suse 9.3 prof server. On every win client is installed RealPopup (RealPopup homepage: www.realpopup.it). I can send popup message from my xp computer to win 95, and I can get reply on new message addressed from win 95 computer, so looks like popup communication works well. If I use: server:~ # echo "test" | smbclient -M bane

Dear SAMBA gurus, I browsed the list archives but found nothing relevant about this big (IMHO) problem. Only just another problem like mine, unfortunately unanswerd :(. I have here samba-2.0.3 on a Linux box, libc5, manually compiled without problems. All is well EXCEPT WinPopUp messages, I can send them OK but I cannot receive. As receiver I set LinPopUp but I don't think that is ever

Is "smbclient -M" supposed to work to a Windows 7 machine? Using samba3-3.4.9-42.el5 I get: # echo "Hello world" | smbclient -NM PC167 Connection to PC167 failed. Error NT_STATUS_BAD_NETWORK_NAME The name resolves correctly, and the command works to an XP client with Messenger service enabled. Win 7 has its own "MSG.EXE" program for that sort of thing, which