|
|
|||||||
I am haveing a problem with the AddPrinter Connection Command. It is returning a error(17220-The RPC Server is unavailable). Is this the RPC server on the PDC or the RPC server on the print server? Also which service would it be The RPC locator, or just the RPC server itself? Thanks |
||||||||
|
|
|||||||
client OS? usually it would mean the RPC on the print server, but if you are on a win95, it may be a kxrpc server error |
||||||||
|
|
|||||||
The server that you are trying to map the printer to. The error may also be caused by the SPOOLER service being down or unresponsive. |
||||||||
|
|
|||||||
Client OS = WinNT 4.0 problem is occuring speradicly across only SOME machines. Print Server = Win2K Print server has RPC service enabled. Client machine also has the RPC service running. Any Ideas. Only other idea I can come up with is network timeouts. Thanks. |
||||||||
|
|
|||||||
Quote: I assume this is the same network that is discussed in execution time As I said in that thread, you have a problem with network optimization. |
||||||||
|
|
|||||||
Yes this is the same network. However, pings to the server are under 10 msec. I am almost thinking that it is another plant on our network that is not 'optimized'. Our machines were originally 'optimized' by someone who originally knew more aout Novell than I. We are still in the long transition away from Novell though. The Client and IPX will be removed from all machines eventually. (As soon as I can get all the printers converted and application images moved over). The network issues we are haveing now did not exists until the networks between the company that bought us(entitely MS shop) and ours was connected. So I am figureing from this that there may be something on the 'connected' side instead of ours. Or even a incompatilibility between them. But I admit that that is WAY BEYOND my knowledge as I do not know all the network configs on the 'global' network. |
||||||||
|
|
|||||||
well, are you part of that domain now? do you have nameservers on your own site or are you heavily pulling from that possible mother ship? etc etc... all about the network it seems. |
||||||||
|
|
|||||||
The only resources we have local is a file/print server. a BDC, an email server and a backup email server. Everything else is from the WAN, so I would have to say we pull Heavily from the 'mother ship' |
||||||||
|
|
|||||||
you could simply try something like using addprinterconnection with ip instead of servername. |
||||||||
|
|
|||||||
Quote: That is not a measure of client optimization. Quote: Therein lies your problem. A Novell guy will optimize for NetWare, not MS. The problem is at the client, not the cable plant. |
||||||||
|
|
|||||||
Interesting idea. I will have to try that. I did not think of that idea. |
||||||||
|
|
|||||||
This has been tracked down to a common thread thanks to a coworker of mine. A printer that was added to the win2k server with difficulty yesterday, was deployed. This was figured out by it only affecting the machines that had this printer. On the machines that have this happening the spooler is gpfing. At current I am wondering if it was the driver that was pushed down to the machines. And if it is, how can I delete the driver? Any pointers? |
||||||||
|
|
|||||||
Just as a completion to this thread. This was a printer driver problem. I used the instructions from the MSKB to remove the printer drivers manually. That fixed the issue. Many thanks for all the ideas and help. |