Lanier MP CW2200 not printing from brand new Windows 10 Pro 64 bit PC's

**ilivetocollate** · 11-16-2019

Have 2 brand new HP PC's with Windows 10 Pro 64, feature release 1903, installed using Windows Media Creation Tool. They will not print to the Lanier MP CW2200. Basic Windows Print Test Page errors out or result in a paper jam message, as does PDF print jobs. The data light will flash at the Lanier and the job acts like it's processing, but after some time, the data light stops and the job just disappears; we're not implementing the User Code authentication feature. Spent much time with a Lanier guru out of Atlanta and was able to make paper come out, but it comes out blank or with a 'syntax' error. Have done resets and updated all firmware for the engine, network, etc. Older computers in the building with Windows 7 print just fine..it's only these two new systems, but these new systems print to other network printers just fine. I'm using the correct driver, correct IP address (I have 30 years experience in IT). My thought is perhaps there is some incompatibility with these brand new 10 systems and the Lanier MP CW2200. Has anyone encountered this or otherwise similar issue?

**Phil B.** · 11-16-2019

Originally Posted by ilivetocollate

Have 2 brand new HP PC's with Windows 10 Pro 64, feature release 1903, installed using Windows Media Creation Tool. They will not print to the Lanier MP CW2200. Basic Windows Print Test Page errors out or result in a paper jam message, as does PDF print jobs. The data light will flash at the Lanier and the job acts like it's processing, but after some time, the data light stops and the job just disappears; we're not implementing the User Code authentication feature. Spent much time with a Lanier guru out of Atlanta and was able to make paper come out, but it comes out blank or with a 'syntax' error. Have done resets and updated all firmware for the engine, network, etc. Older computers in the building with Windows 7 print just fine..it's only these two new systems, but these new systems print to other network printers just fine. I'm using the correct driver, correct IP address (I have 30 years experience in IT). My thought is perhaps there is some incompatibility with these brand new 10 systems and the Lanier MP CW2200. Has anyone encountered this or otherwise similar issue?

well really more info needed:
what size/type of paper does the computer says is in the tray.. same on copier..

I take you are printing via enet cat 5e or 6..
are there lights on the Lanier NIC card?

what are the print/network settings on the PC's?

look in your printers/devices..

click on the printer you just installed

find out what driver was installed

if it is a WSD go to Lanier website and get the Lanier driver for your machine

install / test

**ilivetocollate** · 11-16-2019

Originally Posted by Phil B.

well really more info needed:
what size/type of paper does the computer says is in the tray.. same on copier..

I take you are printing via enet cat 5e or 6..
are there lights on the Lanier NIC card?

what are the print/network settings on the PC's?

look in your printers/devices..

click on the printer you just installed

find out what driver was installed

if it is a WSD go to Lanier website and get the Lanier driver for your machine

install / test

The Lanier and PC set to use 24x36 from Roll/Tray 1

Using CAT5e and there is an amber light on the Lanier NIC

Print/network settings are Standard TCP/IP port, not using WSD. Protocol is Raw; port is 9100; SNMP is enabled.

Driver is Postscript3 driver version 1.3.0.0 for Windows 10 64 bit

**slimslob** · 11-16-2019

I would advise that you double check that some type of user authentication is not implemented. The data light flashing and then no print is the classic symptom of an authentication violation. Syntax error usually is a driver problem. Check the error log on the Print Function screen as it may give some additional information. Also what software are you using. I have encountered cases where it was necessary to install Ghostscript on the computer. This is often the case when they are trying to print construction diagrams downloaded from the internet as those diagrams a often generated with Ghostscript.

**ilivetocollate** · 11-17-2019

Originally Posted by slimslob

I would advise that you double check that some type of user authentication is not implemented. The data light flashing and then no print is the classic symptom of an authentication violation. Syntax error usually is a driver problem. Check the error log on the Print Function screen as it may give some additional information. Also what software are you using. I have encountered cases where it was necessary to install Ghostscript on the computer. This is often the case when they are trying to print construction diagrams downloaded from the internet as those diagrams a often generated with Ghostscript.

I've verified that user authentication is not being used. The error log has nothing in it. The software being used is Adobe Acrobat Reader DC, Chrome, Edge, and the Windows Print Test Page. I replaced two other computers this past July that do not need to print to the Lanier. As a test, I loaded the driver and am getting the same result as the two brand new systems I put in a few days ago. These systems have the commonality that they all started with the 1903 version of Windows 10 Pro 64 bit. I setup one of the old Windows 7 systems to share its Lanier and I can print that way, but it is painfully slow.

This is interesting: On the old Windows 7 systems that work without issue, I can print a Windows Print Test Page quickly. I notice the job size reported in the 'See What's Printing' queue window is '6.00MB/9.00MB' and disappears quickly. On the new systems replaced a few days ago and others this past July, the size is '5.99MB/5.99MB' and sits there until it bombs out. The new systems are all HP EliteDesk 800's with 8GB RAM and 256SSD, and, for the sake of perspective, work flawlessly for all the other functions they perform; running apps, printing to the Canon iR-ADV C3325 via ethernet, etc.

On another note, I am thankful and appreciative of the help here....

**totoro** · 11-17-2019

Is the firmware up to date? Wasn't there something about setting the paper type to the one like " no display " ? I thought it was a glitch in the 2200 that they fixed in the 2201.

**ilivetocollate** · 11-17-2019

Originally Posted by totoro

Is the firmware up to date? Wasn't there something about setting the paper type to the one like " no display " ? I thought it was a glitch in the 2200 that they fixed in the 2201.

Firmware has been updated for all of the component areas; engine, network, etc.

**sandmanmac** · 11-17-2019

How about trying a different IP Address?
Enable DHCP on the machine and then use the IP address that the machine settles on.
I've done 2 installations in the past 6 months or so where I upgraded machines with basically newer versions of their previous one. I initially used the IP address of the previous unit, which is what I typically do and often don't even bother installing the specific drivers. But in these cases none of the PC's would print even with the proper driver installed. I tried PCL 5, Pcl 6 and even the dreaded universal driver. Only when I enabled DHCP, and then locked in the IP address that the machine chose, would it print.
Very strange, and I have no explanation for it.
Worth a try......

**ilivetocollate** · 11-17-2019

Originally Posted by sandmanmac

How about trying a different IP Address?
Enable DHCP on the machine and then use the IP address that the machine settles on.
I've done 2 installations in the past 6 months or so where I upgraded machines with basically newer versions of their previous one. I initially used the IP address of the previous unit, which is what I typically do and often don't even bother installing the specific drivers. But in these cases none of the PC's would print even with the proper driver installed. I tried PCL 5, Pcl 6 and even the dreaded universal driver. Only when I enabled DHCP, and then locked in the IP address that the machine chose, would it print.
Very strange, and I have no explanation for it.
Worth a try......

I'll try that specific approach. I did set a static IP to test with, to no avail, but it wasn't the DHCP assigned address....Thanks.