"Joe Befumo" <joe@nospam.befumo.com> wrote in message
news:131a4tnk5jlfe81@corp.supernews.com...
> I'm trying to set up a Windows 2003 Active Directory Domain for a client,
> and have run into an impasse.
>
>
>
> They currently run in a peer-peer network, with a Linksys Router providing
> DHCP services, including both IP and DNS links to their external DNS
> provider. We didn't want to switch that over to the new server until we
> were ready to have all of the existing clients join the Domain (i.e., when
> we know it's working properly). (Actually, we tried installing DHCP on the
> server, but it was causing clashes, so we temporarily uninstalled it).
>
>
>
> Okay, the server is set up with Active Directory. In the DNS Settings I
> have it forwarding to the two external DNS servers that the switch
> provides. In TCP/IP settings, I grant the server a fixed IP address (which
> I have exempted on the Linksys Router), and I enter as the single (for
> now) DNS Server, the IP that I assigned to the server itself, i.e., its
> DNS is pointing to itself. (The plan is to create a second backup domain
> controller once the first is up and running properly, at which point I
> will add the second domain controller's address as the second DNS Server,
> and the same on the second server).
>
>
>
> Problem is, it's not seeing anything in the internet, i.e., the DNS is
> screwed up somewhere along the line. IF, I set the server up to get IP and
> DNS from the Linksys DHCP server, everything works fine, but, of course, I
> can't leave it that way if it's going to serve as a server.
>
>
>
> Any ideas? Where else should I be looking for problems? Could it be
> related to the fact that I removed the DHCP services? This has been
> kicking around for a while, so I'd really like to be able to get them up
> and running.
>
>
>
> Thanks,
>
>
>
> Joe
>
>
>
>

"Danny Sanders" <DSanders@NOSPAMciber.com> wrote in message
news:eTQ6535dHHA.596@TK2MSFTNGP06.phx.gbl...
> Do you have the Linksys as the default gateway?
>
> You can forward to the Linksys also.
>
> hth
> DDS
> "Joe Befumo" <joe@nospam.befumo.com> wrote in message
> news:131a4tnk5jlfe81@corp.supernews.com...
>> I'm trying to set up a Windows 2003 Active Directory Domain for a client,
>> and have run into an impasse.
>>
>>
>>
>> They currently run in a peer-peer network, with a Linksys Router
>> providing DHCP services, including both IP and DNS links to their
>> external DNS provider. We didn't want to switch that over to the new
>> server until we were ready to have all of the existing clients join the
>> Domain (i.e., when we know it's working properly). (Actually, we tried
>> installing DHCP on the server, but it was causing clashes, so we
>> temporarily uninstalled it).
>>
>>
>>
>> Okay, the server is set up with Active Directory. In the DNS Settings I
>> have it forwarding to the two external DNS servers that the switch
>> provides. In TCP/IP settings, I grant the server a fixed IP address
>> (which I have exempted on the Linksys Router), and I enter as the single
>> (for now) DNS Server, the IP that I assigned to the server itself, i.e.,
>> its DNS is pointing to itself. (The plan is to create a second backup
>> domain controller once the first is up and running properly, at which
>> point I will add the second domain controller's address as the second DNS
>> Server, and the same on the second server).
>>
>>
>>
>> Problem is, it's not seeing anything in the internet, i.e., the DNS is
>> screwed up somewhere along the line. IF, I set the server up to get IP
>> and DNS from the Linksys DHCP server, everything works fine, but, of
>> course, I can't leave it that way if it's going to serve as a server.
>>
>>
>>
>> Any ideas? Where else should I be looking for problems? Could it be
>> related to the fact that I removed the DHCP services? This has been
>> kicking around for a while, so I'd really like to be able to get them up
>> and running.
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Joe
>>
>>
>>
>>
>
>

"JRB Associates" <i***@jrb-assoc.com> wrote in message
news:OKeWUR6dHHA.4004@TK2MSFTNGP06.phx.gbl...
> Joe,
>
> Like many things, there is more than one answer, depending on what is
> desired/required. If they don't have a fixed IP address and need to host,
> then here is one simple possibility which has worked for me.
>
> Determine what addressing and naming scheme will be used on the internal
> network. Connect to the Linksys router and set it to have a fixed IP
> address internally, and disable the DHCP server. The Linksys router will
> then present itself to the outside as a DHCP client, and get an address
> from the ISP, but internally as a fixed IP address. Then configure the
> Windows 2003 server as both DHCP and DNS servers. Give the 2003 server a
> fixed IP address which is from a reserved pool of fixed IP addresses in
> it's DHCP server. Configure the Linksys router IP address as the Default
> gateway address in 2003 server. Set the addresses of the two outside DNS
> servers to resolve addresses which cannot be resolved by the internal DNS
> server. Leaving out more details, this has worked fine for me for many
> years. It takes the Linksys box out of the process of being in a server
> role, and lets the far more powerful 2003 server fill that role.
>
> John Baker
>
>