Promoting 2003 Server to DC

  • Thread starter Thread starter Dave
  • Start date Start date
D

Dave

When promoting a Windows Server 2003 to DC, if SP1 is installed, the network
connections disappear and I cannot connect to the network OR the internet.
Uninstalling SP1 or demoting to a member server fixes this issue. I can't
find any documentation on this problem. Is there a fix so that I can
install SP1 and keep this machine as a DC?
 
In
Dave said:
When promoting a Windows Server 2003 to DC, if SP1 is installed, the
network connections disappear and I cannot connect to the network OR
the internet. Uninstalling SP1 or demoting to a member server fixes
this issue. I can't find any documentation on this problem. Is
there a fix so that I can install SP1 and keep this machine as a DC?
Click to expand...

Were the default permissions altered on the C:\ drive? There was a hotfix
out that caused issues if that were the case.

Systems that have changed the default Access Control List permissions on the
%windir%\registration directory may experience various problems after you
install the Microsoft Security Bulletin MS05-051 for COM+ and MS DTC
http://support.microsoft.com/kb/909444

Otherwise, not sure, but it would be prudent to know what errors are in the
Event logs.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

If this post is viewed at a non-Microsoft community website, and you were to
respond to it through that community's website, I may not see your reply
unless that website posts replies back to the original Microsoft forum.
Therefore, please direct all replies ONLY to the Microsoft public newsgroup
this thread originated in so all can benefit or ensure the web community
posts it back to the original forum.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations.
=================================
 
Were the default permissions altered on the C:\ drive? There was a hotfix
out that caused issues if that were the case.
Click to expand...

Both of the servers I've had this problem on are fairly new. One is brand
new. It's only been hooked up for about a week now. Anyway, I haven't
changed ANY of the default permissions, except on some shares that I copied
over from another server. Regardless, this problem occurred before those
shares even existed on the new server.
 
In
Dave said:
Both of the servers I've had this problem on are fairly new. One is
brand new. It's only been hooked up for about a week now. Anyway, I
haven't changed ANY of the default permissions, except on some shares
that I copied over from another server. Regardless, this problem
occurred before those shares even existed on the new server.
Click to expand...

The ONLY issue I am aware of where the NIC disappears is due to changing the
C:]windows\* permissions and installing that hotfix. Other than that, it may
be a driver issue? Is there an updated driver for your NIC? What type of NIC
is it?

Ace
 
The ONLY issue I am aware of where the NIC disappears is due to changing
the C:]windows\* permissions and installing that hotfix. Other than that,
it may be a driver issue? Is there an updated driver for your NIC? What
type of NIC is it?
Click to expand...

I've tried multiple NICs. Same thing happens with all of them. The default
permissions have not been changed on the Windows folder. Like I said, this
happens immediately after installing the OS, before any other changes are
made, other than promoting the machine to a DC.
 
In
Dave said:
The ONLY issue I am aware of where the NIC disappears is due to
changing the C:]windows\* permissions and installing that hotfix.
Other than that, it may be a driver issue? Is there an updated
driver for your NIC? What type of NIC is it?
Click to expand...

I've tried multiple NICs. Same thing happens with all of them. The
default permissions have not been changed on the Windows folder. Like I
said, this happens immediately after installing the OS, before
any other changes are made, other than promoting the machine to a DC.
Click to expand...

Can I suggest installing the server with an i386 SP1 integrated source? This
way SP1 is not an 'install' but rather a clean fresh installation all based
on SP1. This will eliminate any issues if it is due to the upgrade or a
corruption in the files, harddrive, or RAM itself, which I've experienced in
the past.

Ace
 
Can I suggest installing the server with an i386 SP1 integrated source?
This way SP1 is not an 'install' but rather a clean fresh installation all
based on SP1. This will eliminate any issues if it is due to the upgrade
or a corruption in the files, harddrive, or RAM itself, which I've
experienced in the past.
Click to expand...

Since this has happened on two different servers, I'm certain it's not a
problem with corruption of files, the hard drive, or RAM. I also tried the
suggestions in the tech bulletin you referred to earlier and that did not
work, either.
 
In
Dave said:
Since this has happened on two different servers, I'm certain it's
not a problem with corruption of files, the hard drive, or RAM. I
also tried the suggestions in the tech bulletin you referred to
earlier and that did not work, either.
Click to expand...

There is more than one server with this problem? Hmm... that is odd. Upto
this point, other than that issue concerning the tech bulletin and MSDTC, I
have never heard SP1 causing this sort of problem and I'm sure if someone
else did see this, they would have posted their thoughts by now.

Did you entertain the suggestion in my previous post just to eliminate two
factors:
1. corrupted i386 source
2. SP1 is not being installed as an update but rather a fresh install.

Ace
 
Did you entertain the suggestion in my previous post just to eliminate two
factors:
1. corrupted i386 source
2. SP1 is not being installed as an update but rather a fresh install.

Ace
Click to expand...

Yes, I checked both of those out. SP1 was already part of a fresh install
with the newest server. The other was updated from the Microsoft web site.
 
In
Dave said:
Yes, I checked both of those out. SP1 was already part of a fresh
install with the newest server. The other was updated from the
Microsoft web site.
Click to expand...

Thank you for clarifying that. I'm not sure where else to go with this,
unless you;ve come up with a resolution. If both machines are having that
problem, it seems that something identical on both is causing it, either the
source of the install (as we just seemed to have eliminated), or some other
common factor, possibly a configuration factor (which we haven't totally
ruled out).

Ace
 
Back
Top