Remote printing, lpstat shows waiting for server to come up

[vodkadrinker]

This is a remote printer on a Win2k server it was working fine but now on an lpstat it is showing the following.

win2klpd:
queuing is enabled SCOSERV:
waiting for win2kserver to come up

All documentation tends to point to the Win2k machine however I can print from the windows clients fine.

Any idea's please?
VD

 

[PHV]

And what about

 rlpstat win2klpd

?

Hope This Help
PH.

 

[vodkadrinker]

Gives me the following...

$rlpstat win2klpd
SCOSERV: waiting for win2kserver to come up
Req-Id Owner Size Date
win2klpd-999 bob 2050 Sep 18 12:30
win2klpd-998 bob 2050 Sep 18 12:14

Windows 2000 LPD Server
Printer \\126.2.0.2\win2klpd

Owner Status Jobname Job-Id Size Pages Priority
------------------------------------------------------

I tend to think that the problem is not on the SCO end but on the Win2k end.

Thanks
VD

 

[Annihilannic]

Make sure the Microsoft TCP/IP Printing service is running on the Windows server.

Annihilannic.

 

[PHV]

Just my 2 cents: If this printer can be networked you can perhaps try to not go thru the Win2k server for printing from the unix box.

Hope This Help
PH.

 

[aseidas]

What is the share name of the printer on the windows machine? It appeards that lpd printing is installed on the ths server as you are getting a valid response from the service:
Windows 2000 LPD Server
Printer \\126.2.0.2\win2klpd

Owner Status Jobname Job-Id Size Pages Priority
------------------------------------------------------


you need to make sure your remote print queue name in /etc/printcap(rp=) matches the windows share name of the printer. In this case if your windows share name is not "win2klpd" this is your problem. Hope this helps.

-aseidas

 

[vodkadrinker]

I checked through what each of you suggested and everything seemed ok so I ended up rebooting the Unix server.

20 minutes later once the system was backup the printer started back into life.

It worked all this morning and then stopped again.

I forgot to say that this printer was configured months ago and has never been a problem before.

Is it possible to change the timeout and the number of retry.

Many thanks,
VD

 

[unix42]

make sure the :ex: option is NOT in the /etc/printcap file for this printer.

 

[vodkadrinker]

I have taken the :ex: extended option out but now it hangs with the following output on a lpstat -t...

win2klpd:
queuing is enabled SCOSERV:

I restarted the lpsched and the lpd process.

Many thanks
VD