Nick_Parker Posted September 2, 2009 Posted September 2, 2009 Hi All, I've recently started getting errors when connecting to some of our servers saying: "\\printserver is not accessible. You might not have permissions to use this network resource. Contact the administrator of this server to find out if you have access permissions. 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." This has happened on 2 different servers on two different laptops in the last week. This first laptop was a Vista laptop not connected to the domain, I fixed that by resetting the server (I was able to do it as it was during the holidays). The second one is my Windows 7 Enterprise laptop (also not joined to the domain) - I am unable to reset the server as there are still alot of people connected to it. What is causing this problem? How can I check how many connections there are to the server? I didn't even know that servers had a limit? Both Servers are running Server 2008 Standard. Thanks!
Nick_Parker Posted September 2, 2009 Author Posted September 2, 2009 Sorry, forgot to attach the screenshot
machin05 Posted September 2, 2009 Posted September 2, 2009 Might be a licensing issue? Are you set up per seat or per server?
Nick_Parker Posted September 2, 2009 Author Posted September 2, 2009 I don't remember ever setting anything when installing Server 2008. When installing Server 2003 I always used to use "Per Client" - each client needed a license.
spc-rocket Posted September 2, 2009 Posted September 2, 2009 I don't remember ever setting anything when installing Server 2008. When installing Server 2003 I always used to use "Per Client" - each client needed a license. Hiya, You don't have by any chance symantec antivirus corp edition installed on the server? If so then this is one of the causes of shares located on a server 2008 being disconnected and not available. I'm not sure that it applies to printers biut we had a few problems with the shares being completely inaccissible and locking upi PCs. Ash.
ricki Posted September 2, 2009 Posted September 2, 2009 Have you tried rebooting the server. It sounds like one of the services might have stopped. Richard
Nick_Parker Posted September 2, 2009 Author Posted September 2, 2009 Hiya, You don't have by any chance symantec antivirus corp edition installed on the server? If so then this is one of the causes of shares located on a server 2008 being disconnected and not available. I'm not sure that it applies to printers biut we had a few problems with the shares being completely inaccissible and locking upi PCs. Ash. Nope, no Symantec
Nick_Parker Posted September 2, 2009 Author Posted September 2, 2009 Have you tried rebooting the server. It sounds like one of the services might have stopped. Richard I'm going to try rebooting now, I couldn't earlier as everybody who could connect was still using it.
ZeroHour Posted September 2, 2009 Posted September 2, 2009 How many clients are connecting to the server? What is the server doing? just print spooler or file services as well? Windows 2003 had this issue and you had to reg key it to increase the limits of the LanServer but not sure about 2008
bio Posted September 3, 2009 Posted September 3, 2009 did you check the firewall settings ? Start troubleshooting by disabling windows 2008 firewall. It could be that the RPC services blocks the connection bio...
button_ripple Posted September 3, 2009 Posted September 3, 2009 We had this problem once, it was where monitoring software on clients would open and connect to the server to get the status of the printer, but wouldn't close again afterwards, instead everytime someone printed, it would open another instance, and keep opening them job, after job. Eventually the server stopped refusing connections. The easiest way to tell if you have too many connections (on the server) is to right click Computer --> Manage --> System Tools --> Shared Folders --> Sessions. This will list anyone connected to the server. Hope this helps! 1
Richard_Artes Posted November 2, 2012 Posted November 2, 2012 I also had exactly the same message. After some digging around I noticed the System Clock was 5 minutes out!!! N:\>w32tm /query /source Free-running System Clock N:\>w32tm /config /manualpeerlist:time-a.nist.gov,time.nist.gov The command completed successfully. N:\>net stop w32time The Windows Time service is stopping. The Windows Time service was stopped successfully. N:\>net start w32time The Windows Time service is starting. The Windows Time service was started successfully. N:\>w32tm /query /source Local CMOS Clock N:\>w32tm /query /source time-a.nist.gov,time.nist.gov
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now