1 Server as both PDC and Exchange Server

By the way, does my internal domain need to match the domain name we'll be using for the rest of the world? Say we have buggerz.com registered, and our mail would be sent to user@buggerz.com. Can my domain name be Buggernet or should I change the PDC and all workstations over to buggerz.com?

The 206.x.x.x needs to be on the internet side of the DSL router. Anything being sent to that address on TCP port 25 should be NATted to the internal IP address of your Exchange server. You will require a MX record in you ISP's (or someones) DNS server that directs mail to your domain to the 206.x.x.x address. You do not need 2 NICs. You will also need to configure the Internet Mail Service (IMS) on the Microsoft Exchange Server. I don't know what hardware you have doing the NAT so I can't helpthere, but I would be willing to give you some direction as to getting the IMS up and running on the Exchange server once you get the NAT and DNS stuff set up.

The problem you have right now is a routing problem. The NAT box (whatever it is) translates your static IP address to an internal network address so your internal network will never see it and shouldn't have to. Your exchange server will actuallypoint to the gateway address on your NAT box rather than to your real-world IP address.

If your NAT device also does firewalling, you have some port work to do as well (open SMTP, etc).

The internal domain name and external domain name do not have to be the same and probably shouldn't be. Whoever hosts your DNS will create an MX record associating your domain with your external IP address and the Exchange server will take it from there and deliver it to people's mailboxes.

If you're not hosting your own DNS, you'll also have to tell the Exchange server where to find the DNS server so it can resolve outgoing addresses.

Hope this helps get you started in the right direction.

paul

Answer one covers it pretty good. Mail will have to be directed to the IP address and you router will have to direct that to the exchange server. You may need to check the specs on you router to see if it supports this.
On the domain name you willnot have to change your internal domain name. You set exchange to the public domain name separate from the nt domain you have specified.

Most of the answers so far are doing a good job of answering your question, but I would take issue with the suggestion of using only one network card.

It's true that it's not necessary based on having multiple IP addresses bound to one board, but I look at that statement and I'm reminded of the published minimum hardware requirements for Windows NT Server: 486, 14 MB RAM, etc. In other words, it's technically possible to use only one NIC, but, in my opinion, not at all good practice.

Your instinct to go with two NICS is right on. Do NOT enable IP forwarding (which would create the same effect as using only one NIC). This will help you avoid some security holes.

The ISP providing the DSL service is also supplying the NAT box, and they claim that all I have to do is give my server the proper IP address, and away I go. However, when I set my server to the 206.xxx.xxx.xxx, then my LAN (10.x.x.x) can't see it.

Furthermore, the ISP rep claims that the their stuff is configured so that they can then get the necessary data to the 206.xxx.xxx.xxx even if it's on the "inside."

I appreciate the additional and useful information but I'm not sure I'm grasping the whole picture. If your ISP is NATing your static IP to your internal network, it's not clear to me why you need to enter your outside IP address rather than the gateway address for their router.

But if what they're telling you is correct, adding a second NIC pointed to the 206.xxx address would probably be the best approach.

regards!

paul

This question was closed by the author