Re: Replace 2003 server woes

Install went OK, original machine was PDC, new machine went in OK and
replicated AD etc., - Then old servers were shut down, and new server
is now invisible!

I can map network drives using ip address, but the machine doesn't
show up in network by name. Plus all the XP clients went whacko -


AD totally relies on DNS to *find* the AD domain. Sounds like one of the
shut down server was supplying DNS for the domain and you did not move DNS
to the new server. Set the new server's DNS as AD integrated and the DNS
information will replicate to the new server. Then work out a way to switch
your AD clients from using the old DNS server to using the new DNS server.
If you are using DHCP, change it there, if not then you will have to
manually change each server and client machine to use the new DNS server.


hth
DDS

"kj [SBS MVP]" <KevinJ.SBS@xxxxxxxxxxxxxxxxxx> wrote in message
news:uU55ntvTIHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
Rope wrote:
Over Xmas I setup and configured a new HP rack server to replace the
ageing generic PC box running Win2003

Original configuration was one W2003 machine set up as file & print
server, and a second box with 2 lan cards set up with RRAS acting as
VPN server.

New box has 2 NICs and is intended to replace the original 2 boxes.

Install went OK, original machine was PDC, new machine went in OK and
replicated AD etc., - Then old servers were shut down, and new server
is now invisible!

I can map network drives using ip address, but the machine doesn't
show up in network by name. Plus all the XP clients went whacko -
every one behaving differently, a couple would not log onto the
domain, some lost internet connection...

Restated old server (server-01), and it sees the new server
(server-03) but the new server only sees itself - and I cannot seize
FSMO roles from the old server.

Attempted to remove and reinstall AD, and removal failed.

Basically the whole network is held together at present with sticking
plaster and chewing gum.

Any suggestions short of re-building it again from scratch?

Sounds like DNS issues. Install the support tools and run dcdiag /c / v
on each DC.

Post the results.


--
/kj



.

Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... DNS Host Name: tonyb-pc.imageproc.imageproc.com ... Testing IpConfig - pinging the DHCP Server... ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: How to rebuild a single AD... Please Help...
    ... Replicate from IRDC01 and Replciate to IRDC01 ... The kerberos client received a KRB_AP_ERR_MODIFIED error from the server ... I have added a new dc now, made it a gc and dns and have transferred the ... Bot DCs will be used by all machines, make sure that the machines have ...
    (microsoft.public.windows.server.active_directory)