print server

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a new install of xp pro sp2 with all updates, tried to make it a print
server on my domain with 5 printers and 45 user machines. All worked fine for
about the first 2 hours now if I do not reboot every hour users are unable to
print and I can not install any new machines, after reboot all is well. I ran
the network diag from the print server, no red problems. I can ping all
machine to and from the print server. Something seems to be filling up and
gets reset with reboot? Open to Ideas?? Please Help?? The errors I get are
different-cannot connect -check if printer is on line-RPC Error
 
right! got that but users print and the sessions never end the first 10 users
grab the sessions then the XP "print server" serves no more until I close the
session manually. Been searching the MS web for an answer and tried to apply
autodisconnect which did not seem to effect the problem. I thought they
should tie up print$ and the users are taking IPC$ and not closing after they
are done printing.
--
jrdregs


Alan Morris said:
XP pro only supports 10 client connections


--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

jrdregs said:
I have a new install of xp pro sp2 with all updates, tried to make it a print
server on my domain with 5 printers and 45 user machines. All worked fine for
about the first 2 hours now if I do not reboot every hour users are unable to
print and I can not install any new machines, after reboot all is well. I ran
the network diag from the print server, no red problems. I can ping all
machine to and from the print server. Something seems to be filling up and
gets reset with reboot? Open to Ideas?? Please Help?? The errors I get are
different-cannot connect -check if printer is on line-RPC Error
Click to expand...
Click to expand...
 
Does win2k work better then XP as a print server? (temporary) Was using a Nt
machine and I am trying to get rid of it, driver issues. There must be a way
to close the connections sooner after no traffic, printing.
 
RPC connections stay open until the applications that call the remote
spooler are closed.

Have your users exit their applications from which they printed and you will
see the disconnections at that time.
 
Back
Top