Unable to See Windows Servers

I'm getting this story 2nd or 3rd hand, so I can't provide a lot of details.
I'll try to provide enough basic information to accurately describe the
problem.

We have a group of Windows 2000 Servers in another building. In the same
building, and supposedly on the same switch, are a number of Windows XP Pro
machines. On one machine, if you go to Windows Explorer > My Network Places
> Entire Network > Microsoft Windows Network, you will see all the Windows
2000 servers. On every other machine, if you do the same thing, you will
see only the Workgroup. The question is: Why?

We need to make all the XP Pro machines see all the Windows 2000 servers.
My first thought was that a Windows domain was created, and that the one
machine that can see the servers is in the domain, and the other machines
are not. However, the tech that supports these machines maintains that
there is no Windows domain.

--Tom

Hi thomas,
Thomas M wrote:
> We have a group of Windows 2000 Servers in another building. In the
> same building, and supposedly on the same switch, are a number of
> Windows XP Pro machines. On one machine, if you go to Windows
> Explorer > My Network Places
>> Entire Network > Microsoft Windows Network, you will see all the
>> Windows
> 2000 servers. On every other machine, if you do the same thing, you
> will see only the Workgroup. The question is: Why?

how is the name resolution realized?
Registering all servers and clients on a WINS server could help.
Are there other protocols in use besides TCP/IP? Are the machines in
different subnets?

Best greetings from Germany
Olaf.

If there is not a domain controller, the machines will all need to be in
the same workgroup.

Only a domain controller has the ability to merge browse lists. Without
a domain controller, machines in a workgroup will only see the browse list
for that workgroup.

Thomas M wrote:
> I'm getting this story 2nd or 3rd hand, so I can't provide a lot of
> details. I'll try to provide enough basic information to accurately
> describe the problem.
>
> We have a group of Windows 2000 Servers in another building. In the
> same building, and supposedly on the same switch, are a number of
> Windows XP Pro machines. On one machine, if you go to Windows
> Explorer > My Network Places
>> Entire Network > Microsoft Windows Network, you will see all the
>> Windows
> 2000 servers. On every other machine, if you do the same thing, you
> will see only the Workgroup. The question is: Why?
>
> We need to make all the XP Pro machines see all the Windows 2000
> servers. My first thought was that a Windows domain was created, and
> that the one machine that can see the servers is in the domain, and
> the other machines are not. However, the tech that supports these
> machines maintains that there is no Windows domain.
>
> --Tom

Thanks for the reply. TCP/IP should be the only protocol, but I'll check on
that to make sure. I'm not sure about the other items as these servers and
machines are not in the area that I regularly support, so I'll have to check
on those.

--Tom

"Olaf Engelke [MVP Windows Server]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi thomas,
> Thomas M wrote:
> > We have a group of Windows 2000 Servers in another building. In the
> > same building, and supposedly on the same switch, are a number of
> > Windows XP Pro machines. On one machine, if you go to Windows
> > Explorer > My Network Places
> >> Entire Network > Microsoft Windows Network, you will see all the
> >> Windows
> > 2000 servers. On every other machine, if you do the same thing, you
> > will see only the Workgroup. The question is: Why?
>
> how is the name resolution realized?
> Registering all servers and clients on a WINS server could help.
> Are there other protocols in use besides TCP/IP? Are the machines in
> different subnets?
>
> Best greetings from Germany
> Olaf.
>

Thanks for the reply. I'll pass this information on to the LAN manager who
is working the problem. It may be a few days before I can post an update.

--Tom

"Bill Grant" <not.available@online> wrote in message
news:Obx2A$(E-Mail Removed)...
> If there is not a domain controller, the machines will all need to be
in
> the same workgroup.
>
> Only a domain controller has the ability to merge browse lists.
Without
> a domain controller, machines in a workgroup will only see the browse list
> for that workgroup.
>
> Thomas M wrote:
> > I'm getting this story 2nd or 3rd hand, so I can't provide a lot of
> > details. I'll try to provide enough basic information to accurately
> > describe the problem.
> >
> > We have a group of Windows 2000 Servers in another building. In the
> > same building, and supposedly on the same switch, are a number of
> > Windows XP Pro machines. On one machine, if you go to Windows
> > Explorer > My Network Places
> >> Entire Network > Microsoft Windows Network, you will see all the
> >> Windows
> > 2000 servers. On every other machine, if you do the same thing, you
> > will see only the Workgroup. The question is: Why?
> >
> > We need to make all the XP Pro machines see all the Windows 2000
> > servers. My first thought was that a Windows domain was created, and
> > that the one machine that can see the servers is in the domain, and
> > the other machines are not. However, the tech that supports these
> > machines maintains that there is no Windows domain.
> >
> > --Tom
>
>