Re: Cannot Browse the Domain in the Network Neighborhood
- From: Joshua @ UDA <JoshuaUDA@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 4 May 2005 13:10:01 -0700
David,
Thank you very much for the information. I removed the network card and
successfully removed the extra IP address for the Domain Master Browser in
the WINS server. Apparently the second nic's IP address was given ownership
of all the WINS records before and that disabled the network browsing
capabilities in My Network Places. I'm no expert so I couldn't explain
exactly why it happened or why it caused the problem.
Thanks again for your help. The other posts that I've viewed are leap-frog
conversations that seem to lead nowhere.
I do have another question and will post it seperately as well as here. We
recently had a disaster recovery situation where I had to recreate the domain
here at our office. The domain was in a test phase and no backups were
considered useable. This system is not mission critical and so a reinstall
was the faster option over Domain Recovery tools. When I recreated the
domain, I gave it the same name as the previously existing domain before the
domain controller crashed. Since then I have had random KDC errors talking
about duplicate service principal names. My question is whether or not it is
bad practice to replace one domain controller (and domain) with another of
the same name. Hopefully some of that made sense. Anyway thanks again.
Joshua
""David Copeland [MSFT]"" wrote:
> Joshua,
>
> You should be able to show a list of the records in the WINS database (via
> the WINS mmc) and then right click on the domainname[1B] entry and select
> Delete. Then from a command prompt you should be able to run nbtstat -RR
> to have the server re-register it's NetBIOS names.. Then check to see if it
> comes back.. If you're not able to delete the one entry you could also do
> a Delete Owner by right clicking on Server Registrations.. This would
> delete all of the entres from the WINS database for this owner.. So, on the
> server you would want to run the nbtstat -RR (if not reboot, if there are
> other 3rd party apps that may need to register their NetBIOS names) and
> then either wait or reboot the clients for them to re-register.
>
> --
>
> Hope that helps,
> David Copeland
> Microsoft Small Business Server Support
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Newsgroups:
> SBS v4.x : microsoft.public.backoffice.smallbiz
> SBS 2000: microsoft.public.backoffice.smallbiz2000
> SBS 2003: microsoft.public.windows.server.sbs
>
>
.
- Follow-Ups:
- Re: Cannot Browse the Domain in the Network Neighborhood
- From: David Copeland [MSFT]
- Re: Cannot Browse the Domain in the Network Neighborhood
- References:
- Re: Cannot Browse the Domain in the Network Neighborhood
- From: David Copeland [MSFT]
- Re: Cannot Browse the Domain in the Network Neighborhood
- From: Joshua @ UDA
- Re: Cannot Browse the Domain in the Network Neighborhood
- From: "David Copeland [MSFT]"
- Re: Cannot Browse the Domain in the Network Neighborhood
- Prev by Date: Re: Cannot Synchronize time clock SBS2003 with IIS
- Next by Date: Memory usage
- Previous by thread: Re: Cannot Browse the Domain in the Network Neighborhood
- Next by thread: Re: Cannot Browse the Domain in the Network Neighborhood
- Index(es):
Relevant Pages
|