Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Waiting for printer port?

Status
Not open for further replies.

Seabz420

IS-IT--Management
Joined
Jul 14, 2003
Messages
129
Location
CA
Has anyone seen this message in their print queue before? We have numerous printers attached to Lexmark Marknet X2031e's. Once in a while, a printer will stop printing. The lights on the marknet show the data has gone from the server to the marknet but not to the printer. We usually just cycle the power on the marknet and away we go. Not now! Now, in the print queue on our Win NT 4.0 server, we get a message under status "Printing - Waiting for printer port"? I've recreated the printer port for that printer but nothing seems to be working. The funny thing is that this was happening when we had an old server in this office. Now we have a new server (soon will run Server 2003) but the same problem exists. Lexmark hasn't heard of it and Microsoft hasn't neither. I hope that actual users have seen this! Thanks!
 
We had the same problem (Windows NT4 and Lexmark Printers).

The problem seems to come from the Lexmark software on the server (We were able to print from a windows 2000 system with a printer installed as "local" and printing on a standard network TCP/IP port directly to the network printer).

The problem was solved by stopping and restarting the "Lexbce Server" service (The "Spooler" service must be stopped to be able to stop the "Lexbce Server" service).

 
Here is a recap:

We had 3 Lexmark Marknet x2031e's that were not sending print jobs to the printer. The server showed the status of "waiting for printer port".

Solution:

Marknet 1 - bad marknet, replacement works just fine (we replaced with once before with a new one but must have been DOA from the box)

Marknet 2 - bad network cables. Tested the cables and the marknet was using a bad one. Replaced cable and works.

Marknet 3 - bad network cables. I give a big :P to the managment who decided a regular electrician can do the network cable work!

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top