About DNS. With your former setup you used an external DNS to resolve DNS
names or URLs to IP addresses. (A URL is a Uniform Resource Locator like
www.microsoft.com). You can't do that with Active Directory. You must use
the local DNS server. To still resolve these outside names you need to set
your local DNS to forward to an external DNS service which can resolve them
for you.
If you are getting APIPA (169.254.x.y) addresses you LAN machines are
failing to get their config from the DHCP server. Looks like you DHCP server
is not configured correctly or is not properly authorised in AD. You don't
need to change anything on the workstations. If they got their config from
DHCP before, they should still be able to (if the DHCP server is active).
"Bill" <(E-Mail Removed)> wrote in message
news:5565E714-CB0F-4F0F-9E9E-(E-Mail Removed)...
> Bill
>
> I did the top part of your instructions and everything works correctly on
> the server. But I got lost in the last paragraph about "foreign" URLs.
> I
> don't know what you mean here. I did "Activate" the DHCP Scope.
>
> I must need this part, because my workstations are not receiving ip's from
> the server's DHCP. They're using the default 169.x.x.x. I have the IP
> and
> DNS set to auto assignments. Do I need to change anything on the
> workstations?
>
> Please help. Thanks.
> --
> Bill Jones
>
>
> "Bill Grant" wrote:
>
>> Turning off DHCP on the router is a good start. Give your server an
>> IP
>> address in the same IP subnet as the router and with the router as its
>> default gateway but its own IP address for DNS. Run dcpromo to install AD
>> and setup DNS. After that is done you can install DHCP and register it
>> with
>> AD. (It won't work until you do that).
>>
>> In DHCP set the scope to some part of the local address range. For
>> example if your router is 192.168.0.1 set it to 192.168.0.11 to
>> 192.168.0.100 . (Give the server one of the low numbers outside this
>> scope,
>> such as 192.168.0.3) . Set the default gateway to 192.168.0.1 and DNS to
>> the
>> server's IP.
>>
>> With AD, all machines including the server itself must use the local
>> DNS
>> server. To allow this DNS to resolve "foreign" URLs as well as local
>> names,
>> set it to forward to a public DNS server (such as the one at your ISP).
>>
>> "Bill" <(E-Mail Removed)> wrote in message
>> news:FCBF3838-67B6-40D2-A3E8-(E-Mail Removed)...
>> > As a follow up on my post....
>> >
>> > I found that I can turn the DHCP Off on the modem router and give it a
>> > fixed
>> > ip address. Now, should I go ahead and install DHCP and DNS on my
>> > server
>> > so I can use AD? If so, how would I set the IP range so that it works
>> > with
>> > the modem and the server and all workstations have internet and server
>> > connections?
>> >
>> > --
>> > Bill Jones
>> >
>> >
>> > "Bill" wrote:
>> >
>> >> Forgive my ignorance, but I have been trying to set up a Win2003
>> >> Server
>> >> with
>> >> up to 3 workstations. I have a ActionTec GT704WG DSL router with 4
>> >> switch
>> >> ports. This router has its own DHCP.
>> >>
>> >> How can I set up the Server IP address so that it will work with the
>> >> router
>> >> DHCP addresses. I've tried several things but, I lose the server or
>> >> I
>> >> lose
>> >> the router. I have SQL Server running on the server too and I lose
>> >> access to
>> >> it.
>> >>
>> >> Lets say my DSL is: 192.168.0.1 - 192.168.0.254 Mask: 255.255.255.0
>> >>
>> >> Please help.... urgent.
>> >> TIA
>> >> --
>> >> Bill Jones
>>
>>
>>
Similar Threads
Linear Mode
