Hello Ace Fekay [MVP],

thanks also from me about the explanation about ICS on a server and the consequences.

Just a small remark, some years ago when i started with networking and domains,
i also used ICS on a Domain controller(multihomed) and have disabled the
ICS-DHCP. So it was no problem to use the internal DHCP/DNS services with
a different scope then 192.168.x.x

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** us YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> In news:39AE14CC-8B22-4851-83A9-3E0E7BCE382D@microsoft.com, JoeBradley
> <JoeBradley@discussions.microsoft.com> typed:
>
>> These are answers:
>> 1. Completed.
>> 2. Still there isn't any AD domain! It will be created later than on
>> s.4-61 (I mean - following the course 70-291).
>> 3. Completed.
>> 4. Completed.
>> 5. Still there isn't any DC! Following the book I created ICS
>> (through
>> dial-up conn.) on Comp1 (Server 2003 R2), DNS suffixes on it and
>> Comp2 (same OS) and I didn't see in previous labs that I MUST use
>> Comp1's IP in his, Comp1, IP-properties as his DNS server! The last
>> lab was wrong as I wrote. OK, then I DID USE Comp1's IP in HIS
>> properties as his DNS server. Lab was wrong too! On Comp2 ALL ALWAYS
>> was OK in his ipconfig results - Comp1 was his DNS server, DHCP
>> server and default router.
>> 6. Yes, elaborate. I think all previous labs was OK because of my
>> elaborate steps. Only small exclusion - earlier I tested new created
>> zones on Comp1. Test was failing until I restarted DNS in Computer
>> Management.
>> 7. Excuse me for my english. :-)
>> P.S. I'll try reinstall OS on both computers and shall NOT install
>> R2, only Server 2003 SP1. May be it will ... If not, I'll send
>> you ipconfig results.
>>
> No problem about your English. You are doing fine.
>
> No problem about no domain as well.
>
> If you are using ICS, a DNS or DHCP server cannot be running on an ICS
> server. This is because the ICS server creates a mini-DHCP service
> that will conflict. The mini-DHCP service has a scope of 192.168.1.2
> to 192.168.1.254 and will randomly hand out address and not in
> sequence from 2 to 254. DNS will conflict as well because ICS will
> 'proxy' (or 'pass') any requests to the external NIC's configured DNS
> server, which you would normally use your ISP's. So if an internal
> client were to get an IP from the ICS server, it will automaticlly get
> the ICS server as the DNS address, so when it will try to register, it
> will automatically send the registration request to your ISP.
>
> This is why you are getting the 11164 and 11165 errors.
>
> Reinstalling will NOT .
>
> To make this work, eliminate ICS. ICS is designed for home users who
> are not familiar with proper configuration. Purchase a cheapo (meaning
> an inexpensive) Cable/DSL router such as a Linksy router ( US $40 or
> so) and use that as your router instead of the server as a NAT device.
> Eliminate or disable one of the NICs on the server. Install DNS and
> DHCP. Only point to itself for DNS. In DHCP, configure a scope and use
> the server's address for DHCP Option 006 (the DNS address).
>
> Ace
>