Server 2003 & newbie help?

[roberteyewhy]

Hello new to the server environment. Installed W2k3 Enterprise on a test machine. Have DNS, Active Directory, Terminal Services, DHCP, and Print Servers set.up Connected to a Linksys router with RoadRunner cable. Router is not DHCP server and all machines have static IP's. DNS pointing to the test machine then ISP. Everyone can see everything I allow and have Internet access. Planning on installing Exchange 2003 and Web Server 2003 later when I better understand the Server environment. Domain name is xxxxx.xxxxx.local. Tiny 5.1 Server Firewall's up and running with me monitoring ALL machines' log's daily as security is primary. eTrust 7 Server Anti virus up and running too. So far, no intrusions, virus's or Trojans. All machines running XP Pro or Server 2003. Will have a secondary Domain server up when I better understand the environment as would like redundancy. Just a home setup with 2 laptops and 3 desktops.

Do I need to purchase a legitimate Domain name? If I take my laptop (Standard Server 2003) to New York, will I be able to login to the Domain with the .local ending and have access to whatever I have allowed? Can someone living anywhere with either Dial-up or DSL/Cable connections become part of my Domain with the .local ending and I will be able to administer those machines when connected? Will Exchange & Web server's work with .local. There has to be a reason why Domain names are purchased. Want to run the home network as a business type environment with OU's and objects therein. Again, why the need to purchase a Registered Domain name? Advantages? Do I need one?

All help appreciated,
Robert

P.S. Another great book Woody (Office 2003). Only book I buy when I upgrade Office.

[jscher2000]

You always can access your network, subject to authentication controls, using the IP address. The domain name simply gets translated to that address anyway. How "static" is your external IP address, and who else needs to contact your server(s)? If the answers are "very" and "almost no one," then I don't see the advantage of a domain name. On the other hand, if it's something you expect to grow into in a couple of years, you might as well start working on it now. It can be difficult to find one that's available.

Added: I suppose I should have said, unless your domain name is registered as part of the domain name system, it cannot be used outside of your network to find you.

Also, with respect to joining other networks to your domain, that's a very complicated issue that probably has a number of approaches, but you could consider whether Active Directory will handle that for you and, if not, whether a VPN could be used.

[roberteyewhy]

Thanks for the reply. Right now you are correct for "very" and "almost no one". But, you are also correct in "if you expect to grow into..." as well. I want to run a "real world" business type situation and not just for the home use. But then I would run into problems as would at the most, have 3 desktops and 2 laptops at home and 1 laptop in New York, so would be limited in the scope of configuration and delegation. Will be building another desktop soon to run the server when testing is done but still will be at home. Upside is at least I start from a small and more manageable topography.

So you are saying that if I do not get a registered domain name and without VPN, my sister in NY would NOT be able to join my domain here in Hawaii through a dial-up connection? If I take my laptop to somewhere that either has hardwired or wireless connections, I would not be able to login to the domain too without a registered domain name and without VPN? Would I be able to run Web Server 2003 with SharePoint Portal Server 2003 and Exchange Server 2003 without a registered domain name? I want to take full advantage of Office Prof 2003 and InfoPath 2003.

As you can see, I want to be able to do it all as have all the legitimate software.

What do you suggest? If I can utilize the above servers without a registered domain name and everything would still work, then will hold off purchasing. For now, I can also wait having my sister join the domain without VPNing. Should I just purchase a Domain Name and "take my chances" with security compromises? If there were no security issues involved, these questions would be moot as I would just purchase a registered name.

Thanks,
Robert

[roberteyewhy]

Any Domain Registration sites that you can recomend that will give me what I desire? What the hey. For $5-$8 might as well go for it.

Thanks,
Robert

[jscher2000]

You do not need a registered domain name to allow others into your network. However, without the domain name, they will need to know and use an IP address. As for how that access would be provided, dial-in (telephone network) connections can be handled without a VPN, as you are on a private connection. If you intend to connect using the Internet (IP network), VPN would be highly advisable. Certainly if you are going to use a wireless connection, you would run a substantial risk by NOT using a VPN. All of these facilities are available in Windows, but configuring them is beyond my knowledge.

I don't know how you would use Exchange with or without a domain name. <img src=/S/grin.gif border=0 alt=grin width=15 height=15>

[roberteyewhy]

Thanks again. Have purchased a Domain Name from GoDaddy. Will need them in the near future. Am trying to get the VPN to work. Got through but could not be authenticated. Server Event log confirms this. Everything else is working and just have to learn to fine tune the Server. I appreciate the input.

Thanks,
Robert