Thanks Bill,
Pretty much what I figured -- I'll go back over it and see if I can find
where I screwed up.
Joe
"Bill Grant" <not.available@online> wrote in message
news:(E-Mail Removed)...
> If you are running a machine as a DC in Active Directory you need to
have
> is set to use a static IP. To access the Internet it should have its
default
> gateway set to the IP address of the gateway router (ie the private IP of
> the Linksys). DNS should be set to the local IP address of the DC. If this
> DNS is set to forward to a public DNS, this should resolve foreign URLs as
> well as local names.
>
> "Joe Befumo" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > I'm (still) helping a local radio station migrate from a peer-peer
> > conglomeration of Win 98, Win 2000, and XP peer-peer situation into
> > Windows
> > 2003 domain with 2 servers and all XP (Professional) clients. With the
> > help
> > of folks from this newsgroup, we've been planning this for several
months,
> > and feel pretty comfortable with where's we're going, but have it a few
> > minor glitches as we prepare to deploy.
> >
> >
> >
> > One server will also function to capture audio for archiving, via FTP to
> > their website. I've got the first server built and configured as an
Active
> > Directory domain server, dns is set up, etc & everything seems to work
> > fine,
> > except, that it can't reach the internet when I have TCP/IP set up with
a
> > fixed address. Right now they're running DHCP on a Linksys router, on
> > which
> > I have exempted the two fixed addresses I'd set aside for the two
servers.
> > The plan is to switch over to letting the Windows 2003 Servers handle
> > DHCP,
> > but for now, we're still on the Linksys. When I tell the running server
to
> > obtain an IP address automatically from DHCP, it accesses the internet
> > fine,
> > so that's how it's running right now. My initial suspicion is that DNS
> > isn't
> > configured properly, but I can't see anything wrong:
> >
> > In the DNS setup I have the forwarding IPs set to the external DNS
servers
> > of the station's internet provider
> >
> > In TCP/IP setup I have entered the fixed IP address of the server
itself.
> > (I
> > 'll add a pointer to the second server as soon as I get it on line.
> >
> >
> >
> > I'm trying to handle the switchover with the least interruption to the
> > running business, so the next step is to upgrade all of the clients to
XP
> > Professional.
> >
> >
> >
> > Then I'll configure the second server as a backup domain controller on
the
> > existing Active Directory forest (correct?). I will set up the DNS the
> > same
> > way as the other machine, with the preferred DNS pointing to my two
> > internal
> > servers, and forwarding in the DNS setup to the external DNS servers.
> >
> >
> >
> > Once I get ready to turn off DHCP on the Linksys, how do I force the
> > workstations to request a new IP, so they're getting it from our
servers?
> > During our initial experiments, we wound up with IP conflicts, so I
> > temporarily removed DHCP from the running server.
> >
> >
> >
> > My immediate problem, however, is getting that first server back to a
> > fixed
> > IP address, while maintaining internet connectivity, since, once again,
it
> > has to be able to FTP archived audio to the station's web site. Any
ideas?
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Joe
> >
> >
> >
>
>
|
Similar Threads
Linear Mode
