Page 1 of 1

Printing to WIN:/IP_###.###.###.###

Posted: Thu Oct 01, 2009 8:05 am
by GomezL
We have a single user with 1 workstation that periodically has problems printing.

The user is printing to WIN:/IP_###.###.###.###

Generally speaking the print job works perfectly.

Occasionally the print job simply doesn’t print.

The user noticed that this “Pop-Up Window” that says printing to windows does not happen in these cases.

We also found that the WBSPL###.## does not get delete, and it contains the print job.

My thought is that when we issue CLOSE#255: some windows error is causing the print job to fail, but we don’t have any way to know there was a problem.

Any thoughts?

Posted: Thu Oct 01, 2009 8:12 am
by John
Sounds like the old ECP Printer Port issue.

http://support.microsoft.com/kb/141919

-John

Posted: Thu Oct 01, 2009 8:17 am
by Susan Smith
John,

Aren't ECP ports always parallel? Is this a parallel printer that Luis is having trouble with?

-- Susan

Posted: Thu Oct 01, 2009 9:02 am
by GomezL
It does sound like the ECP problem, except that the printer is an IP Based Windows Printer using NWP.

The other strange behavior is the user does not receive any message that there is a problem, the print job just doesn't print.

Posted: Thu Oct 01, 2009 9:09 am
by dmeenen
Strange problems with printing are sometimes resolved by going into the Antivirus program and exclude the BR folder, and other associated folders that BR uses,
and
the C:\windows\system32\spool directory.

Norton, LightSpeed, TrendMicro especially have this abnomally.