I have searched for this problem and have found similar, but no solution. I have an HP 1055CM DesignJet printer that was originally connected via hardwire. We do not print through a server but directly through TCP/IP port using a static IP address. It worked for years with no problems. We then had to move the printer to a location that had no easily accessible hardwire. We came up with this wireless solution:
1)We have one wireless Access point(1) in AP mode that connects to a switch that eventually connects to the server and network.
2) We have another Access Point in AP client mode that points to the MAC address of the AP mode Access point. It only talks to the AP(1).
3) We have a switch that connects to the AP(2) and we plug the HP 1055CM printer into that switch.
I know the wireless works as I can use wireless computers fine with this configuration and I have also connected another device to the switch that connects to AP(2) and it works OK also.
We can also print to the printer OK at times. The problem is that after awhile, the printer "drops" off the network. You cannot ping or do any kind of communication until you turn the printer off and then back on. After that all is well until it drops off again.
There is no "sleep mode" on the 1055CM other than "idle timeout". IDLE TIMEOUT - This is how long the HP JetDirect will wait before closing an idle TCP print data connection and per manual: Some software applications do not write a file terminator at the end of a file. In this case, the printer does not know when the file is complete and will wait for more data until the end of the "I/O Time-out" period. By default, this period is 30 minutes. You can change the time-out setting in the front-panel menu to as little as 30 seconds.
I have never had to change it from its current 90 second setting. Anyway, that does not seem to have any bearing as it is set for 90s and the the printer does not drop connection until after at least hour or more of inactivity.
I know this is a lot of info, but just wondering if anyone has any ideas.
Thanks,
1)We have one wireless Access point(1) in AP mode that connects to a switch that eventually connects to the server and network.
2) We have another Access Point in AP client mode that points to the MAC address of the AP mode Access point. It only talks to the AP(1).
3) We have a switch that connects to the AP(2) and we plug the HP 1055CM printer into that switch.
I know the wireless works as I can use wireless computers fine with this configuration and I have also connected another device to the switch that connects to AP(2) and it works OK also.
We can also print to the printer OK at times. The problem is that after awhile, the printer "drops" off the network. You cannot ping or do any kind of communication until you turn the printer off and then back on. After that all is well until it drops off again.
There is no "sleep mode" on the 1055CM other than "idle timeout". IDLE TIMEOUT - This is how long the HP JetDirect will wait before closing an idle TCP print data connection and per manual: Some software applications do not write a file terminator at the end of a file. In this case, the printer does not know when the file is complete and will wait for more data until the end of the "I/O Time-out" period. By default, this period is 30 minutes. You can change the time-out setting in the front-panel menu to as little as 30 seconds.
I have never had to change it from its current 90 second setting. Anyway, that does not seem to have any bearing as it is set for 90s and the the printer does not drop connection until after at least hour or more of inactivity.
I know this is a lot of info, but just wondering if anyone has any ideas.
Thanks,
