|
Question : Windows SBS 2003 networking question
|
|
I'm going to try to set this scenario up for you as I am totally stumped...
My company has moved into a new building and I have taken care of all the network wiring. Essentially everything is run over CAT 6 and everything is fully tested from point A to point B, so I know my wiring is good.
I have gotten the T1 installed at the new location and I have moved my server over to the new location as well. Right now my server is acting as a gateway for my network due to my T1 provider providing me with a static IP and not enabling DHCP. This is all fine as I need this for my companies website.
So I come out of the ethernet port on the T1 and into the server. I configured this port to be the WAN on the server. I come out of my second network port and into one of my (3) 24 port gigabit switches, and then I daisy chain from one switch to the next to give them all connectivity. All (48) connections seem to be working fine, I can see the server from the client computers and I can connect to it retrieve files, etc. The server has access to the outside i.e. the internet, however none of the client computers can see past the server. There seems to be a disconnect between the LAN and WAN ports on my server machine. As I said I have configured everything to the best of my knowledge but still the server is the only thing with internet access.
Here is my server network config:
WAN
IP: My public IP Assigned to my by T1 Provider Subnet: Assigned to my by T1 Provider Default Gateway: Assigned to my by T1 Provider
DNS servers: Assigned to my by T1 Provider
LAN:
IP: 192.168.10.1 Subnet: 255.255.255.0 No default gateway entered because the server is serving as the gateway for the rest of the network.
DNS server: 192.168.10.1
Please help, I need to fix this tomorrow!!
Thanks,
- Cary
|
Answer : Windows SBS 2003 networking question
|
|
Yes the router will do everything you want your server to do out of the box and protect your server. A router is your best fastest bet, you configure the router's WAN like you have your server's wan right now, then the router has an internal lan like your internal lan your server has now. The router will have ports you can allow 'IN' to your server you just put in your servers LAN ip or you can make everything available (but I wouldn't- it's unecessary risk) by making it the default host, put it in a DMZ, or virtual server in the router (those are the names they usually mean for redirect all inbout to that machine) BUT that's the good part you only need to open the ports needed web is 80 SMTP (email) is 25 it makes it much more difficult to hack machine if it's firewalled in this manner. Let me know if you need more info.
|
|
|
|