Re: Removing Old Domains in Network Neighborhood.....

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: «bonehead;\) (noone_at_spam.not)
Date: 10/08/04

  • Next message: Sudeep Batra: "administrators account gets frequently locked" 
    Date: Fri, 08 Oct 2004 04:32:46 GMT

    ""Frank Szita [MSFT]"" <a-fszita@online.microsoft.com> wrote in message
    news:TeTRsoOrEHA.3608@cpmsftngxa06.phx.gbl...
    > 1. In Active Directory Domains and Trusts make sure that the domains
    > aren't listed there
    > 2. If using WINS make sure there are no records for the rogue domains and
    > computers
    > 3. Check the local LMHOSTS file to make sure there are no rogue domains
    > and computers
    > 4. Make sure there are no computers on the network that were a member of
    > the now defunct domain
    >
    > Best regards,
    >
    > Frank Szita [MSFT]
    >
    > This posting is provided "AS IS" with no warranties, and confers no
    rights.

    Thanks for the tip.... We are setting up networks in our labs at school, it
    becomes
    quite annoying when all these entries appear...
    I've learned more from these NG's then I have from my lameass
    instructors....
    thanks again.... 

    -- 
<B0N3H3@D>
"I have no special talent. I am only passionately curious." Albert Einstein
  • Next message: Sudeep Batra: "administrators account gets frequently locked"

    Relevant Pages

    • Re: Removing Old Domains in Network Neighborhood.....
      ... This posting is provided "AS IS" with no warranties, and confers no rights. ... Check the local LMHOSTS file to make sure there are no rogue domains ... >> and computers ... Make sure there are no computers on the network that were a member ...
      (microsoft.public.win2000.advanced_server)
    • RE: Removing Old Domains in Network Neighborhood.....
      ... In Active Directory Domains and Trusts make sure that the domains ... Check the local LMHOSTS file to make sure there are no rogue domains ... and computers ...
      (microsoft.public.win2000.advanced_server)
    • Re: The Hard Problem for Behaviorists
      ... correct low level abstractions to define the operation of the brain with - ... Do you not know how computers work? ... you can think of this type of network like you ... when you drop a marble in hole X1, ...
      (sci.cognitive)
    • Re: Networks : Workgroups and Domains. How Do I Use Them?
      ... I think the problem is from my lack of understanding whether these machines are together as a workgroup or domain. ... If I want to configure solely for a workgroup network, then I would think I do not need to provide a domain name, and vice versa for a domain network. ... It's not clear whether any of your computers is running Windows 2000 *Server.* If not, you don't have a "domain" and shouldn't be using domain names. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall or overlooked firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
      (microsoft.public.windowsxp.network_web)
    • Re: {workgroup}"...is not accessible" after removing NWLINK
      ... I generally reboot the machine whenever I make network ... >problem is a browse service that won?t run on the XP machine using the TCP/IP ... >?The browser has forced an election on network ... >> computer, and one, or preferably two, of the Windows 98 computers. ...
      (microsoft.public.windowsxp.network_web)