A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Networking and the Internet with Windows XP
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Net Send issues



 
 
Thread Tools Display Modes
  #1  
Old January 10th 04, 01:17 AM
BHO
external usenet poster
 
Posts: n/a
Default Net Send issues

We're trying to figure out how to use net send to send a
message to all used on the network. According to the
directions I've found, we should simply need to type:
net send * "message"

Howeverm whenever I do this I get a "system error 123
occured". Is this due to the name of the network having
a space in it? If so is ther a workaround, and if not do
you have any idea what the issue cold be? I can use net
send to individual users, just not the entire network.
Ads
  #2  
Old January 10th 04, 01:17 AM
Paul Russell
external usenet poster
 
Posts: n/a
Default Net Send issues

If your in a domain, it will work in the global method you outlined. if
your in a workgroup or have multiple workgroups it won't work as expected.
There are alternatives but it depends on your needs.



--

Paul.


"BHO" wrote in message
...
We're trying to figure out how to use net send to send a
message to all used on the network. According to the
directions I've found, we should simply need to type:
net send * "message"

Howeverm whenever I do this I get a "system error 123
occured". Is this due to the name of the network having
a space in it? If so is ther a workaround, and if not do
you have any idea what the issue cold be? I can use net
send to individual users, just not the entire network.



  #3  
Old January 10th 04, 01:17 AM
Steve Winograd [MVP]
external usenet poster
 
Posts: n/a
Default Net Send issues

In article , "BHO"
wrote:
We're trying to figure out how to use net send to send a
message to all used on the network. According to the
directions I've found, we should simply need to type:
net send * "message"

Howeverm whenever I do this I get a "system error 123
occured". Is this due to the name of the network having
a space in it? If so is ther a workaround, and if not do
you have any idea what the issue cold be? I can use net
send to individual users, just not the entire network.


Yes, I think that the problem is that your workgroup name contains a
space. When I use the workgroup name "MSHOME", the command that you
listed works fine. When I use the workgroup name "MS HOME", the same
command fails, with this error message:

An error occurred while sending a message to MS HOME*.
System error 123 has occurred.
The filename, directory name, or volume label syntax is incorrect.

Then only workaround that I know of is to use a workgroup name with no
spaces.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
  #4  
Old January 10th 04, 01:17 AM
Steve Winograd [MVP]
external usenet poster
 
Posts: n/a
Default Net Send issues

In article , "Steve
Winograd [MVP]" wrote:
In article , "BHO"
wrote:
We're trying to figure out how to use net send to send a
message to all used on the network. According to the
directions I've found, we should simply need to type:
net send * "message"

Howeverm whenever I do this I get a "system error 123
occured". Is this due to the name of the network having
a space in it? If so is ther a workaround, and if not do
you have any idea what the issue cold be? I can use net
send to individual users, just not the entire network.


Yes, I think that the problem is that your workgroup name contains a
space. When I use the workgroup name "MSHOME", the command that you
listed works fine. When I use the workgroup name "MS HOME", the same
command fails, with this error message:

An error occurred while sending a message to MS HOME*.
System error 123 has occurred.
The filename, directory name, or volume label syntax is incorrect.

Then only workaround that I know of is to use a workgroup name with no
spaces.


Here's an alternative: the RealPopup program can send messages to all
users in a workgroup, even if the workgroup name contains spaces. Get
the program he

http://www.realpopup.it

To send a message to a workgroup, click the network icon in the "Send
message" window and browse to the workgroup.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
  #5  
Old January 10th 04, 01:18 AM
James Arrow
external usenet poster
 
Posts: n/a
Default Net Send issues

you can use Original software
LanTalk XP
http://www.cezeo.com/products/lantalk-xp/

"BHO" wrote in message ...
We're trying to figure out how to use net send to send a
message to all used on the network. According to the
directions I've found, we should simply need to type:
net send * "message"

Howeverm whenever I do this I get a "system error 123
occured". Is this due to the name of the network having
a space in it? If so is ther a workaround, and if not do
you have any idea what the issue cold be? I can use net
send to individual users, just not the entire network.

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 03:55 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.