I would like to start aquiring further information on IP and Port number info.
I like to keep it simple, when it comes to learning additional valuable info.
I WILL BE THE SMARTEST MAN ALIVE... JK
I need to know how a given computer can connect to another computer using IP and PORT info...?
I know how to stream video now on the HTTP, using my IP and a PORT number, but I used another program to do it.
But if its really that simple to connect to another persons PC using an IP address and PORT number, whilst only having to type it in the URL Textbox in the WebBrowser of your choice, then why not a PC.
Anyway, I LOVE COMPUTERS and I have been learning for many many years, but I'm still young, so can you just help me out, and point me in the right direction, Please...
Thanx Well let me just say this before its time to choose a best answer.
I used a program called YAWCam, and yes I did connect on another persons PC useing the HTTP, MYIP:ANYPORTNUMBER, thats it, no passcode, no key, LIVE STREAM, but it only lasts for like 5 min, then it stops.
http:\\myIP:PORT, thats it...
And it made me angry that other people can show other people what seems to be really simple stuff, but they still know more than you.
So I guess you could say, the freeware made me very much more anxious, to start learning more about IP and PORT info... as far as it being a learning experiance, towards Networking and PC experience.
Thanx for the answers so far, not bad if I don't say so myself.
Thanx. I've been in your shoes. Keep researching and asking intelligent questions and the lightbulb will eventually come on. It takes persistence, though.
Okay, first of all, there's more involved that just IPs and ports (by the way, and IP + port combination is called a socket). When you start a server program, it starts to "listen" to a particular port (or range of ports) on the machine it's on. So if I'm on my home computer with IP address 192.168.1.2 and start up a web server, it will listen on port 80 (socket 192.168.1.2:80).
Let me break that down with an analogy. You've probably already heard that an IP address is similar to a physical address, like for your house. A port, then, could be likened to the particular person at that address that a piece of mail is for. For example, all the mail goes to the same house at 1234 Main Street, but certain mail goes to different people. The bills go to Dad, the catalogs go to Mom, the magazines go to Junior. What happens if the wrong mail goes to the wrong person? It gets ignored. Dad doesn't care about the magazines or catalogs. Mom doesn't care about the magazines and doesn't pay the bills in this family, etc. The same thing happens when a packet comes to a computer. The socket is analyzed. First, if the IP is wrong, the packet is dropped. If the IP is correct, then the port is checked. Is there a server listening for information directed to that port? If so, then the packet is delivered to that program; if not, the packet is discarded (just like junk mail addressed to "Occupant").
Now that the packet has been delivered, the application reads the information within the packet to determine how to act on it. Imagine that Dad receives a bill for cable TV. Well that's great if Dad has subscribed to cable TV service. He'll write the check and send it back to the cable company. But what if he hasn't subscribed to that service? Dad ignores the bill. The same happens if a server gets a request for information that it doesn't provide. If my web server gets an HTTP GET request, it'll return a web page; but if it receives an SQL query, it'll say "sorry, I have no idea what you want from me," and ignore the request or send an error.
The request also has to be in the correct format. That may mean the correct encapsulation or protocol (or version of the protocol). Back to our family, let's say Junior gets a magazine written in French. Well, that's great if he happens to understand French. If he doesn't, he'll ignore it. If he does, he can process the information.Likewise, if my web server is an older version running HTTP version 1.0 and it receives a request in HTTP version 1.1 format, it may not know how to respond and may generate an error.
I hope that analogy helps you wrap your mind around the concepts. If not, post again and I'll try some more. Well first of all HTTP ( the web ) is through port 80.
So a video that streams would stream via YOURIP:80.
FTP uses ports 20 and 21 to transfer files, but if you were to transfer a file through program methods then it'd be yourip:3200 for example.
Hm? To connect to another person's computer you'd type in
//local/jasonpc
or if it were port forwarded to someone else not in your network:
66.34.55.22:8080:user:pass
etc. into the url box. it's overly complicated. also, firewalls block every port that isn't authorized by the user. turn left my son always |
