emumaster
asked on
SBS 2003 R2 setup and DHCP and Internet questions !
I currently have 4 pc's connected to the internet (atlantic broadband) into a wireless router and sharing the internet with the router providing the DHCP for the internet and workgroup.
I just bought a dell server with SBS 2003 R2. It has 2 ethernet ports.
The purpose of the server is for in-house email and public calendering with outlook 2003.
I also purchased 2 Dell's Firebox's to hook up this office and our other office in a different city and to make a VPN between the offices. The firebox has an easy WYSIWYG setup(claimed by a dell tech)
Now for my questions:
How do I handle DHCP for communicating to the internet and to establish the connection between all pc's? Is it thru the server ?
Do I need to setup Active Directory?
I want each computer to still get the internet connection. Does the internet go to the dell server and then shared to each pc?
Obviously I've never setup SBS 2003, so I am open to any advice to help me accomplish these goals.
Do I run the cable modem line into the
I just bought a dell server with SBS 2003 R2. It has 2 ethernet ports.
The purpose of the server is for in-house email and public calendering with outlook 2003.
I also purchased 2 Dell's Firebox's to hook up this office and our other office in a different city and to make a VPN between the offices. The firebox has an easy WYSIWYG setup(claimed by a dell tech)
Now for my questions:
How do I handle DHCP for communicating to the internet and to establish the connection between all pc's? Is it thru the server ?
Do I need to setup Active Directory?
I want each computer to still get the internet connection. Does the internet go to the dell server and then shared to each pc?
Obviously I've never setup SBS 2003, so I am open to any advice to help me accomplish these goals.
Do I run the cable modem line into the
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You can keep the setup (more or less) the way it is now.
- Give your server a static IP outside that DHCP range like .2 or .254
- Only connect one of it's Ethernet ports (you've already got a router, no need to add another).
- I would use AD, and create a domain.
- I'd advise you to run DNS on your server as well.
- Change the DNS address given through the DHCP to your server
I can't really go into more detail than that otherwise i'd be typing an essay, AD and DNS are reasonably easy to setup, if you look there'll be some nice HOW-TO's somewhere on the net.
Good Luck!
- Give your server a static IP outside that DHCP range like .2 or .254
- Only connect one of it's Ethernet ports (you've already got a router, no need to add another).
- I would use AD, and create a domain.
- I'd advise you to run DNS on your server as well.
- Change the DNS address given through the DHCP to your server
I can't really go into more detail than that otherwise i'd be typing an essay, AD and DNS are reasonably easy to setup, if you look there'll be some nice HOW-TO's somewhere on the net.
Good Luck!
ASKER
Let me ask about Jerry the Great's comment about SBS wanting to be THE mail server.
What's your opinion about making it the email server for pop and in-house?
Is it better having the individual machines get their email via pop3 as they are doing now and then setup outlook to get the in-house email from the server?
What's your opinion about making it the email server for pop and in-house?
Is it better having the individual machines get their email via pop3 as they are doing now and then setup outlook to get the in-house email from the server?
The main benefit of doing it through a local Mail server is that:
- You have a single point of administration
- Spam / AV filters can be easily implemented
- Automatic backups
- The ability to create Distribution groups
- You have a single point of administration
- Spam / AV filters can be easily implemented
- Automatic backups
- The ability to create Distribution groups
If you try to setup Exchange without Exchange being THE mail server, you could end up having mail delivery problems for users on Exchange. There are ways to do it, but they are not advisable because they increase your management requirements.
Using Exchange to store mail allows for FAR easier backups and when implemented properly, easy access via portable phones, web, and office systems.
But again, you clearly aren't familiar with this - and if you are not intending to LEARN it - DEEPLY LEARN IT, you are ASKING for trouble. Could it be setup without professional help - yes... just like you COULD rebuild a car engine without a mechanic's help... but the odds of doing it right go up dramatically when you get professional help.
Using Exchange to store mail allows for FAR easier backups and when implemented properly, easy access via portable phones, web, and office systems.
But again, you clearly aren't familiar with this - and if you are not intending to LEARN it - DEEPLY LEARN IT, you are ASKING for trouble. Could it be setup without professional help - yes... just like you COULD rebuild a car engine without a mechanic's help... but the odds of doing it right go up dramatically when you get professional help.
emumaster:
To personally respond to your question about making SBS THE main server, there are 2 things you would need to do to set it up this way.
1. Either get a static IP for your internet (if you don't already) or ask your email provider if they can be a smarthost for your email service.
2. Modify your company's DNS MX records to ensure email is delivered to the right place (either your static IP, or you ISP's.)
The reason for making SBS THE mail server is that Outlook really wants to send email through Exchange if it is present, regardless of the user's email settings. this is what I alluded to, and the other experts reinforced. You can research and see there are always other ways, but this is the most stable way.
PS to reinforce another comment above, ALWAYS use the wizards with SBS--it is a customized server build, and settings outside the wizards have weird manifestations--don't be smarter than the computer-- swallow your pride and use the wizards--"connect to the internet" being the most common one for most changes.
good luck!
To personally respond to your question about making SBS THE main server, there are 2 things you would need to do to set it up this way.
1. Either get a static IP for your internet (if you don't already) or ask your email provider if they can be a smarthost for your email service.
2. Modify your company's DNS MX records to ensure email is delivered to the right place (either your static IP, or you ISP's.)
The reason for making SBS THE mail server is that Outlook really wants to send email through Exchange if it is present, regardless of the user's email settings. this is what I alluded to, and the other experts reinforced. You can research and see there are always other ways, but this is the most stable way.
PS to reinforce another comment above, ALWAYS use the wizards with SBS--it is a customized server build, and settings outside the wizards have weird manifestations--don't be smarter than the computer-- swallow your pride and use the wizards--"connect to the internet" being the most common one for most changes.
good luck!
If you don't, you run the SERIOUS RISK of costing yourself MORE in the long run. SBS is an easy to manage, VERY STABLE system... when it's setup PROPERLY. And someone who JUST knows Windows server is NOT QUALIFIED to setup SBS properly (I know - I was such a person and I screwed up my first install severely).
Yes, You NEED to setup Active Directory - if you don't you are violating licensing and it's probable that the server will reboot itself hourly after a 1-3 week grace period.
I will say, If you ARE intending to LEARN this so you can do it for other people - and you SERIOUSLY want to understand it, then get some books and set things up MULTIPLE times - even if you think you got it right, wipe and reinstall at least twice - LEARN how to set it up and ALWAYS use the wizards.