I'm helping out at a school that just had a catastrophe. One of the servers dropped dead -- this thing was being used a proxy server for the internet. It had Microsoft ISA server on it, SurfControl, all kinds of stuff. I don't know why they did that, I would have used a Sonicwall appliance or something, but anyway, what I did, to at least get them back in business so they could read their email, was buy a $90 Linksys cable modem router. It works fine. But there's a quirk.
For reasons I don't know, the domain name on the domain controller is exactly the same as the school's internet domain name (hosted on the outside). So, when you fire up a web browser, and type www.whatever.org
, you can't get to it. And I think its because the name of the domain on the server is whatever.org! If you do a tracert, whatever.org translates to the IP address of the domain controller, not the internet IP address. What do I do to fix that?
Now, I must say, that this did NOT happen when that proxy server was alive. So, there must have been some setting on it somewhere that figured this out. Of course, I never had the opportunity to examine it before it dropped dead.
I plugged the cable modem into the "internet" port on the cable modem router. I plugged the router into one of the ports on one of the network switches. I reserved an IP address for it in DCHP on the domain controller (192.168.124.10) . In the router's settings, I gave it a static IP address of the same. The router is not being used as a DHCP server.
On the client desktops, I set the TCP/IP properties of the nic card to use 192.168.124.10 as the DEFAULT GATEWAY.
Again, it seems to work fine, except for the confusion between the two domain names. I guess I need to know how to tell the network to point whatever.org to outside. I -SURE- don't want to rename the internal domain name to something else, because I really don't want to go around to 250 computers rejoining them to a new domain.
Please tell me what I missed???