how to use TCP over IP to communicate between the two processes?
469705
Basically you'll need to open a port on each of the two processes, and send a packet between them to communicate.  Generally that will be structured as a sending/"talking" process and a "listening" process to catch the sent packet. In C, you'll need to check the library for the operating system and compiler you're using to find the appropriate functions.  Look under "low level IO", usually.
952871
download "cc proxy"  software by searching in google.install it on on both client.set ip address wich is your server has.this software can also shares a broadband connection which is works on ip address.\nand in a yahoo messenger go to conncetion and also give name of server and ip address to so it can works.u can also us NETOP software to send message on each pc on screen.
523892
you need to run the applications on the PC you consider as server, give it IP address then tell your DNS that this name map to this IP.\n\nopen ports for "others" that the applications will recieve requests through.\n\ntry to connect from one computer to the server.\n\nHave Fun!
828268
You're probably thinking of TCP-IP and wikipedia has an interesting article on its history, and comparisons between the two. http://en.wikipedia.org/wiki/TCPIP  \n(It's far better than me boring you with explanations of models and standards)
814137
go to command prompt..\ntype ipconfig..\nthats all.\nDon't resolve ur ip on net :D
267895
TCP/IP ports are, well, think of them as virtual phone lines that your computer uses to talk to the Internet.  Each port is connected to another computer you are "talking to" on the Internet.  \n\nIf you are using Windows XP you can go to a command prompt by typing cmd.exe in the run dialogue box and typing netstat at the prompt.  It will list all the connections made over the internet to your computer.  If you want to use a graphical interface, try downloading sysinternals TcpView.  \n\nIf you are using a filesharing program like Bittorrent, the port number is configured though the program and I'd consult the help/online documentation to find out how to determine that.
2728
It's really easy, you just have to use the Socket class in the System.Net namespace.\nPlease see a complete sample on the link below.
478422
Try these:\n\nhttp://www.sockets.com/a_e.htm\nhttp://zoo.cs.yale.edu/classes/cs433/lecture/network_programming.ppt
881032
physical data network transmission session ---Application
178746
TCP OPERAThttp://www.dcs.gla.ac.uk/~lewis/networkpages/m07s03TCPoperation.htm
215048
Could always use a remote client such as Tight vnc, its pretty good, works with windows and unix. Just be careful which ports you leave open ;-)\n\nphil\n\nps. its open source
473377
try NOD32, www.eset.com
180663
You could try using a proxy server, or go there directly by IP.
510194
let take a example you are having small network in that  different systems are present.\nif you want to tranfer the files (data) from the remote system to your system or wise versa then following commands\nin the command prompt type ftp 1.1.1.1 (1.1.1.1 is the ip address) then one window is to be opened.\nin that window u find all the sharred folders of the remote system then u copy the respective file and get that file to your system
185556
Networking Tools\n\n    * Ping.exe : The BIG one. This is probably one of the most used tools for TCP/IP. Ping sends ICMP Echo Requests to verify that TCP/IP is configured correctly and that a remote TCP/IP system is available. Ping is very customizable through switches. This should be your first stop during times of networking problems. Using it to test network response time is but one of it's many functions.\n    * Arp.exe : allows you to view and modify the ARP (Address Resolution Protocol) cache on the interface of the local computer to detect invalid entries.\n    * Nslookup.exe : Check records, domain host aliases, domain host services, and operating system information by querying Internet domain name servers. When you start Nslookup, it shows the host name and IP address of the DNS server that is configured for the local system, and then display a command prompt for further queries. If you type a question mark (?), Nslookup shows all available commands. You can exit the program by typing exit. To look up a host's IP address using DNS, type the host name and press Enter. Nslookup defaults to using the DNS server configured for the computer on which it is running, but you can focus it on a different DNS server by typing server (where is the host name of the server you want to use for future lookups). Once another server is specified, anything entered after that point is interpreted as a host name.\n    * Hostname.exe : Displays the hostname of the computer.\n    * Ipconfig.exe : Displays current TCP/IP network configuration values. You can update or release DHCP (Dynamic Host Configuration Protocol) allocated leases, and display register, or flush DNS (Domain Name System) names. Output can be redirected to a file if desired.\n    * Nbtstat.exe : Check the state of current Netbios over TCP/IP connections, update the NETBIOS name cache, and determine the registered names and scope ID. Nbtstat is designed to help troubleshoot NetBIOS name resolution problems. When a network is working ok, NetBIOS over TCP/IP (NetBT) resolves NetBIOS names to IP addresses. It does this through several options for NetBIOS name resolution, including local cache lookup, WINS server query, broadcast, LMHOSTS lookup, Hosts lookup, and DNS server query.\n    * Netstat.exe : Displays protocol statistics and current TCP/IP connections. Very cool utility. Try running it while connected to the net.\n    * Pathping.exe : Trace a path to a remote system and report packet losses at each router along the way. Pathping combines features of Tracert and ping.\n    * Route.exe : Display the IP routing table, and add or delete IP routes.\n    * Tracert: Trace a path to a remote system. This tool gives you the number of hops a packet must make to get there, and the IP address of each hop. It does this for a maximum of 30 hops. This tool is very useful for seeing where a problem with a slow response time may lie.\n    * NetDiag.exe : a diagnostic tool that helps isolate networking and connectivity problems by performing a series of tests to determine the state your network client and whether it is functional. Using the /l switch will output results to netdiag.log as the results can be lengthy. This tool will likely not be installed on your system by default. What you must do is go into your Windows 2000 CD in the support/tools directory. Run the setup file there for full access to the Windows 2000 Support Tools. I had problems with getting this program running due to fatal errors from it, but see how you make out. I'll keeps troubleshooting it to see what I can do. \n\nNon Networking Tools\n\n            /? switch displays options on these utilities as well.\n\n    * Sfc.exe : System File Checker. This utility scans protected system files and replaces files overwritten with the correct system files provided by Microsoft. This could prove to be an invaluable tool for repairing your system after some of those search and replace programs that we all know
1070605
I would suggest "Active Ports" from Smartline. It monitors all port traffic on your PC and allows you to see the originating, and destination IP address for any traffic either coming in, or going out of your computer. Also, you can use a program like "visual route" to track the IP down to its originating hub geographicly speaking
287213
The same way you transfer any kind of UDP packets; dial-up makes no difference.  Usually users are not concerned with the underlying transport mechanisms, TCP or UDP.  UDP packets may be transferred programatically using standard methods.\n\nWhat are you trying to accomplish?