Re: Workgroup issue

Tech-Archive recommends: Fix windows errors by optimizing your registry

I try and go to "view workgroup computers" from the my network places, and
it stalls for a second and then says i don't have permission. there
shouldn't be permission issues because they are just plain shared. there
isn't a domain controller giving permission to see the workgroup computers.
that is, if i am thinking right. once i can see the computers, i can deal
with individual password issues, but i think the problem lies somewhere with
a residual computer thinking it has some connection with the domain math and
not the workgroup math. am i thinking this through right? if i am, how do i
go about finding which computer it is?

Brett

"Bill Grant" <not.available@online> wrote in message
news:O7ewA0GyFHA.3360@xxxxxxxxxxxxxxxxxxxxxxx
> 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: workgroup File sharing problem XP SP2
    ... All computers ARE in the same workgroup called MSHOME. ... On A: View workgroup computers now shows 4 computers: B, C, and A twice, ... ANY of the "My Network Places" windows, but they are accessible by clicking ... B's and C's shared folders are ...
    (microsoft.public.windowsxp.network_web)
  • 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: Accessing Computer on Network: Access is Denied
    ... You might not have permission to use this ... network resource. ... I have three computers on the network. ... laptop running 98 SE, and a laptop running XP media center edition version ...
    (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)