Windows Vista Forums

SBS 2003 Best Practice Analyser reports problems but nothing in event viewer

  1. #1


    Chris curtis Guest

    SBS 2003 Best Practice Analyser reports problems but nothing in event viewer

    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 following:

    The server running Windows SBS2003 is not the Schema Master
    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 Master

    Even my limited knowledge and experience led me to think that if this was
    the case I might have been aware of it before now.
    Nevertheless, I followed KB234790 and established that the server was the
    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 having
    first configured it.
    I suspect I should have made other changes!
    I have noticed that the
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Win2kCfg\values
    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



      My System SpecsSystem Spec

  2.   


  3. #2


    Merv Porter [SBS-MVP] Guest

    Re: SBS 2003 Best Practice Analyser reports problems but nothing in event viewer

    Try re-running CEICW and then select the correct NIC and complete the rest
    of CEICW. Then run the SBS 2003 BPA again.

    --
    Merv Porter [SBS-MVP]
    ============================

    "Chris curtis" <nospamatmitredotnet> wrote in message
    news:eI$0MudlKHA.4408@newsgroup

    > 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 following:
    >
    > The server running Windows SBS2003 is not the Schema Master
    > 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 Master
    >
    > Even my limited knowledge and experience led me to think that if this was
    > the case I might have been aware of it before now.
    > Nevertheless, I followed KB234790 and established that the server was the
    > 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
    > having first configured it.
    > I suspect I should have made other changes!
    > I have noticed that the
    > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Win2kCfg\values
    > 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
    >
    >

      My System SpecsSystem Spec

  4. #3


    Larry Struckmeyer[SBS-MVP] Guest

    Re: SBS 2003 Best Practice Analyser reports problems but nothing in event viewer

    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
    this magnitude.


    -
    Larry
    Please post the resolution to your
    issue so others may benefit
    -
    Get Your SBS Health Check at
    www.sbsbpa.com


    > 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
    > following:
    >
    > 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
    > Master
    > Even my limited knowledge and experience led me to think that if this
    > was
    > the case I might have been aware of it before now.
    > Nevertheless, I followed KB234790 and established that the server was
    > the
    > 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
    > having
    > first configured it.
    > I suspect I should have made other changes!
    > I have noticed that the
    > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Win2kCfg\val
    > ues
    > 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
    >


      My System SpecsSystem Spec

  5. #4


    Chris Curtis Guest

    Re: SBS 2003 Best Practice Analyser reports problems but nothing in event viewer

    I don't get an option to select a NIC. It already recognises that there is
    only one.

    Chris


    "Merv Porter [SBS-MVP]" <mwport@newsgroup_spam_hotmail.com> wrote in message
    news:e%23pVoKelKHA.5040@newsgroup

    > Try re-running CEICW and then select the correct NIC and complete the rest
    > of CEICW. Then run the SBS 2003 BPA again.
    >
    > --
    > Merv Porter [SBS-MVP]
    > ============================
    >
    > "Chris curtis" <nospamatmitredotnet> wrote in message
    > news:eI$0MudlKHA.4408@newsgroup

    >> 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 following:
    >>
    >> The server running Windows SBS2003 is not the Schema Master
    >> 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
    >> Master
    >>
    >> Even my limited knowledge and experience led me to think that if this was
    >> the case I might have been aware of it before now.
    >> Nevertheless, I followed KB234790 and established that the server was the
    >> 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
    >> having first configured it.
    >> I suspect I should have made other changes!
    >> I have noticed that the
    >> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Win2kCfg\values
    >> 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
    >>
    >>


      My System SpecsSystem Spec

  6. #5


    Chris Curtis Guest

    Re: SBS 2003 Best Practice Analyser reports problems but nothing in event viewer

    Yes I wasn't migrating.
    And yes there is a wizard & yes I didn't use it initially not realising it
    existed!
    I did run it afterwards without changing any settings.
    I have BPA reports from last year when I originally installed the software
    which are fine so I'm pretty sure it has something to do with the way I
    changed the NIC's.
    I'll try your suggestion and change the ip address again using the wizard
    when disconnected from the switch.
    It will probably be over the weekend.

    Chris

    "Larry Struckmeyer[SBS-MVP]" <lstruckmeyer@newsgroup-wizards.com> wrote in message
    news:4e6835158f7f8cc63d216aa6993@newsgroup

    > 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
    > this magnitude.
    >
    >
    > -
    > Larry
    > Please post the resolution to your
    > issue so others may benefit
    > -
    > Get Your SBS Health Check at
    > www.sbsbpa.com
    >
    >

    >> 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
    >> following:
    >>
    >> 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
    >> Master
    >> Even my limited knowledge and experience led me to think that if this
    >> was
    >> the case I might have been aware of it before now.
    >> Nevertheless, I followed KB234790 and established that the server was
    >> the
    >> 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
    >> having
    >> first configured it.
    >> I suspect I should have made other changes!
    >> I have noticed that the
    >> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Win2kCfg\val
    >> ues
    >> 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
    >>
    >
    >


      My System SpecsSystem Spec

  7. #6


    Jim Behning SBS MVP Guest

    Re: SBS 2003 Best Practice Analyser reports problems but nothing in event viewer

    http://support.microsoft.com/kb/555605

    On Fri, 15 Jan 2010 12:09:08 -0000, "Chris curtis"
    <nospamatmitredotnet> wrote:

    >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 following:
    >
    >The server running Windows SBS2003 is not the Schema Master
    >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 Master
    >
    >Even my limited knowledge and experience led me to think that if this was
    >the case I might have been aware of it before now.
    >Nevertheless, I followed KB234790 and established that the server was the
    >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 having
    >first configured it.
    >I suspect I should have made other changes!
    >I have noticed that the
    >HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Win2kCfg\values
    >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
    >
    See what SBS support is working on
    http://blogs.technet.com/sbs/default.aspx
    Check your SBS with the SBS Best Practices Analyzer
    http://blogs.technet.com/sbs/archive...A/default.aspx

      My System SpecsSystem Spec

  8. #7


    Chris Curtis Guest

    Re: SBS 2003 Best Practice Analyser reports problems but nothing in event viewer

    No joy I'm afraid.
    I disconnected the server from the switch and ran the change ip address
    wizard.
    I got a message saying an error occured while changing the IP address.
    Rerun using original address.
    So I reran it and 'restored' the original address.

    Looking in the changeiplog.txt file reveals the following:
    *** ConfigureIIS returned ERROR 80070003
    "Generic Error"; hr is 0x80070003.

    I also note that the WWWPublishing service does not restart.

    Incidentally the ipconfig results are:

    Windows IP Configuration
    Host Name . . . . . . . . . . . . : server
    Primary Dns Suffix . . . . . . : mitre.local
    Node Type . . . . . . . . . . . . : Unknown
    IP Routing Enabled. . . . . .. : Yes
    WINS Proxy Enabled. . . . : Yes
    DNS Suffix Search List. . . : mitre.local

    Ethernet adapter LAN:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Intel(R) PRO/100 Network Connection
    Physical Address. . . . . . . : 00-06-5B-8C-AB-0C
    DHCP Enabled. . . . . . . . : No
    IP Address. . . . . . . . . . . . : 172.16.10.2
    Subnet Mask . . . . . .. . . . : 255.255.255.0
    Default Gateway . . .. . . . : 172.16.10.254
    DNS Servers . . . . . . . . . : 172.16.10.2
    Primary WINS Server . . . : 172.16.10.2

    Chris




      My System SpecsSystem Spec


SBS 2003 Best Practice Analyser reports problems but nothing in event viewer
Similar Threads
Thread Forum
Re: Best Practice for Vistualizing SBS 2003 R2 with ISA installed SBS Server
Re: Best Practice for Vistualizing SBS 2003 R2 with ISA installed SBS Server
SBS 2003 Best Practice Analyzer and WSuS SBS Server
Nero problems in Event Viewer Software
HELP need to solve this problem asap - Unable to start event viewer/event log service Software