What this page tries to do:

This page is meant to be a general introduction to 概念s you will need to master to connect an ArduServer, ArduSimpSrv or FarWatch computer to the internet. 打ち勝つing the 詳細（に述べる）s, in practice, is covered どこかよそで.

関係s to the internet- General considerations-

Serve a LAN/ Serve the Internet. See the tutorial I just について言及するd for a more 徹底的な explanation. In a 迅速な nutshell...

If you ask Google to find places to buy an Arduino, you will be using （弁護士の）依頼人 ソフトウェア (your web browser, e.g. Firefox) to 接近 a web server, Google.

Not every server is a web server. To be a web server, something must not only 答える／応じる to requests from （弁護士の）依頼人s, but it must 答える／応じる with data "wrapped up" (formatted) によれば some "extra" 支配するs. Those 支配するs explain why it (hardly) 事柄s which web browser you use.

In your 熟考する／考慮する of servers and （弁護士の）依頼人s, you will 徐々に become used to the fact that when we speak of a server or of a （弁護士の）依頼人, we will いつかs be speaking of 金物類／武器類, and いつかs be speaking of the ソフトウェア which makes the 金物類／武器類 do the serving or be the （弁護士の）依頼人 asking for service.

Servers and （弁護士の）依頼人s have to be connected.

It is perfectly possible to have やめる separate server ソフトウェア and （弁護士の）依頼人 ソフトウェア co-存在するing in a 選び出す／独身 PC. You can have your web browser and a wordprocessor running at the same time, can't you? While they will rarely "talk" to one another, there are （弁護士の）依頼人/ server 状況／情勢s which do arise in a 選び出す／独身 PC. (Not every example of one program "talking" to another is an example of （弁護士の）依頼人/ server 操作／手術, though.)

But it is more usual, when speaking of （弁護士の）依頼人/ server work, that the two pieces of ソフトウェア are in two separate bits of 金物類／武器類. And thus they need connecting. (When the （弁護士の）依頼人 and the server were in one PC, they still needed "connecting", 経由で the operating system. But the "関係" was more abstract, harder to perceive.)

Today, the usual 関係 between （弁護士の）依頼人 and server is TCP/IP, which is more general that "ethernet" or "LAN" or "world wide web". All of those may 井戸／弁護士席 伴う／関わる or carry TCP/IP 関係s, though.

And you can have TCP/IP without having HTML. TCP/IP is a lower level 概念. HTML does usually travel from place to place over TCP/IP links.

On ordinary 地元の area 網状組織s (LANs), we use ethernet or WiFi 科学（工学）技術 to connect 装置s. That is the 金物類／武器類 level 関係. TCP/IP, for most of our 目的s, doesn't care what 金物類／武器類 is 存在 used to connect the 装置s.

Consider a 非，不，無-（弁護士の）依頼人/ server "関係" between two computers: とじ込み／提出する 株ing.

If I have とじ込み／提出するs on "Computer A" 株d with "Computer B", then I can read those とじ込み／提出するs from either machine. If I read them into B from A, the 過程 will probably use TCP/IP. It will make no difference at all to what I do whether the machines are connected with wires or wirelessly.

One of the 広大な／多数の／重要な 創立／基礎 石／投石するs laid 負かす／撃墜する at the 夜明け of all of this was the "IP 演説（する）／住所" (The link will take you to Wikipedia's article, in a new tab or window).

All you need to know for now is that IP 演説（する）／住所s look like...

192.168.0.250

or... not so very different, just another example...

86.25.177.101

IP 演説（する）／住所s consist of numbers between 0 and 255 (inclusive), separated by periods. To date, IP 演説（する）／住所s made up of four such numbers have 一般に 十分であるd. A new "基準" IP 演説（する）／住所 is coming into use. The modern one has six numbers from 0-255 separated by periods.

Not all IP 演説（する）／住所s are created equal. The way the system is 始める，決める up, an IP 演説（する）／住所 starting "192.168.0." will take you to someplace on your LAN... maybe. (If there is no 装置 with the 演説（する）／住所 in question, you will just be told "unreachable", or somesuch.) There are probably millions of 装置s, certainly thousands, "at" 192.168.0.250.... but this isn't a problem, because there is only one such 装置 on any given (working) LAN. (One way to make your LAN buggy is to somehow attach two 装置s both using the same IP (or MAC) 演説（する）／住所.)

The other 演説（する）／住所 given above, will take you to just one place in the whole world. There is only one "86.25.177.101". At the time I wrote this, it was the modem I have 大（公）使館員d to the internet. However, the assignment of my modem to that IP 演説（する）／住所 is not within my 支配（する）／統制する. By the time you read this, my ISP may have given me a different IP 演説（する）／住所, and given 86.25.177.101 to someone else.

持つ／拘留する those IP 演説（する）／住所 thoughts.... we will come 支援する to them.

When you go off to your favorite web page, you don't worry about the IP 演説（する）／住所 for it, do you? You use a URL, aka URI.

It is 構成するd of a domain 指名する, e.g. bbc.co.uk, and an optional path specification, e.g. radio3. (Enter just bbc.co.uk, and the server there will send you the page the 行政官／管理者s at bbc.co.uk have decided to send anyone who queries the server without 明示するing a page. Enter bbc.co.uk/radio3, and the server uses the 構成要素 to the 権利 of the first "/" to guide it in knowing what you 手配中の，お尋ね者 returned.

We are spared having to use IP 演説（する）／住所s because of the DNS... the "Domain 指名する System". Think of it as a telephone 調書をとる／予約する for internet TCP/IP 関係s. If I knew the IP 演説（する）／住所 for the BBC, I could use that, 加える /radio3. But I don't. And for some of the things I want to 接近, the IP 演説（する）／住所 changes from time to time. For my ArduServers and ArduSimpSrvs, the IP 演説（する）／住所 changes. So it is really nice that DNS servers 存在する. As long as 使用者s of URLs keeps the DNS appraised of the 現在の IP 演説（する）／住所s of their services, the DNS can, behind the scenes as far as ordinary 使用者s are 関心d, tell anyone wanting to 接触する a particular service what the 現在の IP 演説（する）／住所 is for that service.

See why I told you not to let IP 演説（する）／住所s out of your mind before now?

Think about it hard enough, and you will see that there can be only one owner... in the world... of the domain 指名する "bbc.co.uk". Happily, you can buy 所有権 of your own domain 指名するs. Even a .com 指名する only costs about $10 per year. I use 1and1.com (and 1and1.co.uk) as my スパイ／執行官 for buying the domain 指名するs I own.

Owning a domain 指名する is a good first step. There's no point in owning it, though, if the DNS doesn't know where to send people who know the domain 指名する, and there's no place to send them unless you own, or rent the use of, a server.

You can connect an ArduServer to the internet. You can connect fancier web servers to the internet. You can rent the use of a web server from many people; I use 1and1.com and 1and1.co.uk.

The IP 演説（する）／住所 of your server will depend on several things. If you are renting the use of a web server, the company you rent from usually takes care of making sure that the DNS always has the 権利 IP 演説（する）／住所 for the pages "at" your URL.

Some people have "static IP 演説（する）／住所s". If you are one of those lucky people, you will know (from your 法案) and will know more than I can tell you.

Most of us do not have static IP 演説（する）／住所s. We have a 関係 to the internet, thought which we send out requests, e.g. a question to Google, and through which we get the answers 支援する.

When you are ready to take the next step, to join the 階級s of Google, and 申し込む／申し出 a server to which （弁護士の）依頼人s can send requests, you start to need to have your IP 演説（する）／住所 known to the DNS.

And there's a really clever answer to this problem. There are さまざまな companies out there willing to help you. I use "Dyn.com" (They used to be called Dyndns.com). And here's how it 作品...

I have an account with them. And, where I have my 器具／備品, one piece of that checks the IP 演説（する）／住所 現在／一般に 配分するd to me by my ISP. If that 演説（する）／住所 has changed since the last check, my 器具／備品 gets in touch with Dyn.com and says "Please tell the DNS that the IP 演説（する）／住所 for Tom's server has changed. It is now at..." Cunning! And it 作品!

That's "it"... almost. I give you help with the 詳細（に述べる）s of Doing It in さまざまな places. I hope that overview will help you understand the 詳細（に述べる）s, as they arises.

There is one general 事柄 which I 港／避難所't 演説（する）／住所d so far.

For the people likely to read this, the 装置 they want to connect as a server on the internet will not be 直接／まっすぐに connected to the internet. It will be on a LAN, with a 地元の 演説（する）／住所 like 192.168.0.250... but there will be other 装置s on the LAN, too. Everything on the LAN will connect to the internet through a router and a modem (often the two are inside a 選び出す／独身 box). When, say, computer "A" asks the internet for Google results for "buy arduino" at almost the same time as computer "B" asks "do I have any email?", the router takes care of sending both requests out の上に the internet, and 大勝するing (hence the 指名する) the separate 返答s to computer "A" and computer "B", as appropriate.

That's all 井戸／弁護士席 and good for things 始めるd within the LAN, because when the answers come 支援する, "inside" the answer is data about who asked the question giving rise to the arriving answer.

However, when a （弁護士の）依頼人 outside your LAN makes a request over the internet, it can't say "send this question to the 装置 on the LAN at 192.168.0.250". Happily, we have "ports" to save the day. A "port" isn't, except in the broadest, figurative, 条件, "ports" in the sense of "USB port", or "serial port". Rather, they are more like a parameter on a subroutine call. When the request for service arrives, it will arrive with a port number. ALL TCP/IP （弁護士の）依頼人 ソフトウェア 含むs a "port to be used" datum with the request for service. ALL of the requests to your domain 指名する arrive at the same place... the "outside" 味方する of your router. When you are just getting started, you may not even notice it, but requests for a web server are ordinarily sent with the "port" setting 始める，決める at 80. And when you 始める，決める up a web server inside your LAN, you 普通は tell the router that requests 耐えるing the "port 80" setting should be sent to the web server 金物類／武器類 which you have 大（公）使館員d at, say, 192.168.0.250. But it isn't 始める，決める in 石／投石する that the （弁護士の）依頼人 should attach "80" as the port number. Nor that your router should only 扱う requests 耐えるing "port=80".

As long as people who want to use your service know what port to 明示する when they send their request for service, one router and LAN can host 多重の services. At the moment, for instance, my router at mon7nc.dyndns.org has a web server on port 80. (That is my FarWatch server... it will tell you about 最近の and 現在の 天候 at a place in southern England.) If you send a request to mon7nc.dyndns.org over port 81, however, you will get a web server running in my first ArduServer. You do that by putting http://mon7nc.dyndns.org:81 into your ordinary web browser, by the way. If you send a TCP/IP request to mon7nc.dyndns.org:5202 with an ordinary web browser, you won't get a sensible result. But if you send a request 示すd for the attention of that port with the （弁護士の）依頼人 ソフトウェア I give away for 解放する／自由な, you will get a sensible answer from the ArduSimpSrv on the same LAN as my web server and my first ArduServer.

A lot to take in, I know. I once didn't understand it, and worked hard to get to where I am now. But I am self taught. It isn't ロケット／急騰する science. All of the pieces have a rather beautiful 簡単. It is just a bit of a challenge to fit it all together in your mind!

その上の reading....

That will, I hope, have taken you 今後 in a 追求（する），探索（する） to connect a server to the internet. For 詳細（に述べる）s and 明確な／細部s of some instances of servers on the internet, I commend to you my ArduServers (平易な... if you are an Arduinophile) , or my FarWatch system (do-able... for 解放する／自由な... if you are a Windows 使用者, and many of the points will help Linux people, too.)

Page 実験（する）d for 同意／服従 with INDUSTRY (not MS-only) 基準s, using the 解放する／自由な, 公然と accessible validator at validator.w3.org. An 早期に 草案 of the page was valid apart from several things inside the code to embed the ビデオ clip of the ocelots.