Setting up a server for the first time
- Thread starter Schoieuk
- Start date
Permabanned
- Joined
- 9 Aug 2008
- Posts
- 35,711
I guess that applies to me, do you understand that this sort of environment is not easy? These types of configs don't last forever and require troubleshooting.
Your asking questions that are the basics but not many have replied because they know that it's far too complex for someone just to jump into the deep end with? You need the basics first.
Basically, you have:
Router:
Internal IP - 192.168.0.1
External IP (Static IP/One from ISP): 4.2.2.1
Server:
IP - 192.168.0.2
Now in this example you want to set up a web server, so anyone going to 4.2.2.1 gets to the web server on your server in your house (192.168.0.2).
To do this, on your router, you need to set up port forwarding so that TCP port 80 is forwarded to 192.168.0.2:80 (Port 80 on 192.168.0.2). Your router will then use Network Address Translation/Port Forwarding to pass through the traffic from the outside to the inside while tracking the TCP connection to keep it alive.
HTH.
Router:
Internal IP - 192.168.0.1
External IP (Static IP/One from ISP): 4.2.2.1
Server:
IP - 192.168.0.2
Now in this example you want to set up a web server, so anyone going to 4.2.2.1 gets to the web server on your server in your house (192.168.0.2).
To do this, on your router, you need to set up port forwarding so that TCP port 80 is forwarded to 192.168.0.2:80 (Port 80 on 192.168.0.2). Your router will then use Network Address Translation/Port Forwarding to pass through the traffic from the outside to the inside while tracking the TCP connection to keep it alive.
HTH.
i get all that.. my port forwarding is sorted. I have now set up FTP, HTTPS, HTTP, Remote Desktop, and various other ports for personal application and all are working fine. only thing i need to do now is start on ms exchange. and im half way there. Domain is running and DNS server is working.
Even if you do set-up exchange, it's likely that you won't be able to send to a lot of places, as residential IP ranges are often blacklisted for email.
How are you connecting externally, do you have a static (external) IP, or are you using a dynamic DNS service?
How are you connecting externally, do you have a static (external) IP, or are you using a dynamic DNS service?
I wonder if you can round this though but using a pay-for SMTP relay?
Not really, 2008 sever is childsplay, it will work by following the wizards. It will even attempt to configure your router for you.
i have an external ip address ye, that i bought from my ISP
when you say share data do you mean like hold data on the server and allow access to it to users on the network or whaT?
Is it simply a static IP or is it one meant for this kind of thing, IE not in the residential ranges / on blacklists?
Associate
- Joined
- 11 Aug 2010
- Posts
- 660
- Location
- Cambridge
that's ok bud I have all this to learn 
For anyone else looking to set up their own server, by using the wizards and readig the 'help' wizard that comes with win server 2008 u can learn pretty much everythign thereis to do with the servers roles, functions, configurations etc. But there is a lot to read ^^
To all the folk saying that setting up AD/ Exchange is too complex - WTF? It's an absolute doddle. Anyone who can read, and has the ability to use google on any messages that seem confusing can set up a home domain.
The dude already seems to be doing fine.... complex my arse
The dude already seems to be doing fine.... complex my arse
To all the folk saying that setting up AD/ Exchange is too complex - WTF? It's an absolute doddle. Anyone who can read, and has the ability to use google on any messages that seem confusing can set up a home domain.
The dude already seems to be doing fine.... complex my arse
hehe ye its been a lot easier than i thought but understanding whats going on mabey a little more challenging. Following wizards and googling when u get stuck isnt difficult
