Question Locked

Windows Server 2003, Exchange Server 2003, 2-Wire 2700 HG, static IP, help.

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Noob alert.

I built a single "server" computer for my small business which is actually a powerful and redundant desktop tower.

The software put me a little over budget and we cant buy more hardware for now. I have:

Server with single Gigabit NIC
2-wire DSL Modem w/ built-in: 802.11g, 4 port
switch
Network printer
Static IP from Qwest
8 clients running XP Pro, 2 clients running
Vista Home Premium, all wireless
Windows Server 2003
Exchange Server 2003

My clients need the following services:

File service
Printing
Email
VPN

The server and printer are connected to the 2-wire's switch/hub.

I've done LOTS of reading and this is my first time doing this. Here's what I've done so far:

Configured 2-wire with DHCP enabled + static IP
Internet access to all clients and server
Printing service to all xp pro clients
File service to all XP pro clients

I have yet to enable/install the following because I'm frustrated and confused about what to do next:

Active Directory
Exchange Server
DHCP server
DNS
VPN

And the vista clients take forever to see any network files or printers besides each others.

Any advice would help. Thanks for your valuable time.

4 replies

by churdoo

LOL! High-to-mid level view here ...

In order,
AD and DNS Simultaneously
Next DHCP
Join XP/Vista clients to the Directory
Then you can do Exchange and/or VPN in either order

We'll take the LAN first, and then Exchange and VPN later. Let me start by saying that Active Directory and DNS go hand in hand. DCPROMO your server and run through the wizard. When you do this, the wizard should ask you if you want it to configure DNS, go ahead and allow this -- it's important that DNS for all of your clients be handled by your AD controller. Furthermore, install and configure DHCP on your server and disable DHCP on your 2-wire appliance. In the DHCP Server Options or Scope Options, configure the Router option with the correct default gateway IP, and configure DNS server with your AD Controller's IP.

Next you can create users in AD and have your XP and Vista clients join the directory. Note: since you've already configured File and Print services on the clients prior to AD, you'll have to modify them after implementing AD; you'll also lose the local profiles of any customizations that users have done at the clients before implementing AD. The profiles can be copied if this is significant.

Lastly, I have to say for the record -- sounds like you spent a ton of time on this, and have more time to spend. The right IT consultant could have done this whole project for you in a matter of hours, leaving the time that you're spending, available for you to focus on your own new business. The consultant probably would have also warned you about the performance of running all of your clients via wireless, not to mention the security concerns. If you have network performance issues once you get all of your desired functionality, you can budget in having a cabling guy pull copper throughout your office and a reasonable switch.

Good luck and post back when you need to

by newperson

I'm returning to my office tomorrow, and I'll then follow your advice with this project. I understand what you have told me thus far (especially about hiring a consultant, but I must say this has been fun), however I have a couple further questions pertaing to our current email hosting with Network Solutions:

According to Network Solutions (our domain registrar and email hoster), once I get my email/exchange server up, I need to call them to enable "DNS forwarding" to my static IP address through qwest. I want to keep the same domain name for our email addresses. Is this really possible? It doesn't sound too complicated, is it?

Also, I'm using WPA on the wireless router along with MAC address filtering (I had to input, individually, the MAC address of each client that is allowed to connect to the router). So far I'm not having congestion issues, but I'm wondering if this is still insecure or not secure enough. Any thoughts?

Thanks again!

by churdoo

No that email scenario isn't complicated, in fact it's quite easy. I'm not sure why Netsol is calling it "DNS Forwarding"; I think that's just their admin panel way of saying it's an A record for your static IP and an MX record to point your email there, cuz that's really all it is.

Again, this is high-level, and when you're ready to dig into the weeds, there are other things to talk about, not so much for inbound email delivery cuz inbound is quite simple (don't let me forget about Exchange IMF), but for the outbound delivery, there are t's to cross and i's to dot so your emails don't get stopped as suspect SPAM by recipient mail servers. If your Qwest package let's you forward your outbound SMTP through them (in fact they may REQUIRE it), then that's the way to go.

As you implement Active Directory and Exchange, you'll tend to have a lot more chatter on your network, and this may or may not begin to choke your 54mbps WAP on the 2-wire appliance.

So taking wireless security out of the equation for just a moment, 802.11g/n(draft) are at best 54mbps solutions, and the Access Point if I'm not mistaken, where all of that traffic funnels through, basically acts with respect to throughput, like a 54mb HUB, a single 54mb piece of pipe, versus a copper switch which gives you 100mb or even 1000mb (gigabit) bandwidth at EACH individual switchport. Your lappies came with wireless and copper both built in probably, but your desktops probably only had the copper built in, gigabit, so you had to spend money to downgrade their bandwidth to 54mb.

Reliability -- switches have been around so long, they're braindead simple and ironclad reliable, at least until the lightening storm comes through (get business grade gear, doesn't have to be cadillac top of the line, but buy from a computer outlet and not from your office supply store where you get your post-its and paper clips, ugh!, and remember the addage "you get what you pay for"). The wireless is still a relatively new technology and is also prone to interference and other issues ... I can go on longer, and I STILL haven't talked about SECURITY!

So at least consider the upgrade path, to have someone pull Cat5e to all of your desktops and network printers. Rule of thumb in my area is $150/jack location to have a professional installer do it. Let the lappies roam via the wireless, after all, what's a laptop for? And yes, keep the WPA and MAC filtering in place.

Oh sure! You're doing everything else yourself, so you probably want to pull the copper yourself, I mean a 1000-foot spool of non-plenum Cat5e for less than 50 bucks, and crimpers and punch-down tools, but it will look like crap, and you don't want your office looking that way; the pro will run in the walls wherever possible and install wallplates and jacks and a patch panel, and with the professional install, the patch panel and wall jacks will be reliable as heck.

OK enough. Sorry to babble, and I'm putting away my inflatable soapbox. :-)
--C

This discussion is closed to new replies.