Windows Networking

Basically a step by step guide...

If you are like me and have a Windows Server 2003 system, providing lots of services, and do not have a direct connection to the internet, I have the solution... I looked long and hard on Google, but never found anything relevant, so i tried myself, and Lo-and-behold, I found the solution...

So here it is!

My internet connection went like this -

NTL Cable box -> Windows XP SP2 machine with ICS -> Switch -> server

I needed it really to go:

NTL Cable box -> server

So... I installed windows server, set up the services I was to provide (e-mail, terminal services, webcam streaming etc).
NOTE: You must set up a STATIC IP on the server machine!!!
My settings were as follows -
IP - 192.168.0.10
Subnet mask - 255.255.255.0
Default Gateway - 192.168.0.1 (considering my gateway to the internet was the ICS machine)

Primary DNS - Ntl dns server 1 (194.168.4.100)
secondary DNS - Ntl dns server 2 (194.168.8.100)

Restart Server


Now for the steps for the main internet gateway:

Download a program called NetworkActiv AUTAPF (port forwarding software)

Forward all the ports you need to to the server's static IP

For an example

Port 80 / 443 - HTTP/S
Port 3389 - Terminal Services
etc etc

Then away you go... set NetworkActiv AUTAPF to resume all saved port forwarding sessions on startup, and set the main computer to start up NetworkActiv AUTAPF on every startup (C:\Documents and Settings\All Users\Start Menu\Startup)

And then you are sorted!

Appendix -

NetworkActiv AUTAPF

Server 2003 Port Requirements

Windows Server 2003 Port Requirements


Thanks for listening!!

Nick

btw, Hope I helped

 

Hmmm. I think the weakness of the setup is relying on the XP box as the gateway. Personally, I wouldn't want to run a business network via ICS nor put such an vital (for network connectivity) XP box in such an exposed position (directly connected to the internet). At the very least you should install a good personal firewall on that gateway XP box - the SP2 firewall is not good enough IMHO.

Personally I'd replace the XP gateway with a hardware router (preferably one with a proper firewall - that is not just relying on NAT). This will give you a much more reliable and secure solution that would probably be easier to set up.

If you want to stick with using an older PC as the router have a look at smoothwall, a Linux based software firewall solution that will do just what you want to do with a lot of flexibility.

Anyway, hope you appreciate some feedback. Thanks for the link to the port forwarding software, that looks interesting.

 

ReggieB
It would be useful if you could do a step by step of how you would set it up....Please Pleaseeee

 

That's difficult, because each router has it's own set up routine. However, if you want general steps this is a rule of thumb procedure that I tend to follow.

1. Install router and connect one computer (running a personal firewall) to it, but do not connect either the computer or the router to the internet (don't connect it to your DSL or telephone line).
2. From the computer establish a connection to the router (the precise way you do this will depend on the router - check the documentation. However, generally if you look through the router's documentation you should be able to find its default IP address. If you set up the computer to be on the same subnet as the router and then put the router's IP address in a browser window {e.g. http://192.168.0.1} you usually get to the router's configuration pages. If you are unsure of an address to use that will be in the same subnet as the router, you can use this tool to try some options out.)
3. Log in to the router as an administrator - the router's documentation will tell you what user name and password to use to do this.
4. Change the admin password to something different to the default - something you can remember. Include numbers in the password. You may have to log back in with the new password at this point.
5. If you want to use a different network address for the router or a different subnet completely (e.g. 10.0.0.0/255.255.0.0) change the IP address of the router now. If the router then has to reboot don't forget that you will have to change the computer's IP address to match the new router address. If this seems too complicated, leave the IP addressing as default.
6. Go to the DHCP setup page on the router and enable it if you want to use this feature. If you have a proper server on the network (e.g Window NT4, 2000, or 2003 server, Novell, or Linux) I would strongly recommend turning OFF the router's DHCP service and instead using the service on the server. Server OSs tend to have a much better DHCP service - router's DHCP is relatively rudimentry. Set the DHCP service on the server to give out the "route" as the internal address of the router. What you definately do not want is two DHCP services on your network.
   However, if you have a small peer to peer (no server) workgroup, then enable the DHCP service on the router. If you changed the router's IP address in the previous step, you will need to change the DHCP set up so that it gives out IP addresses in the same subnet as your router.
7. Configure the DSL/ADSL/dialup setup on the router using the information provided to you by your ISP. If you have a lack of information try using the routers default settings. Connect the router to the internet connection. The router's configuration pages usually have a status page where you can check that the internet connection is working correctly. Also make sure that NAT is enabled (for most broadband routers it will be by default)
8. Change you computers IP address to get the address automatically. (if win9x reboot.) Check that you can still connect to the router. If not go back to the previous address settings and check the DHCP set up.
9. Once you can connect to the router run a tracert to www.google.com. If this reaches the google server, the router is working correctly.
10. Go back to the router configuration pages and make sure the firewall is enabled. For most users you should leave the firewall as default (which is usally anything out - nothing in). If your ISP is giving you a true SMTP e-mail feed (that is you DO NOT use a POP3 mailbox for your domain) you will need to forward port 25 to your internal mailserver's address.
11. Make sure that you can still connect to the internet from the computer after the firewall has been set up. Browse the internet.
12. Connect the router to the network (or your other computers to the router if this is a small network) and test.