General discussion

  • Creator
    Topic
  • #2087385

    BDC and Rebooting

    Locked

    by -j- ·

    I have a problem with only this particular BDC. The past two times this box has needed to be rebooted, when the box comes back up The workstation service and others fail and the reason is a duplicate computer name already exists on the network. We are using WINS and all the servers are Statically mapped. All other BDC’s as well as member servers do not have any problems when rebooting?

All Comments

  • Author
    Replies
    • #3876540

      BDC and Rebooting

      by mpdcsup ·

      In reply to BDC and Rebooting

      If, indeed, no other machine has the same name as the BDC, then for some reason WINS is not recognizing that the machine coming up (the BDC) is the one it has registered entries for. You say all of your servers are statically mapped. Do you mean they are statically mapped in WINS? or do you mean they have static IP Addresses? If they have static IP Addresses, that’s nice, but irrelevant. If you have them statically mapped in WINS, why?

      Shut down the machine and (if you can’t wait three days for the records to expire) flush the WINS cache. You may find your Network Neighborhood suddenly doesn’t show every connected machine, but over a few days (as the cache is rebuilt) everything should be hunky-dorey. If this really irks you, you can manually delete all references in the WINS database to the BDC. If you have multiple WINS servers in your network, you only need to do this on the one on the same segment as the BDC.

      • #3879900

        BDC and Rebooting

        by -j- ·

        In reply to BDC and Rebooting

        Poster rated this answer

    • #3879899

      BDC and Rebooting

      by -j- ·

      In reply to BDC and Rebooting

      This question was closed by the author

Viewing 1 reply thread