Windows Forum

Ask something
Discussion Locked

NT 4.0 Printing

0 helpful
8 replies

by ndpro.knelson

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have an NT 4.0 network. My clients are running win98 se. One of my clients all of a sudden quit printing to a network printer. It has worked for years. They were trying to print something for the Internet when it quit. I get the error that the path doesn't exist for this printer. I have 10 other computers pointing to the same path and they work just find. Also any new computers get the same error. I'm unable to attach any new clients to this printer. Everything seems to be installed right. Like I said it has been working for years and all of the other Workstations print to it just fine. It is only these two computers.

8 replies

by avi_mohod

Hi,
It is not very clear that this problem is totally a software based or any hardware problem.It may poosble that these may not in network.I assume that u have check that this is not a network problem.As printer is printing from other computers there no problem in printer.What I think that problem is s/w based.What I think printer driver is currupted.First of all remove
print driver from trouble computer and again install it.Because it may be currupted due to virus.If this does not worktry to reinstall driver frim print server(a server which is doing spooling for ur network printer.Also check permission.Check also spooler service is working or not.
Try this hopfully will solve ur problem.
avi

by curlergirl

I would first try uninstalling and reinstalling the printer at the server. Make sure you have the most up-to-date drivers available. If this doesn't solve the problem, your print spooler files may be corrupted. Here's how you can try to fix that:
1. On the print server go to the \WINNT\system32 folder and rename (or delete) the following two files: spoolss.exe and spoolss.dll.
2. From another NT server, copy these two files back into the \WINNT\system32 folder on your print server.
3.Re-run the service pack (SP6a) and then reboot.
4. Check your RPC and Spooler services and make sure they're set to start automatically.

Hope this helps!

by ndpro.knelson

I figured out the problem. There is a novell server that this client log into also. Novell doesn't like long names for printers. So I shorten the printer name on the NT side and eveything works great.

This discussion is closed to new replies.