This does not seem to be the result of a migration gone wrong, as your post
says you installed, not migrated. Based on a relatively quick search of
prior posts, I see only migrations with this or similir issues.
My best guess is:
There is a wizard to change the ip address for the NICs in SBS. The first
rule, to quote a fellow MVP, is "Use the wizards". That is also the second
and third rule, btw. <g>
Attend to such items as off loading and drivers
being outdated, then find
and use the wizard. You may want to change it to a different subnet, reboot
and change it back. My preference for SBS 03 is the standard 192.168.16.2,
but that is for the sake of consistancy accross the SBS installs that I manage.
I would disconnect the SBS from the switch before this, and I would change
it back to what it was, but only to keep from confusing the stations with
a new DHCP assigned address and or breaking any of the links you have set.
As always, have a known good, tested backup before making any changes of
Please post the resolution to your
issue so others may benefit
Get Your SBS Health Check at
> I installed a SBS 2003 server just before Christmas with just 6
> clients and
> all seems to be well according to the daily server reports.
> Yesterday I ran the Best Practice Analyser which reported the
> The server running Windows SBS2003 is not the RID Master
> The server running Windows SBS2003 is not the Infrastructure Master
> The server running Windows SBS2003 is not the Domain Naming Master
> The server running Windows SBS2003 is not the Primary Domain Naming
> Even my limited knowledge and experience led me to think that if this
> the case I might have been aware of it before now.
> Nevertheless, I followed KB234790 and established that the server was
> master for those roles.
> Significantly there are other errors which seem to revolve around the
> NIC. I am using one NIC connected to an external router.
> The server has two onboard NIC's and the one I had selected to use
> packed up
> just after Christmas. I disabled it and connected to the other one
> first configured it.
> I suspect I should have made other changes!
> I have noticed that the
> has the wrong ip address and nicdesc name.
> Can I just manually change this key?
> I would be grateful for advice on resolving this
> Chris Curtis