NetSuporte wrote:
Robert, I also used the free service of DynDNS the model I have is ( network everywhere ) LynkSys cable/DSL router Model Number:NR041 This is on the DDNS configuration screen inside the router:DDNS (Dynamic DNS) allows assigning a domain name to a dynamic WAN IP address,making it easier to host Web, FTP, or other servers. The Dynamic DNS service is powered by TZO.com.To use the Dynamic DNS Services, please sign up for a free 30 day trial <http://www.tzo.com/MainPageDownload/30days_free.html>To order the TZO service, click here <http://www.tzo.com/order.html>To manage your domain name and related services: Controlpanel.tzo.com <http://Controlpanel.tzo.com>TZO Password Key: -philip Robert Zagarello wrote:NetSuporte, I use a D-Link DI-624 that doesn't complain. Who wants to charge you? I did not use DynDNS's subscription $$$, only their free service. It means you have to use one of their domain names. I'd like to know the Linksys model you are using so I can tell people to avoid it ! Thanks. BZAG ================================= --- NetSuporte <netsuporte@xxxxxxxxxxxxxx> wrote:Thanks Robert Right off I ran into a snag my Lynksys router insists I use TZO.COM and they charge a fee after 30 days. That really sucks as I discovered this after signing on with DYNDNS.ORGWhere they assigned me a domain of homelinux.com A redirected host name of quecaixa.webhop.net withthe redirected URL of www.quecaixa.com.br:8222 cloaked - yes cloak = www.quecaixa.com.br Not sure what the cloaked stuff is about exactly but with or with out I still cannot get to my server outside my own net. So I will try to enable DMZ and see if it helps. Philip Robert Zagarello wrote:Here are some guidelines for running a private web server on your home network for internetaccessibility. I think I've included everything. This is actually what I am using myself (am runningNetBSD) and it is working: 1. Use Dynamic DNS and a 3rd party DDNS service provider like dyndns.org. There should be an entryfor DDNS in your home cable/DSL router for this.Youdon't need an internet registered domain and DNS address - the DDNS service will do it. You don'tneeda static IP address from your ISP for your router. 2. Install and run the SSH daemon for remote admintoyour web server. 3. On remote Windows PCs use PuTTY and PuTTY'scommandline utilities for up/downloading files from yourwebserver. 4. On your cable/DSL home router put an entry fortheremote IP addresses in your firewall, specifyingthehost and SSH ports, and route them to your webserver.5. Put an entry in your router's firewall for the router itself, as in the previous step, to test internet accessibility from your home network. Ifyouput an entry for your web server's host name in ahomenetwork PC's hosts file, you will access the web server without going out to the internet. If youusethe web server's FQDN (full host plus domain name, fully qualified domain name), your home PC will actually request name translation from your ISP'sDNS,which is your router, and then direct your requesttoyour router's WAN side port, effectively testingforinternet accessibility. 6. In your web server's host file put your DDNS address and FQDN (full host plus domain name, fully qualified domain name) you got from your DDNSserviceprovider. Don't put in the web server's privateLANaddress. Note the IP address may change becauseyouare using DDNS - but it doesn't change thatfrequently- so you may want to run a script that checks it daily. 7. You may want to put a simple non-dotted up-to-15-character name for your ISP's DNS to test name resolution from your web server when you have problems using nslookup for example (you have to specify the server using nslookup because the web server is on your home network). 8. You can also put a simple non-dotted up-to-15-character name (say, just the host nameonlyof the FQDN) for the web server in your home PC's hosts file to permit local testing of your webserver.9. In rc.conf (I am running NetBSD) on the web server, put in the DDNS FQDN as the hostname and similarly its domain part for the domainname. There are entries above for the IP address that are made manually so these have to be checkedperiodicallyif changed by your broadband ISP. (This does not include the DDNS entry in the router which willupdateyour DDNS service entry automatically). BZAG =======================================---------------------------------------------------------------------The official User-To-User support forum of theApache HTTP Server Project.See <URL:http://httpd.apache.org/userslist.html>for more info.To unsubscribe, e-mail:users-unsubscribe@xxxxxxxxxxxxxxxx" from the digest:users-digest-unsubscribe@xxxxxxxxxxxxxxxxFor additional commands, e-mail:users-help@xxxxxxxxxxxxxxxx---------------------------------------------------------------------The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx---------------------------------------------------------------------The official User-To-User support forum of the Apache HTTP Server Project.See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx---------------------------------------------------------------------The official User-To-User support forum of the Apache HTTP Server Project.See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
--------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx