JonSoellner
asked on
Windows 2000 Server ''no more connections can be made'' when browsing network
Hi
I am logged in to a workstation as a domain admin. I want to browse the windows network tree, but when I try to expand the domain tree, I am receiving the error message "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".
We have purchased 20 per seat CALs for our Windows 2000 Server, I have just updated the licencing config on the server. Do I need to restart the server before this takes effect? Or does this have nothing to do with the error message?
The solution is probably very embarrassingly obvious but any help would be appreciated. Thanks
error-msg.JPG
I am logged in to a workstation as a domain admin. I want to browse the windows network tree, but when I try to expand the domain tree, I am receiving the error message "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".
We have purchased 20 per seat CALs for our Windows 2000 Server, I have just updated the licencing config on the server. Do I need to restart the server before this takes effect? Or does this have nothing to do with the error message?
The solution is probably very embarrassingly obvious but any help would be appreciated. Thanks
error-msg.JPG
ASKER
I can open folders on the server with no problems.
I now think the problem is actually caused by one of the workstations in the tree, preventing me from exploring the rest of the network.
One machine is acting as server for a CAD software package used in the factory - something that was implemented before I started with the company (excuses, excuses)
I will have to check that the guys in the factory are logging off correctly. In fact, if the 'server' machine is being left on all the time, which I suspect is the case, the inactive sessions will probably be causing the problem.
Sorry, I should have checked this earlier while I was at work. I will accept your comment as the solution if that is the case.
Thanks for your help.
I now think the problem is actually caused by one of the workstations in the tree, preventing me from exploring the rest of the network.
One machine is acting as server for a CAD software package used in the factory - something that was implemented before I started with the company (excuses, excuses)
I will have to check that the guys in the factory are logging off correctly. In fact, if the 'server' machine is being left on all the time, which I suspect is the case, the inactive sessions will probably be causing the problem.
Sorry, I should have checked this earlier while I was at work. I will accept your comment as the solution if that is the case.
Thanks for your help.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thanks JonSoellner.
Cheers !
--Rob
Cheers !
--Rob
Do you get the same message when you try to connect directly to the server using \\ServerName\Share