Workstations cannot see workgroup afetr installing Windows Server 2003 R2

We just installed a new server at a site and set up an active directory
domain for the users. They can log on to the domain fine, but they
cannot browse their previous workgroup. The only thing that shows up in
"entire network" is the new domain. I am thinking this is due to some
new security policy in R2, but I can't seem to find it. Any help would
be GREATLY appreciated!



llong@zaltec.com

A machine cannot be a member of both a workgroup and a domain at the same
time. A user cannot be logged on as a local user and a domain user at the
same time from one machine. Since you said they can "log on to the domain
fine", I am assuming the machine and the user are a member of the domain
now. That's why they can't browse their old workgroup.

With the correct domain permissions, they could still access resources on
those other (now domain member) machines though.

-Frank

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> We just installed a new server at a site and set up an active directory
> domain for the users. They can log on to the domain fine, but they
> cannot browse their previous workgroup. The only thing that shows up in
> "entire network" is the new domain. I am thinking this is due to some
> new security policy in R2, but I can't seem to find it. Any help would
> be GREATLY appreciated!
>

I know I have done this before. I have users that are logged in to a
domain, but they are still able to see and browse a workgroup.

I can still access resources on the workgroup by using //sharename, but
I though I need to be able to see the workgroup resources in the
"Microsoft Windows Network as well.

On Nov 15, 11:29 am, "Frankster" <F...@SPAM2TRASH.com> wrote:
> A machine cannot be a member of both a workgroup and a domain at the same
> time. A user cannot be logged on as a local user and a domain user at the
> same time from one machine. Since you said they can "log on to the domain
> fine", I am assuming the machine and the user are a member of the domain
> now. That's why they can't browse their old workgroup.
>
> With the correct domain permissions, they could still access resources on
> those other (now domain member) machines though.
>
> -Frank
>
> <l...@zaltec.com> wrote in messagenews:(E-Mail Removed) ooglegroups.com...
>
>
>
> > We just installed a new server at a site and set up an active directory
> > domain for the users. They can log on to the domain fine, but they
> > cannot browse their previous workgroup. The only thing that shows up in
> > "entire network" is the new domain. I am thinking this is due to some
> > new security policy in R2, but I can't seem to find it. Any help would
> > be GREATLY appreciated!- Hide quoted text -- Show quoted text -

Is it possible that the workgroup name has to be the same as the domain
name? I think this is the case in my other installations.

-Ralph Long

On Nov 15, 12:45 pm, l...@zaltec.com wrote:
> I know I have done this before. I have users that are logged in to a
> domain, but they are still able to see and browse a workgroup.
>
> I can still access resources on the workgroup by using //sharename, but
> I though I need to be able to see the workgroup resources in the
> "Microsoft Windows Network as well.
>
> On Nov 15, 11:29 am, "Frankster" <F...@SPAM2TRASH.com> wrote:
>
>
>
> > A machine cannot be a member of both a workgroup and a domain at the same
> > time. A user cannot be logged on as a local user and a domain user at the
> > same time from one machine. Since you said they can "log on to the domain
> > fine", I am assuming the machine and the user are a member of the domain
> > now. That's why they can't browse their old workgroup.
>
> > With the correct domain permissions, they could still access resources on
> > those other (now domain member) machines though.
>
> > -Frank
>
> > <l...@zaltec.com> wrote in messagenews:(E-Mail Removed) ooglegroups.com...
>
> > > We just installed a new server at a site and set up an active directory
> > > domain for the users. They can log on to the domain fine, but they
> > > cannot browse their previous workgroup. The only thing that shows up in
> > > "entire network" is the new domain. I am thinking this is due to some
> > > new security policy in R2, but I can't seem to find it. Any help would
> > > be GREATLY appreciated!- Hide quoted text -- Show quoted text -- Hide quoted text -- Show quoted text -

Yes, that should do it.

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> Is it possible that the workgroup name has to be the same as the domain
> name? I think this is the case in my other installations.
>
> -Ralph Long
>
> On Nov 15, 12:45 pm, l...@zaltec.com wrote:
>> I know I have done this before. I have users that are logged in to a
>> domain, but they are still able to see and browse a workgroup.
>>
>> I can still access resources on the workgroup by using //sharename, but
>> I though I need to be able to see the workgroup resources in the
>> "Microsoft Windows Network as well.
>>
>> On Nov 15, 11:29 am, "Frankster" <F...@SPAM2TRASH.com> wrote:
>>
>>
>>
>> > A machine cannot be a member of both a workgroup and a domain at the
>> > same
>> > time. A user cannot be logged on as a local user and a domain user at
>> > the
>> > same time from one machine. Since you said they can "log on to the
>> > domain
>> > fine", I am assuming the machine and the user are a member of the
>> > domain
>> > now. That's why they can't browse their old workgroup.
>>
>> > With the correct domain permissions, they could still access resources
>> > on
>> > those other (now domain member) machines though.
>>
>> > -Frank
>>
>> > <l...@zaltec.com> wrote in
>> > messagenews:(E-Mail Removed) ooglegroups.com...
>>
>> > > We just installed a new server at a site and set up an active
>> > > directory
>> > > domain for the users. They can log on to the domain fine, but they
>> > > cannot browse their previous workgroup. The only thing that shows up
>> > > in
>> > > "entire network" is the new domain. I am thinking this is due to some
>> > > new security policy in R2, but I can't seem to find it. Any help
>> > > would
>> > > be GREATLY appreciated!- Hide quoted text -- Show quoted text -- Hide
>> > > quoted text -- Show quoted text -
>