|
You
start reaching the end of my knowledge here, but I know it can't be good that it
says it's the pdc.
You'll
notice that it says there should only be one pdc on the network. Is it possible
that either it was the pdc when it was originally up all of the time or that it
is setup for a different domain? It's possible that you could have powered up 2
pdc's at the same time, the impact of which is way beyond my knowledge. It's
possible that the computers on the network are now looking for it to be the pdc
even though by your statements, there should either be another pdc up or you
shouldn't be on a domain at all. You keep mentioning workgroups, which are
opposite from a domain network, so is it possible that you just run everything
on a workgroup normally without a pdc, and you confused the situation by
powering up a pdc? Are you logging in to all of the computers as a domain user
or a local user with access to the workgroup?
Bruce Dunwiddie
Ticket Technology
P:
866.543.3331
F: 913.451.7832
[EMAIL PROTECTED]
OK but what does that mean exactly that its the
primary domain controller. According to my network diagram it should
have had little impact. In fact that computer sits off most of the time with
no problems.
Adaryl "Did you reboot?" Wakefield
Aviator by passion
Programmer by
sheer force of will
----- Original Message -----
Sent: Tuesday, January 06, 2004 12:41
PM
Subject: RE: [KCFusion] SA help
(OT)
It
sounds to me like that really was your primary domain controller and you
just took it down. Everything happened when you demoted it. I'd suggest
getting it set back up as a pdc and crossing your fingers and finding
another server to back up to.
Bruce Dunwiddie
Ticket Technology
P:
866.543.3331
F: 913.451.7832
[EMAIL PROTECTED]
Ok well here is what I was doing. I was
putting Norton Ghost on the webserver to back it up to a harddrive on the
network. I mapped a drive on the gateway to the server I wanted to back up
to and continued to set up Ghost. Ghost told me that it would not take a
mapped drive that did not use a computer name. I then tried to change the
name of the backup computer and it told me no cause it was a primary
domain controller. Someone else did this work. I figured it was part of
the internal mail system that we no longer use so i ran dcpromo, demoted
the computer and changed the name. I then went back to the webserver
and tried to map a drive using the new name of the back up computer
and it was like no. So then I glare at it for a while with my lip
curled up. I ran around to some other computers and discovered that
I could see the backup computer from other PCs in the office but I
could not see the webserver. On the webserver despite the fact that its
part of the same workgroup as all the other computers the network places
window is empty like its the only computer on the network. Actually the
webserver its self does not even show up. Its all on the same work group
with static IPs and no firewall changes. Oddly enough now we can't
surf the net but we can see our webpage. All gateways and DNSes ping out
fine. I don't know if the network thing and the web thing are related. Its
been a very hair pulling morning and I don't have any hair.
Adaryl "Did you reboot?" Wakefield
Aviator by
passion
Programmer by sheer force of will
----- Original Message -----
Sent: Tuesday, January 06, 2004
11:58 AM
Subject: RE: [KCFusion] SA help
(OT)
I'm not going to claim any form of expertise in these matters, so
I'm just going to list maybe some questions that might spark an idea in
your head as to what might have happened. I know that when a
computer logs on to the network, it has to negotiate the ip from the
dhcp server, but then it has to register itself with the primary dns
server on the network for your dns mapping of machine name to ip to
work. Has your primary dns server failed? You should have a secondary
dns server also, and has it failed? Have new firewalls been installed on
any of the machines affected or any of the primary dns/dhcp servers that
might be blocking the necessary communication between the machines? Is
there a domain involved or is it just a workgroup? Have any of the
network settings been changed recently for either the domain, or any of
the machines? How long has it been since you've noticed these problems?
It normally seems to take maybe 10 - 15 minutes for the dns to register
on the domain just from my experience, and sometimes quite a bit longer.
What has changed recently around the same time as the problems started
happening?
Bruce Dunwiddie
Ticket Technology
P: 866.543.3331
F:
913.451.7832
[EMAIL PROTECTED]
What does it mean when you can find a
computer on the network by IP but not by computer name? I have three
computers all in the same workgroup. A webserver a backup server
and a workstation. I can't see the backup server from the webserver
but I can see the backup server from my workstation. I can see
the backup server from the webserver if I map a drive using
the IP address but not the computer name.
Adaryl "Did you reboot?"
Wakefield
Aviator by passion
Programmer by sheer force of
will
|
