Re: Workgroup issue

No. A machine still in a domain would not cause that problem. A domain
and a workgroup can exist on the same segment. They would appear as two
separate entities.

All of this is driven by the computer browser service. Do you still have
the servers there, running as workgroup servers? You will need to recreate
the shares after they have been demoted.


Brett Evanson wrote:
> 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: Network Neighborhood
    ... > inability to browse by using Network Neighborhood in Windows 95 or Windows ... > communicated effectively with the other workgroup computers. ... > not have a common networking protocol, a common workgroup, and common user ... the computer that is running Windows ...
    (microsoft.public.win2000.networking)
  • Re: WindowsXP and RISC OS computers
    ... >> - You can however ping Nixiyo from the windows XP machine, ... > workgroup: WORKGROUP ... > Name as M$ calls it, had been changed on the centrex machine. ... > Neither icon appears in My Network Places on the centrex. ...
    (comp.sys.acorn.networking)
  • clarification sought in using XP Pro laptop for domain at work and workgroup at home
    ... I am inquiring for a friend. ... The XP Pro laptop was once configured for a two-computer workgroup. ... "WORKGROUP" as the name of its network affiliation. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Setting up a network using XP and Vista
    ... In XP I have gone to Network Set Up Wizard the default Workgroup is MSHOME. ... a misconfigured firewall or overlooked firewall (including a stateful ...
    (microsoft.public.windowsxp.general)
  • Re: help understanding authentication on workgroups
    ... network client services on and print/file sharing on), ... workgroup authentication is said to be ... the password for that guest account on that computer, I get access to that PC ... The browser provides visibility. ...
    (microsoft.public.windowsxp.network_web)
Loading