Net Send Computer Message Command



Hello:

I run Seti@Home on several computers all joined into a LAN. I have
written several programs that make sure Seit@Home is running on the remote
computers and use the Net Send Computer Message command to the machine I
normally work on so if there is a problem I can fix it w/o wasting days of
electricity doing nothing. It has worked well for several years.

Recently I read an article about NetMeter, a little program to measure
network traffic over an interface or all interfaces. I run the Gomez Peer,
Dimes, and Seti@Home and know I use a lot of bandwidth, but I never was able
to measure how much. NetMeter would let me measure that. But to separate
WAN from LAN traffic, I needed two NICs. I installed a second NIC in each
computer, so that 192.168.0.X has a gateway and therefore accepts all
traffic destined for the WAN, and 192.168.1.X accepts all traffic destined
for the LAN. That part is working; I used Wireshark to confirm that all
Internet traffic goes over the 0.X interface and all LAN traffic goes over
the 1.X interface.

Two other features suddenly disappeared though. I can't send messages
using Net Send Computer Message and no computers show up under my workgroup
in Windows Explorer. Both of these are a real pain in the neck. Naturally,
if Seti@Home fails on one of the remote computers, I don't hear about it, I
can't even use Net Send to send a mesage to my own, primary computer, the
one I am typing this message on. The error is:

An error occurred while sending a message to Comp.

The message alias could not be found on the network.

More help is available by typing NET HELPMSG 2273.


If I type "Net Send * Message", I get

An error occurred while sending a message to WORKGROUP*.

System error 64 has occurred.

The specified network name is no longer available.

I get the same error when typing "Net Send /domain Message" or "Net Send
/domain:Name Message."


I am running Server 2003 on one computer and so could make that computer a
Primary Domain Controller and install Active Directory, but I don't want to
do it unless it will solve my problems. BTW, the Messenger Service is
running.


Does anyone know how to get Net Send to work and/or the computers on the LAN
to show up in Windows Explorer?

Thank you in advnace for any help you might provide.

Charles Elliott


.



Relevant Pages

  • Re: Installing multiple SBS VPN clients
    ... please check the Local area network routing only. ... reachable from the remote access server. ... Check to ensure the SBS Server is using a static IP address on its LAN ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN connection works, lan access fails
    ... The extra IP you see is indeed the internal interface. ... first remote user connects, the internal interface acquires an IP address. ... > from the PPTP daemon virtual IP to the physical. ... From the inside LAN I can ping the SBS static IP, ...
    (microsoft.public.win2000.ras_routing)
  • Re: How Can I Allow Access From The Internet to Only Selected Users?
    ... big the lan is. ... for some users on my network for years. ... When the systems box opens,click the tab that says remote. ... "select remote users" and enter in th administrators group. ...
    (microsoft.public.windows.terminal_services)
  • Re: Windows 2003 disabling/blocking public IP?
    ... private interface (LAN), no NAT, no basic firewall ... public interface (connected to the Internet through a Cable ... to DISABLE/ENABLE the Network connection on NIC 2 and this seemed to ...
    (microsoft.public.windows.server.networking)
  • Re: Remote Desktop Connection - Client could not connect...
    ... To test from a PC on your LAN to another PC on your LAN you can *NOT* use the public IP, ... To call from the remote site use the public IP of the router, ... well for me when I call my home network using Remote Desktop. ... >>> Remote Connection might not be... ...
    (microsoft.public.windowsxp.work_remotely)