Discussion Locked

NT workstation not receive message from

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

NT 4.0, one PDC, Two BDC, Five member server.
3 DHCP(node 1 on PDC, node 2 on Remote BDC, node 3 on Printer server.

Problem: When I send message from server manager on PDC(highlight PDC, then go to send message box), only all member servers got message from PDc. All workstations did not get the message at all.

Appreciate any suggestions. Thanks

Eddie

13 replies

by shmaltz

I assume that the administrator (or someone with that is part of the domain admin group) is sending the messege.
Make sure the messenger service on all the computers are started automaticly.

by dbowlin

When you look at the send message dialog box it says something like "send message to all users connected to." Not everyone on your network is connected to your PDC. Just because they are logged on to the network does not mean they are connected toand using the services of the PDC. In order for a user to be logged onto the network they have to be logged onto either the PDC or one of your BDC's. Try sending a copy of the message to all users connected to each BDC as well as the PDC. That always seems to work for me.

Good luck.

by shanghai sam

Only member server got message. Workstation connected to network did not
receive the same message at all.

by ntoz

If you would like another way to send a message to everyone, use the net send command from a cmd prompt. Your workstations must all be running the messenger service. Look in control panel, services and see if messenger is running on the workstations. If your workstations are Win9x you will have to be running winpop up for them to work, its not setup by default.

net send * This is a test

will send a message to every workstation in the domain running messenger or winpopup.

See Q168893 for more information on this topic.

I have also seen when workstations are setup with more then one protocol, issues like this. Yet another reason not to install every protocol until it works, Im not saying this is your case but Ive seen people install everything under the sun and the binding orders get out of whack. If by chance someone installed all your workstations with Netbeui, TCPIP, IPX/SPX or you need all these services, make sure they are all using the same primary protocol in the binding order, this will fix lots of other issues like long time out's when accessing network resouces.

Pete

by shanghai sam

I tried " net send * This is a test "on PDC, this works only to the workstations connected to DHCP1that install on PDC, pcs connected to DHCP2 and DHCP 3 did not received the same message all. DHCP2 & DHCP3 were installed on two different memberservers under the same domain name, same DNS & WINS, but
these member servers have their own IP addresses.

All workstation installed TCP/IP protocol only and some laptops with PPTP.

How can I send message at once to all users(in different DHCP)?

Thanks a lot

by lintadsl

Try in cmd;
net send domain "hello, this is test"
If all workstations get a messamge, workstations are fine. You need to take a look at the server side. I don't think DHCP servers problem. You can try to send a message to individual such as;
net send sunny-nt "hello" sunnyj-nt is machine name. If you have win9x on client, I don't think you can send a message.

make sure all workstation users are domain users, not guest.(just in case)

Good Luck,
Sunny

by teinfo

net send works and only work on subnet 1 and subnet 2(on remote site), it did not work on subnet3(newly added print server with DHCP)
No win9x on client, all are NT 4.0 and some Appple workstation.
Do I have to check subnet 3 configuration?or something else?

Thanks a lots.

Eddie

by ntoz

I am going to venture one of two things, if your running separate DHCP servers, Im going to first guess you have separate subnets. If this is the case, only workstations on the same subnet, or anything for that matter will get a net send message. This is because its a broadcast and its not forwarded by a router. Even in bridged enviroments, your going to see this filtered in many cases. In this case, you could pass these broadcasts but the problems associated with broadcast forwarding, would not be worth the resolution. Oh one more thing, This would also be true if your running three subnets on the same phyical network

If your not useing multiple subnets and you have three DHCP services running, I dont know why you would have three running as two should be sufficent enough to spilt a range accross for redundancy, your problem might be related to how DHCP is registering the leases with Wins.

by teinfo

Subnet 1 in head office, sunet 2 is on off site office(at other city). We ran out Ip and then added a new print server also runs DCHP(subnet 3).
I conifrmed with the remote site that they did got my net send *this is test message a that ran on cmd. So now I only have problem with the newly added DHCP that did not get my message all.

I don't know why only subnet3 having problem and also I don't why it did not work when I used server manager send message. (only member servers got message, no clients receive message at all)

What you think the problem may be?
Is there any configuration I should check?
Thanks a lots. Your first answer works on Subnet 1&2.

by lintadsl

Then you have a problem with Printer Server(subnet3). Make sure your subnet3 in the smme domain, all users in subnet3 are the domain users. Can you be able to ping one of machine(subnet3) from your machine(I assumed your machine is subnet1)?

by shanghai sam

Hi Sunny,

I can ping a pc at subnet3 from PDC(subnet1). I can also run send message from
subnet3, still could not send from subnet 1 to subnet3.

Any idea?

Thanks

This discussion is closed to new replies.