In
the confused said:
I think the key is to use the DNS/DC as the DNS on the
DC/DNS machine.
ICS may not know how to send the query back tor the
DNS/DC for looking up local names as it is Internet
oriented.
without setting the forwarder on the DNS may work, if you
are using the default root hints. But you must use the
w98 as the gateway, so it can assist you DNS for
recursion on Internet names. But I would set up the
forwarder just to avoid confusion, making sure the DNS
knows what to do for Internet names.
I agree with you here.
I would probably suggest at this time that Andrew purchase a LInksys or
Netgear DSL.Cable Broadband Router for around $50.00 and eliminate the Win98
machine. This way he'll have a more secure network and it's easier to
configure and administer since ICS is pretty much a set service without too
many configurable options, such as disabling DHCP with that fixed range it
creates 192.168.0.2 thru 192.168.0.254. You can even purchase the Linksys
version with a comprehensive firewall (about $75.00). Really nice unit. This
way you can get away from exposing a Windows machine on the internet and
inviting other issues, such as hackers, etc, besides the configurable
options you need at this time to run your AD/Exchange environment.
ICS is problematic when Active Directory is concerned. If you do purchase
the router, you can opt not to run DHCP on it for your internal machines and
suggest to use your W2k server's DHCP service so it will automatically
update your client information into W2k's DNS.
Dynamic Updates are actually a recommended requirement for Active Directory,
(unless you want to manually enter all the records from the netlogon.dns
file), hence why you do not have the SRV records in your zone (the _tcp,
_udp, _sites, _msdcs folders) which are a REQUIREMENT for AD and Exchange to
function.
Also, the current machine, thenew4850 at 192.168.0.2, should NOT be a DHCP
client, especially if running Active Directory and Exchange, which
apparently is what's going on. Using the ICS machine for DNS is partially
what's happening as well (as you and Kevin have already indicated).
Andrew, if reading this, I would suggest to statically set your DC/Exchange
machine to 192.168.0.2. Use only 192.168.0.2 on all your machines for DNS.
If you would like, I can offer to remote into your machine and fix all this,
but I highly recommend to purchase an inexpensive router as mentioned above.
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory