I Can No Longer Map A Printer On Windows 2000 Machine

[Arsynic]

This is only happening on one server. I'm using Terminal Services to map to a printer connected to a remote Windows 98 machine. We do this because our users connect to the Terminal Server to access a DOS database at the remote site. We map the printer to allow the users to print reports from the server locally. This week I've been having problems with the server not being able to connect to the printer. When the batch script runs:

net use lpt1: \\computername\printername

I get system error 67 network name cannot be found.

The name is right for both the printer and computer. I can't even ping Windows 98 clients from the Terminal Server but I can ping 2000 clients and map to their printers fine. This is the only server where this problem exists. I can map to Windows 98 printers from the other 5 terminal servers (but I still cannot ping 98 clients, but printing is my main concern).

What could be the problem.

 

[JeffG2583]

Maybe try replacing the computer name in your net command with the IP address of the machine attached to the printer?

 

[Arsynic]

Did that earlier, no such luck. On investigation I found out that the WINS service isn't running on the server and there's all kinds of crap going on. So I'll just repair Windows after the break.