Send popup msg to USER in another domain (PART II)

The question is how can I using net send or any other comman d line utility send message to a given username in another domain. I asked this before , but didn't get a positive answer. See the following thread:

However I still think it should be possible, since I know at least one GUI utility, that allows to view a list of all accessible users and  send popup messages, even if they are in a different domain.400 Points for a positive answer.
Victor SpiridonovAsked:
Who is Participating?
I suspect this all comes down to windows networking using NetBIOS and WINS resolution (As hinted in the first answer).

As previously mentioned, using the /DOMAIN switch will send to the whole domain so if you want to send to a particular user you can't use it. This is because as far as windows is concerned, a DOMAIN is just a specialised form of user - they are just netBIOS names which are registered on the network (OK, it's a touch more complicated, but that's the essence). Generally, sending to a USER on a different domain is unlikely to work because your machine is unlikely to be able to resolve that name to a network address because a) It is not available in the WINS database of your server (Because it won't have authenticated that user or have access to that domain's user list) and b) usually the domain will be in a different subnet so no NetBIOS registration data for that name will have been received by your machine.

There are several possibilities which may make this work:
1. Send to a MACHINE not a USER - this is slightly more likely to work as the list of machines is more likely to be available to your resolver (If you can see the machine in a browse list you should be able to SEND to it).
2. If you have a very simple network with no switches or routers and are using NetBIOS natively (eg not over TCP/IP) there is a possibility that the registration will have been stored by your WINS server (Of course there can be no users in different domains with the same name so the Domain name is irrelevant), but, this should work with the simple 'NET SEND USER MESSAGE' format, so it is unlikely that you can do this.
3. Setup WINS replication from domain to domain will give you full browse lists allowing messages to MACHINE names to be sent - and using trusted servers may give you access to the User information (Not having tried this, I can't be sure).

I suspect the GUI you mention lists all the NetBIOS names that have been stored in the WINS database (Or just those it has seen on the network). I have come across one called NetHail which is similar to WinPopup, but this just uses the browse list (ie Machine names only - no Users) so would not help.
PSS ID Number: Q168893
Article last modified on 05-21-1998

The information in this article applies to:
 - Microsoft Windows NT Workstation versions 3.5, 3.51, and 4.0
 - Microsoft Windows NT Server versions 3.5, 3.51, and 4.0
Using the Messenger Service in Windows NT gives you varying results that
depend on the command options or interface you use to send messages.
The method you use determines whether the message will be a local
Broadcast or a directed datagram, and to which NetBIOS name the message
will be sent.
For additional information, please see the following article in the
Microsoft Knowledge Base:
   ARTICLE-ID: Q163409
   TITLE     : NetBIOS Suffixes (16th Character of the NetBIOS Name)
Sends out a broadcast to all registered users of the local domain <00>
through each protocol on the sending computer. For example, a computer
running Windows NT server with NWLINK, TCP/IP, and NetBEUI would send three
broadcast messages to domain <00>. A user in the domain running all three
protocols would receive three messages.
Sends out a broadcast to the specified domain name <00> through each
protocol on the sending machine. This functions the same as the NET SEND *,
with the exception that you can choose a specific domain, instead of using
your current logon domain.
   NOTE: With NET SEND * and NET SEND /DOMAIN:NAME, only users on the
   local subnet that belong to the specified domain, will receive the
For additional information, please see the following article in the
Microsoft Knowledge Base:
   ARTICLE-ID: 150881
   TITLE     : Local NetBIOS Name Query Broadcast Not Forwarded by Router
Sends a directed message to the <03> NetBIOS entry for the user specified.
The user receives only one message, and the normal methods for detecting
NetBIOS names will be used.
For additional information, please see the following articles in the
Microsoft Knowledge Base:
   ARTICLE-ID: Q119493
   TITLE     : NetBIOS over TCP/IP Name Resolution and WINS
   ARTICLE-ID: Q119490
   TITLE     : How Routers Handle IPX Type 20 NetBIOS Packets
Sends a directed message to the <03> NetBIOS entry for the computer name of
each session established with the server. You can view these connections
through Server Manager. If a computer has three sessions open under Server
Manager, then that computer will receive the message three times.
Send a directed message to the <03> NetBIOS entry for each computer
connected to the server. Unlike the NET SEND /USERS, only one message will
be sent to each connected computer, even if the computer has multiple
sessions with the server.
Keywords          : ntdomain ntdosap ntnetserv NTSrvWkst ntui ntutil
Version           : WinNT:3.5,3.51,4.0
Platform          : winnt
Issue type        : kbinfo
Copyright Microsoft Corporation 1998.


Victor SpiridonovAuthor Commented:
I don't see how it answers my question. give me an examle of sending message to user J D in domain D.
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

net send JD /domain:D "message".
Victor SpiridonovAuthor Commented:
dlansens:Have you tried it?
The syntax you provided sends message : "JD message" to all users in D domain, not message "message" to user JD.

All you need to do is this NET SEND "username" "message"
Thats it!
as long as the messenger service is running on the pc just that user will get the message.
example: NET SEND testuser test
the user testuser will then get a popup box with the message test on it.
If you want to change the domain then its this
net send testuser /DOMAIN test
where as DOMAIN is the domain name.
correction  its /domain:domainname  it will not send to all users unless you add /users.
And yes I have try this.
Victor SpiridonovAuthor Commented:
NET SEND testuser test - message is sent to the user in the current domain. (Anyway what happens , when there are users with the same name in different domains?)

net send user1 /domain:domainname - message is sent to the whole domain. It doesn't matter what I put as user1.

.  /users - sends message to the users connected to the computer, from which I'm sending the message.

Tim HolmanCommented:
NET SEND JD message

/DOMAIN will broadcast a message to the entire domain, no matter what you put in the net send.

This is an old LAN Manager command that never really understood the concept that domains would eventually be joined together...

So you're stuck, unless you're part of the other domain.

I have a gui that I will send to you. Give me email address.
Please send me also the copy of the same,Derosa at
I would really appriciate it if you send it to me too!

Or maybe just tell us the name of that GUI and where can
we download it...
derosa - if you get this, i would also like a copy of the gui you mentioned.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.