Windows Server 2003 printer problem

Soldato
Joined
18 Oct 2002
Posts
8,920
when the printer has been left idle for a while some of the network printers stop responding, the server doesnt go to sleep or anything. it locks and the screen goes off. the problem doesnt happen with any consistency either.

im using HP Laserjet2600 connected directly to the network and installed on the server.

i get this error

Clerkin-error.JPG


when i click ok, the printer goes back to normal after a minute or so.

any ideas?
 
I don't suppose your printer is set up to get an IP address from the DHCP server?

If it is, give it a static IP outside the DHCP range and also check the gateway IP address on the printer.

Andy
 
madman045 said:
I don't suppose your printer is set up to get an IP address from the DHCP server?

If it is, give it a static IP outside the DHCP range and also check the gateway IP address on the printer.

Andy

i allowed it to pick up a ip from the dhcp and then reserved it afterwards. i'll check the gateways as i probably didnt configure them.
 
printers seem to have picked up everything from the dhcp.

i have 2 servers running here, ips are allocated drom the dhcp on server 1 but the printers are installed on server 2. could this be the reason?
 
Clerkin said:
printers seem to have picked up everything from the dhcp.

i have 2 servers running here, ips are allocated drom the dhcp on server 1 but the printers are installed on server 2. could this be the reason?

Always a possibility, I would try it with a static IP, it's usually best to keep network resources with static IPs.

Andy
 
I want to keep an eye on this thread, as we have a similar setup at work.

Did you install the HP Software on the server that came with the printers?
 
We have a HP Laserjet 2600n at work ... set up using DHCP (static lease), JetDirect over TCP port 9100, shared and published in Active Directory, no problem at all. No nasty HP software installed.

edit: Unrelated story:

an interesting problem I had with a Kyocera the other day ... it's set to DHCP, static lease from DHCP server. However, before it even sends a DHCP discover packet, it ARP's for the existance of an APIPA address (169.254.0.0/16), Microsoft style. Normally that'd fail to get a response, it'd know the IP isn't in use, then it'd figure out that it really wanted DHCP (bad coding) and get a DHCP lease. However (this is the interesting bit), we have a VPN setup to a client in the states, and their router on our premises was responding to the ARP requests for IP's in the 169.254.0.0/16 subnet, replying with the VPN router's MAC address, so that the printer thought that EVERY IP address in the 169.254.0.0/16 range was taken, and would go into an infinite loop checking random IP's in that range. :rolleyes:
Linux's ebtables MAC-level firewall saved the day. :p
 
Last edited:
still getting this problem :(

set up with static ip now. gatway and subnet mask all set up too. still getting that error in the op everynow and then.

to the poster that set it up over port 9100. what do you mean by that? im not that up on ports etc. ive got it set to a hp standard tcp/ip port that is the ip address of the printer.

edit: just looked at ports, it is on port 9100. thats the raw port. i see now.

still got problem though
 
Last edited:
Back
Top Bottom