Re: Workgroup issue
Tech-Archive recommends: Fix windows errors by optimizing your registry
What exactly do you mean by "see the computers"? Do you mean in Network
Neighborhood/My network Places?
You should be able to see every machine which has at least one file
shared. In the worst case, you may have to run the network setup wizard on
each machine.
Brett Evanson wrote:
> The machines were set up as workgroup members instead of domain
> members. Would it be a problem it there was a machine somewhere that
> still thought it was a member of the domain? Could it be that some
> machine still thinks it is on the domain even with the dc gone? How
> would I go about finding this computer. We have hundreds that used to
> be on the domain. I really don't want to go one by one trying to find
> out which one is the problematic one. Thanks in advance for your
> expertise and help
>
> Brett Evanson
>
>
> On 10/3/05 11:19 AM, in article
dKd0f.702$YH6.12@trnddc06, "A. Feiner"
> <none@xxxxxxxx> wrote:
>
>> Were the machine ever removed from the domain?
.
Relevant Pages
- 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) - Re: How to create file on network share from ASP.NET
... You might want to talk to your network admin ... Juan T. Llibre ... > Thank you for your reply, but my point is exactly that both computers ARE ... > NOT members of the same domain - one is standalone Win2003 and another is ... (microsoft.public.dotnet.framework.aspnet) - Re: Help with 070-217
... The network contains 25,000 computers. ... > single Windows 2000 domain named research.contoso.com. ... > Server computers that are configured as domain controllers. ... (microsoft.public.cert.exam.mcse) |
|