9 replies
by fossil
Can't answer directly about winpopup, but as a workaround you can use the messenger service via the NET SEND command. The output of
NET HELP SEND is (sorry for the formatting):
---------------------------
NET SEND {name | * | /DOMAIN[:name] | /USERS} message
Sends messages to other users, computers, or messaging names
on the network. The Messenger service must be running to receive messages.
You can send a message only to an name that is active on the network.
If the message is sent to a username, that user must be logged on
and running the Messenger service to receive the message.
name Is the username, computername, or messaging name
to send the message to. If the name is a computername that contains blank characters,
enclose the alias in quotation marks (" ").
* Sends the message to all the names in your group.
/DOMAIN[:name] Sends the message to all the names in the
workstation domain. If name is specified, the
message is sent to all the names in the specified
domain or workgroup.
/USERS Sends the message to all users connected to
the server.
message Is text to be sent as a message.
NET HELP command | MORE displays Help one screen at a time.
-------------------------------
I've used it to send messages over 100 characters long. Try sending one to yourself to test it. Hope this helps until you get you initial problem fixed.
by winnythevaz
Hi,
These error messages can occur when you send WinPopup messages to an invalid or inaccessible computer name, or when you send to a computer with the same name as the sender's user name (whether or not it is also a valid computer name on the network).
see the MS KB Article ID: Q173494 for the full explination.
regards,
by winnythevaz
Your not doing anthing wrong.
It is a limitation set by the protocol used to send the messages.
Rgds
Jm
by winnythevaz
by tlippert
by winnythevaz
by winnythevaz
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending