Re: Workgroup issue

We don't have a workgroup server. I thought you didn't need one. The shares
we are trying to access are on each individual computer. Sounds like I might
be doing something wrong. Thanks in advance for your help.

Brett Evanson


"Bill Grant" <not.available@online> wrote in message
news:%23EMHFSVyFHA.1552@xxxxxxxxxxxxxxxxxxxxxxx
> 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: Access Sql server 2005 from .net class library
    ... Just use regular connection string for Windows Authentication, ... data from another workgroup server using direct sql access. ...
    (microsoft.public.sqlserver.security)
  • Re: logon failed when trying to access server
    ... as a workgroup server. ... point to the local DNS (probably the sbs server) and log in to the domain. ... >> workgroup named WORKGROUP, and then restart the computer. ...
    (microsoft.public.windows.server.networking)
  • Re: LSASRV Errors point to wrong network
    ... firewall, and the 2 sites are not supposed to communicate with each other. ... I have seen LSASRV errors on my workgroup server that seem to happen almost hourly. ...
    (microsoft.public.windows.server.general)
  • aliasing user logins
    ... Originally we only had a Windows Workgroup, and I run Samba on the server to ... Samba was running, shares worked fine. ...
    (comp.unix.bsd.freebsd.misc)
  • Re: administrative shares
    ... >> Windows 2000 Professional Workgroup ... >> share command loads the shares, ... Start/Run/fsmgmt.msc produces a list of shared folders. ... enables the ipc$ share ("ipc$ was shared ...
    (microsoft.public.win2000.networking)