18 replies
by raphdg
Hey there-
Are your machines on the same workgroup?
Try a net send * and see if it comes through on computerB after that.
by hop228a
Yes, both machine are on the same workgroup(MSHOME). I assume they are as they both can access each others shared folders.
I typed:
net send /domian:mshome computerB testing
Checked both messager service is enabled, and they are.
by hop228a
by rewrite
If it's on your home network you don't need the /domain tag. Do a "net view" to get the names of the computers on your network and then use this syntax:
net sent computer1 "this is a test"
This would send a message to the computer named computer1 and assumes that both pc's have the messenger service enabled and started.
Cheers.
RW
by hop228a
Typed NET VIEW and got the following
Server Name Remark
\\ComputerA Main
\\ComputerB Second
The command completed successfully.
When I type:
net send computerB testing
I get the following error:
An error occurred while sending a message to computerB.
The message alias could not be found on the network.
More help is available by typing NET HELPMSG 2273.
When I type in NET HELPMSG 2273, I get:
An error occurred while sending a message to NET.
The message alias could not be found on the network.
More help is available by typing NET HELPMSG 2273
by hop228a
by rewrite
The messenger service is not running. It has either been disabled or is set to manual. This is not the same as windows messenger. To start the messenger service click on Start->Control Panel->Administrative Tools->Services. Locate the messenger service. If it is disabled then set it to either manual or automatic. In automatic mode it will start when windows starts but beware that this service can be used to send messages from the net to your pc and is a security risk. If set to manual you can then start the service when you want it to run. If set to manual, click on the Start button to start the service. The messenger service will need to be enabled and started on each pc as stated previously.
Cheers.
RW
by hop228a
by statykserver
in addition (once you are sure the service "messenger" is running on both computers) use the net send command with the ip address to test if it is working properly
usage
net send 192.168.0.xxx Message text here
To get the ip address from a command prompt type in ipconfig
Good luck
by hop228a
Tried that and I get the following message:
An error occurred while sending a message to computerB.
The message alias could not be found on the network.
More help is available by typing NET HELPMSG 2273.
Okay, so when I type NET HELPMSG 2273, I get:
The message alias could not be found on the network.
EXPLANATION
This message alias could not be located.
ACTION
Check the spelling of the message alias. If it is correct, then the computer that is to receive your message may be busy. Try sending the message again later.
by rewrite
If you are sure that the messenger service is enabled and running (started) on both pc's then also check for the Terminal Services and make sure that it is enabled and running (started) on both pc's.
Cheers.
RW
by hop228a
by hop228a
by rewrite
OK, let's narrow it down. On each pc, send a message to that pc. Try it by name and by ip address and by the loopback (127.0.0.1). Can each pc send/receive messages to itself? The 2273 message is telling you that either the message is not going out or it is not arriving at one of the pc's. Also,as an afterthought, do either/both pc's have a firewall enabled (don't remember asking this before)? If so, disable it.
Cheers.
RW
by hop228a
Okay, still getting the mentioned error when I tried by name and ip address. I get the same message when I tried the loopback ip.
"An error occurred while sending a message to computerB.
The message alias could not be found on the network.
More help is available by typing NET HELPMSG 2273."
by hop228a
by rewrite
OK, let's review computerB. The messenger service is enabled. You can do a "net view" and see computerA and computerB. Doing a "net send computerB test" from computerB gives you the 2273 error.
Try these steps. If you have a firewall on computerB disable it for the time being. If you have to disable it, try the "net send" command and see if it works. If so, you will need to adjust your firewall to allow the "net" commands through. If it doesn't work then check the netbios settings for the local area network. Go to Start->Control Panel->Network Connections->Local Area Connection. Right click and select Properties. Choose Internet Protocol (TCP/IP) and click the Properties button. On the General tab click the Advanced button. On the WINS tab in the Netbios area choose "Enable Netbios over TCP/IP". OK your way out of all of the dialog property boxes.
Another setting that can stop "net send" messages is TCP/IP" filtering. By default, filtering is not enabled but you can check it by going to Start->Control Panel->Network Connections->Local Area Connection. Right click and select Properties. Choose Internet Protocol (TCP/IP) and click the Properties button. On the General tab click the Advanced button. Go to the Options tab, select TCP/IP filtering and click the Properties button. If the "Enable TCP/IP filtering" checkbox is checked make sure that no filtering is done for port 135 in the TCP or UDP boxes.
When changing any of the settings mentioned wait about 30 seconds before trying the "net send" command. Sometimes there can be a lag before the command takes effect.
Post back with your results. Once you get computerB to "net send" a message to itself then try a message to computerA and vice versa.
Cheers.
RW
by hop228a
This discussion is closed to new replies.
Trending Software posts
Sort by Trending