I just recently purchased two HP P1505n printers where one is to be used as a USB printer to one workstation and the second one is to be used as a network printer for two workstations nearby. There was no troubles installing the USB Printer or the Network printer onto the workstations however the two workstations connected to the network printer seem to loose communication with the printer every 30 min or so. The only way to resolve this is to power off and on the printer, from that point it receives all print jobs for he next 30 min or so. The Printer is set with a manual IP on the office network since there is no DHCP Presently active to supply an IP address. When communication is lost to the printer I have attempted to ping the IP address assigned and it gets a reply back with no troubles, I can also access the internal imbedded website of the printer during these times, its just the print jobs sit at the workstations stating "Document Failed to Print" I contacted HP and was informed to attempt a direct connection through USB to one of the workstations to see if the printer is dropping the connection or the network is. At this point I swapped the two printers so that the one that was being used through USB is now the network printer and visa versa. The new network printer is having the exact same issue and the old network printer is showing no errors when connected through USB. I Updated the firmware of the printer and updated the drivers on the workstations with the latest version from the HP website. Issue still continuing. I contacted our network suppliers since they have full access into the Cisco Switches that are the backbone of our network. They inform me that they can see the print requests going out onto the network and being sent off to the printers with no filtering or blocking. At this point I have ran out of ideas on points of possible trouble and am looking ofr suggestions. My Google search pulled up a similar issue with different models of the HP Printer. In the troubleshooting they found it would be resolved by opening a telnet session to the printer and changing the "SLP Config" value to "1". Unfortunatly this solution solved the issue with a higher model then the P1505n printers. I attempted to telnet into the printer but was unsuccessful through any port other then port 9100 in which nothing appears in the telnet window to allow me to change any printer settings. The internel imbedded webpage does have a checkmark box for SLP Config however the issue still continues no matter if the box is checked or not. So to recap: *Printer looses communication with Windows to receive print jobs every 30 min or so. *Still able to ping printer and access imbedded webpage of printer during down time *Swapped printer with no result *Network support states no filtering or blocking showing in Cisco switches *Telnet session to port 9100 shows blank with no way to check SLP settings. *Updated firmware and drivers are being used. Any suggestions would be greatly appreciated.

I forgot to add, when I telnet into the printer through port 9100 and type anything in the session window, although it does not display in the telnet window, when I close the window it does print on the printer. To me that would mean that the printer port on the printer itself is not getting jammed up, but that would be a guess. Also when the printer drivers were installed on the workstations, the port was assigned as a "HP Standard TCP/IP port". Once again, any direction or possible fixes would be great... Thanks,

I'm having a nearly IDENTICAL issue. In our network, however, 3 of 4 computers never have trouble printing; only 1 does. And... this machine doesn't give any errors. The print job goes away without error, but nothing prints. This same workstation can access the internal web server just fine... and it used to print until I updated the printer drivers. Rolling back did not fix it. Yeah -- $199 for a network printer is a great deal... until we spend multiple hours trying to make it work. Hopefully someone else will have solved the issue, because HP can't.