Windows 2003 NET SEND?
438520
Simply enable the messenger service by going in control panel > administrative tools > services\n\nthis service is not enable by defualt in windows 2003, when it is in 2000
543023
use NET SEND command. For more information type NET SEND /? on command prompt and hit enter.\n\nNET SEND <name | * | /DOMAIN["name] | /USERS> message\n\nYou may have to enable Messenger service on your and your recepients system before you can send the message (Start -> Run -> services.msc [Enter]).
435840
yes, you can use net send, but make sure that all the computers have messenger service running, some firewalls also block it.\n\nuse:\nnet send [computername/computer IP] your message\n\nor\nnet send * your message \nto send to all computers.
6680
The .NET Framework does not support direct control of USB ports. You'll need a class that wraps the unmanaged WIN32 API to open, control, and close the ports.\n\nHere is some sample code to get you started:
778015
you could try radmin, logmein, gotomypc, \n\nif you are able to access the net properly than these software will work fine with it.\n\nlet me know if you have any further question.
643115
well u can share internet in win server 2003 . well step is below\n\n1) start dns server\n2) start dhcp server\n3) then configure Remote and Route Service in that u  \n   select NAT service\n   but for that u need two NIC (Lan Card)\n\nif u didn't get me then tell me i will explain in detail
1010736
Contact network administrator.
49051
From the point of inbuilt support, Windows offers 2 softwares, namely NetMeeting and Remote Assistance Feature.\n\nNetmeeting : NetMeeting delivers a complete Internet conferencing solution for all Windows users with multi-point data conferencing, text chat, whiteboard, and file transfer, as well as point-to-point audio and video. This white board feature is which you want. You can learn using it at : http://www.microsoft.com/windows/netmeeting/\n\nThe other feature is Remote Assistance(http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/remoteassist/intro.mspx). It lets you stream your screen and its controls with someone else when you need help.\n\nPersonally, I have tried various tools that share your desktop screen and controls. From that point, I would not recommend these 2 utilities, because of following reasons:\n\n1) You need MSN Messenger for using Remote Desktop\n2) Hence, you also need an account at the Passport Network of MSN\n3) You can share screens between 2 users only,\n4) Its pretty resource consuming on systems with lighter configuration\nIf you take my word, try TightVNC (http://www.tightvnc.com/). It is a free remote control software package derived from the popular VNC software. With TightVNC, you can see the desktop of a remote machine and control it with your local mouse and keyboard, just like you would do it sitting in the front of that computer. TightVNC is:\n\n* free, GPL-licensed, with full source code available;\n* useful in remote administration, remote customer support, education, and for many other purposes;\n* cross-platform, available for Windows and Unix, compatible with other VNC software;\n* well maintained and being actively developed.\n\nThere are other like RealVNC (http://www.realvnc.com/), GoToMyPC(https://www.gotomypc.com/) and around a hundred others for the same purpose. But I prefer TightVNC because it is the lightest on resources and most easy to use. I have tried experiments from buffering Video Game screen to streaming your screen on 22 PCs in a chain (not directly). When using other tools, Video games gave a lower FPS( frame per second) as they were consuming more CPU cycles. Also, the time delay in chain screening ( one comp receives and sends its screen to the other comp), was heavy with other tools. Some other services are http://www.logmein.com. Hope this helps you.
353315
Is the receiver on your net work?\n\nIf so, \n\nnet send (ip address goes here) "(message goes here)"\nif you only have one other computer on your network, just do net send * "message\nthe * sends it to all PCs on the network\n\n\nNOTE: If this doesn't work, you might have you messenger turn off. here's how to turn it on:\n1)Access you control panel\n2)Click "administrative tools"\n3)Choose "services"\n4)Scroll down the list until you see "messenger"\n5)Select "Messenger"\n6)From the drop-down menu, choose your start up type as "automatic"\n7)Hit "apply"\n8)On the same tab that the "automatic" feature was located, choose "start" then "apply"\n\nThe end
526625
Check out MSDN on the net
779991
you can use the cpan module \n\nNet::SMTP\n\nit doesn't require special 'sendmail' programs!\n\nor   use MIME::Lite::HTML;\n\nwhich makes it real easy!
369889
Try this link:http://www.microsoft.com/windowsxp/using/networking/setup/default.mspx\n\nhttp://www.xsanity.com/article.php/20050602163711913
807306
windows messenger or maybe even net meeting
331696
Use the VB Connection Wizard!
1099448
Simple Mail Transport Protocol
279064
Easiest way would be to run netstat from a command prompt window.  Just type "netstat" while at a dos screen and it will tell you any and all open data connections at the time.
982411
Try this ....\n\nMS-DOS 6.22\n\nThe DOS program that lets users send data between computers is called INTERLNK (pronounced "interlink"). It's a file transfer program that essentially lets one computer access the hard drive and printing functions of another computer. It won't let computers talk through the Internet using modems, nor will it lets users run DOS-based programs between computers. It's merely a way to transfer data. \n\nYour first move is to make sure INTERLNK is in the Config.sys file. If it's not in the file, place an Interlnk.exe file there by adding a DEVICE= statement. Type edit config.sys at the C> prompt. On one of the lines in the text window that appears, enter device=c:&#92;dos&#92;interlnk.exe. There will probably be other DEVICE= statements in this section so you have some sort of pattern to follow. \n\nAs soon as INTERLNK is installed, the program will begin looking to connect with another computer, one that is running Intersvr.exe, which is server software. (We'll talk about this more in a minute.) If the INTERLNK PC finds a companion, it will display a screen that looks like this:\n\n\nMicrosoft Interlnk Version 1.00\n\n\nPort=Com1\n\nDrive letters redirected: 5 (D: through H:)\n\nPrinter ports redirected: 1 (LPT3:)\n\nThe DEVICE=C:&#92;DOS&#92;Interlnk.exe statement adds one half of the PCs to our two-sided computer linkup. This part of the connection will be the client side, a program that's dependent upon another computer for a major part of its service. This other computer is the server. It will do a majority of the processing between our two computers so make sure that of the two PCs you're connecting, the stronger machine is the server. On this PC, you'll load the server software by typing intersvr at the C> prompt. \n\nYou must reboot both computers before the software will be fully installed. Once the client and server software is loaded, the programs will be looking for each other, usually on communications port 1 (COM1). If you've plugged the serial connector into a ny port other than COM1, type /com2 (or whichever COM port it was) at the end of the client DEVICE= statement. The complete client's DEVICE= statement for the new COM port will read "DEVICE=C:&#92;DOS&#92;Interlink.exe /com2". \n\nOne drawback to INTERLNK software is that the server PC can do nothing while the client has access to it. The server PC merely serves the client-side computer. This means you can't access files or print from the serving computer. On the client side, however, you'll have three new drives: D:, E:, and F:, which correspond to the A:, C:, and D: drives of the server. Access them with normal DOS commands.\n\nNOTE: You will need a PC-to-PC serial cross cable.\n\nPin --- Pin\n1 --- 1\n2 --- 3\n3 --- 2\n4 --- 5\n5 --- 4\n6,8 --- 20\n7 --- 7\n20 --- 6,8\n\nSee here for more info on the cabling:\nhttp://www.arcelect.com/rs232.htm