Dominiczek wrote:I have Linksys Router WRTU54G-TM, and Comcast ISP - which is a bitch, because they did not let me get static ip, even additional IP, even additional account.
I've had Comcast in the past and ran my own personal web server from it. . . you really don't need a static IP with them because as long as you have your computer on and connected, it's almost never that they change your IP. ( I think mine may have changed every 3 months or so if even that). Normally it would only change in the event of a power outage that lasted for a good while.
Dominiczek wrote: So I have Dyndns Updater, for now I have a free domain name just for testing, if I will get it to work, I am going to buy a couple of dyndns domainnames, for my dream websites. I forwarded the ports listed below. Do I need to do the triggering port stuff? DNZ is enabled. DHCP is enabled. Firewalled is disabled in the router. dyndns.org is set up in the router, because it's got the option for it.
I highly recommend looking into Zoneedit.com. You can set up to 5 zones (domain names) free of charge and I've had nothing but a great experience with them.
As far as your router configuration goes, all you need to do is set up port forwarding and make sure you're sending it to your server's IP.
Everything else you can probably leave "as is". I wouldn't recommend disabling the firewall in your router because that helps protect you. I've got a tutorial on port forwarding here:http://www.myownserver.info/home/step-4-additonal-settings/8-port-forwarding.html
Dominiczek wrote:If I don't have static ip, and I have Comcast should I set my TCP/IP in Local area connections to static or what or I should leave to obtain automatically?
Don't change anything on your pc. You'll only cause yourself headaches.
Dominiczek wrote:Looks like that dyndns is working properly. Is there any way I can check if it works properly?
I am using appache 2.0 as a server. I added there ports; 80, 8080, 443, even 21, 22, 23, 25. The IP is the same as my ISP's. The domain name is dominiczek.mine.nu - again just for testing for the start.
In the host file in my windows my ip is set up to the same as my ISP and domain name.
dyndns will work correctly as long as you have it pointed to the correct IP. Do note it will take up to 24 hours for it to update to your IP, but usually it's more like 30 minutes to 1-2 hours. The same is true for any DNS services.
As far as the ports go, I wouldn't open any that you don't ABSOLUTELY need. The FTP protocol is a very insecure one, which is why you'd open 21, so I'd be very careful on that one. using a VPN (such as Hamachi) for your FTP server is by far the best solution in my opinion for still having remote access.
There's a tutorial on my website on how to do that as well, just search for Hamachi.
If you're just connecting to it over your LAN, leave the port closed in your router configuration and just connect straight to your server via the server's local IP, which will be something like 192.168.1.123. Ports are not blocked over LAN networks in most cases unless you're using a router above a consumer home-use model, so there's no need to open them just for local access.
The only port you really should need open is 80 and ONLY if you are using SSL will you need 443, which in most cases you won't be using it.
I highly recommend you not modifying your hosts file, especially if you don't know what you're doing. This won't help your server run or be publicly accessible. Instead, you're probably causing yourself more problems.
Dominiczek wrote:I have Windows XP Professional Service Pack 3
I forwarded the ports in Windows Firewall.
I have windows Defender
I have Kasperky Antivirus, free one - which is the best - I totally recomend it.
I'm not sure if Kasperky has a firewall or not, but you will need to add the exceptions to it as well. Normally your firewall programs will prompt you when you start Apache, letting you know that it is blocking it and allowing you to allow it as an exception.
Windows Firewall sucks. I'm not sure of a good free firewall by itself, but Comodo makes a free internet security package that has both an AV and Firewall combined and it's a pretty decent firewall.
When you've got open ports on your network, a good firewall is essential for protecting yourself against hacker attacks.
It can be a bit confusing at first, but once you get it figured out, you'll be hosting your own website(s) for the world to see. Security is always an issue, so the more research you do to take preventative measures, the better. The biggest thing I can't stress enough is MAKE BACKUPS! It's easy to get lazy, but if your server does get hacked, the only way to recover is from backups and if they're outdated, you end up loosing valuable information you can't get back. Don't start hosting sites for others either. Each person you allow access to your server is a potential thief with keys to your house. It's not a good idea no matter how "cool" they seem online.
I've tried to structure my site in a step-by-step way for doing just what you're trying to do, so if you want, go take a look and see how far you get. If for some reason you run into a problem, just let me know and I'll help ya and update whatever information is wrong or not clear.