"Z Web Server" schematic uses ZX-24

[zbasicandy]

I would like to inform all ZBasic users hoping to put an embedded web server on the internet using an (A)DSL connection.

Be thoroughly aware of a "dirty dark secret" concerning your ISP and embedded Web Servers. Your ISP might/will change your "outside
IP address" on occasion and even block port 80. This means you will not find your Web Server unlessyou find it through your router information.

Most Web Servers use port 80.
(I was informed that the SitePlayer should work on any port?)
I spent hours talking to my Gateway manufacturer and my ISP. Both will try to avoid helping you because your device is not a PC. Also, the gateway/router manufacturer does not want to lose the ISP business. Here is why. Your ISP does not want you to put a Web Server of any type on his line. They will try to block port 80. Can you imagine if everyone decided to put a Web Server on a DSL line and not pay for it. (It doesn't matter how big or small the Web Server is even though you are not using the Web Server for E commerce) (Actually you are paying for it with your monthly fees) The ISP will steer you towards a "static" or fixed IP address which costs up to five times your residential rate. You ISP will tell you that your gateway/router's "outside IP address" will change occasionally and that's the reason why you need to buy their "upgrade" to a fixed static IP address.

To fix the port 80 problem just configure your router for "port forwarding".

To fix the "outside IP address" changing every day (in may case every week with SBC) just sign up with a "Free" dynamic DNS service provider (www.dyndns.com (free) tzo.com($$$)) and get a domain name for your IP address. Here is the "catch22" you need a utility running on your PC to notify the dynamic "domain" server that your ISP has changed your siteplayer's IP outside address. This prevents from having a totally standalone embedded web server without a PC. The other alternative is to get a fixed IP address which is big bucks $$$$$ or switch to a cable modem which in most cases far more expensive than DSL.

As for DSL users hoping to send email from an embedded devices authentication is the standard now days. Without it, in most cases, it can't be done!

[stevech]

the dynamic IP address - subject to change - is a very well known thing. That's why there are dozens of dynamic DNS service providers. Some are Free. Most anyone with an IP camera at home or a web server uses a dynamic DNS. You can pay your ISP more $$$ to get a static IP address (or several). But most people don't.

Some recent routers can use one of the free dynanmic DNS services. The router tells the service whenever the IP address changes. They update their DNS server. You refer to your router by the symbolic name of your choice.

For an embedded device, you simply set up port-forwarding in your router, e.g., if you have a web server on your lan at 192.168.1.100, you setup your router to forward port 80 to that LAN address. You need to have the device setup for static IP on your LAN, to an address outside the range used by your router's DHCP server.

For another web server, you use a different port. So 192.168.1.101 might be arranged to use port 8080 instead of 80. So the router port-forwards port 8080 to the 101 PC or device. And users would say www.myname.com:8080 with a web browser. Same idea if that device used telnet rather than HTTP.

I have used DNS2GO (D2G.COM) for years. I have an always-on server PC. On that PC, I run a free DNS2GO program that, like the router case I mentioned, tells the DNS service when your IP changes. I prefer D2G.com though it costs $20/yr because they also redirect visitors if your home PC is down, send you email if your PC fails (or like me, the cable modem goes out *again*). Mine is www.childress.d2g.com (login guest/guest). I have several PCs and devices accessable via the Internet - using different port forwards: IP Camera, web server, telnet, FTP, VNC to a couple of other PCs, etc.

[mikep]

I would suggest at this point we are off-topic and should halt any further public discussion. If you have some ZBasic relevant stuff then start another thread.

[stevech]

what's the harm?