Can not browse computer in a different workgroup

  • Thread starter Thread starter Chow
  • Start date Start date
C

Chow

My organisation a recently purchase a few new PC running
Win XP Home Edition. I had set configure to be a
different because there are over 80 PC connected to the
orginal Workgroup.
Lately I had encounter the following when I tried to
access the other workgroup.

"Workgroup is not accessible. You might not have
permission to use this network resource. Contact the
administrator of this server to find out is you have
access permissions.
No more connections can be made to this remote computer
at this time because there are already as many connection
as the computer can accept."

I can access the computer is the workgroup if I search
for it in the Windows Explorer, ie the Permission should
not be an issue.

Thank You
 
Chow said:
My organisation a recently purchase a few new PC running
Win XP Home Edition. I had set configure to be a
different because there are over 80 PC connected to the
orginal Workgroup.
Lately I had encounter the following when I tried to
access the other workgroup.

"Workgroup is not accessible. You might not have
permission to use this network resource. Contact the
administrator of this server to find out is you have
access permissions.
No more connections can be made to this remote computer
at this time because there are already as many connection
as the computer can accept."

I can access the computer is the workgroup if I search
for it in the Windows Explorer, ie the Permission should
not be an issue.

Thank You

Are you sure you're not talking about domains? It seems very unlikely to
me that anyone would set up 80 computers in a workgroup instead of a
domain. In that case, your problem is that XP Home cannot join a
domain, only XP Pro can. Home Edition can use the domain resources (by
doing what you describe). Post back with more details of the network
setup if you need more help.

Malke
 
-----Original Message-----


Are you sure you're not talking about domains? It seems very unlikely to
me that anyone would set up 80 computers in a workgroup instead of a
domain. In that case, your problem is that XP Home cannot join a
domain, only XP Pro can. Home Edition can use the domain resources (by
doing what you describe). Post back with more details of the network
setup if you need more help.

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
Don't Panic!
.
Thanks for replying.
Well, the Network setup in this organisation is a bit
weird(I'd just join the organisation). They had put the
Win NT 4.0 in a different domain as a PDC call "Server".
And all the workstations(95,98,Me&XP) in a different
workgroup. All workstation except for the XP's logon
will be authenticated by the PDC but they are in the
workgroup call "workgroup".
The XP user will be authenticated locally but the same
user id was created on the PDC so that they can access
the resource on the Domain "Server".
Thanks again.

What I suspect is could XP
 
Chow wrote:

(various snippage)
Thanks for replying.
Well, the Network setup in this organisation is a bit
weird(I'd just join the organisation). They had put the
Win NT 4.0 in a different domain as a PDC call "Server".
And all the workstations(95,98,Me&XP) in a different
workgroup. All workstation except for the XP's logon
will be authenticated by the PDC but they are in the
workgroup call "workgroup".
The XP user will be authenticated locally but the same
user id was created on the PDC so that they can access
the resource on the Domain "Server".
Thanks again.

What I suspect is could XP

Since the rest of your post didn't make it, I don't know what you
suspect. However, this is a very strange setup. If the workstations are
being authenticated by the PDC, then they are not in a workgroup, but
must be in the domain. Unless the domain has stupidly been called
"Workgroup"? I'm afraid I still don't have a clear picture of your
setup from your descriptions. Basically, if you want the XP machine to
be part of the domain, you need to have XP Pro and join the machine to
the domain. If you don't care about it being authenticated by the
domain (as part of the domain and therefore with domain rights and
permissions) and are OK with the mechanism for using domain resources
in XP Home, stay with Home. Either please post back with a clearer
outline of exactly what the problem is and what you actually want to
do, or (and I really think this is your best solution) contact a local
networking guru and have them check out your setup in person. I don't
say this last thing to be hurtful, but when dealing with that many
computers in a corporate environment, you really need to have things
set up correctly and securely by an expert.

Good luck,

Malke
 
Back
Top