XP Home on Win 2003.

I have a new W2K3 server a made it my PDC. I cannot connect to the server
itself through Windows Home to access shared folders. I realize I can't set
it up on the domain, but I have been able, in the past, to set it up on W2K
to see shared folders. Is this a W2K3 issue, or is there some other possible
reason?

Make the workgroup name match the domain name.

Create an identical acount on the domain the matches the local account on
the "home" machine.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"David Langschied" <(E-Mail Removed)> wrote in
message news:2DA959FF-5810-41D4-BAF2-(E-Mail Removed)...
> I have a new W2K3 server a made it my PDC. I cannot connect to the server
> itself through Windows Home to access shared folders. I realize I can't
set
> it up on the domain, but I have been able, in the past, to set it up on
W2K
> to see shared folders. Is this a W2K3 issue, or is there some other
possible
> reason?

I will do this. However, even the work group (domain) was not necessary on
W2K. Is this no longer possible?

"Phillip Windell" wrote:

> Make the workgroup name match the domain name.
>
> Create an identical acount on the domain the matches the local account on
> the "home" machine.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "David Langschied" <(E-Mail Removed)> wrote in
> message news:2DA959FF-5810-41D4-BAF2-(E-Mail Removed)...
> > I have a new W2K3 server a made it my PDC. I cannot connect to the server
> > itself through Windows Home to access shared folders. I realize I can't
> set
> > it up on the domain, but I have been able, in the past, to set it up on
> W2K
> > to see shared folders. Is this a W2K3 issue, or is there some other
> possible
> > reason?
>
>
>

"David Langschied" <(E-Mail Removed)> wrote in
message news:B979755C-AA8A-4F38-861B-(E-Mail Removed)...
> I will do this. However, even the work group (domain) was not necessary
on

The way you wrote that "work group (domain)" implies you think it may be the
same thing. workgroups and domains are two different things.

> W2K. Is this no longer possible?

You *must* be either a Domain (requires a Domain Controller) or a Workgroup.
You cannot be nothing at all,...never could.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

I guess what meant was that I could be part of workgroupA and see domainA and
domainB under entire network. I was having trouble seeing server2 on
domainB. I am now seeing it.

"Phillip Windell" wrote:

> "David Langschied" <(E-Mail Removed)> wrote in
> message news:B979755C-AA8A-4F38-861B-(E-Mail Removed)...
> > I will do this. However, even the work group (domain) was not necessary
> on
>
> The way you wrote that "work group (domain)" implies you think it may be the
> same thing. workgroups and domains are two different things.
>
> > W2K. Is this no longer possible?
>
> You *must* be either a Domain (requires a Domain Controller) or a Workgroup.
> You cannot be nothing at all,...never could.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
>
>

"David Langschied" <(E-Mail Removed)> wrote in
message news:6EC05543-573E-47D7-A001-(E-Mail Removed)...
> I guess what meant was that I could be part of workgroupA and see domainA
and
> domainB under entire network. I was having trouble seeing server2 on
> domainB. I am now seeing it.

Ok.
It have take the browse List time to "rebuild". What you see in "Network
Places" is taken from a "browse list" and is not a "live" view of the
network.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com