No. of connections possible in peer to peer

[cygan]

Originally posted by: Brazen
[That is my guess, but it's hard to tell without seeing when exactly they get that error, the exact words of the error, and most importantly - what are they able to access even when they get the error, such as can they browse the internet, can they ping the servers, can they ping other workstations or the gateway, etc...


The exact message reads like this"Workgroup Name is not accessible. You may not have permission to use this network resource" and secondly" No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept. ".

In both cases, the machine cannot perform any network obligations- neither can it see any computers nor can it access them or the internet.

 

[cygan]

I think I may have found the answer to the" Workgroup not accessible...." error. It may have something to do with enabling NetBios over TCP/IP for XP Pcs & starting the "computer Browser" in services. I will have to wait until tomorrow though till I can practically try the same

 

[Brazen]

Originally posted by: cygan

Originally posted by: Brazen
[That is my guess, but it's hard to tell without seeing when exactly they get that error, the exact words of the error, and most importantly - what are they able to access even when they get the error, such as can they browse the internet, can they ping the servers, can they ping other workstations or the gateway, etc...


The exact message reads like this"Workgroup Name is not accessible. You may not have permission to use this network resource" and secondly" No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept. ".

In both cases, the machine cannot perform any network obligations- neither can it see any computers nor can it access them or the internet.

hmm, if it was in fact a concurrent connection problem, I would think you should still be able to browse the internet. Have to checked to make sure the the computer is getting an IP address and is able to ping stuff. Per the first error, "Worgroup Name blah blah..." maybe you are running out of DHCP leases. Find your DHCP server and increase the number of leases available (this does not cost anything, but there could be complications involved).

Either way, it still sounds like you need to get a central file server put in desperately. Especially if files are being shared between workstations, they are not getting backed up (I would assume), which of course can spell disaster for a business. BTW, here is a Knowledgebase article on that second error.

BTW, you can use SAMBA as a domain controller, too, and manage all the login accounts. That is getting a _little_ more complicated though (I would image, I've never used SAMBA as a domain controller myself).

 

[Brazen]

Here is a KB article on the other error: http://support.microsoft.com/?kbid=913628

Isn't Google wonderful?