Stupid printer problem
 

I have a xerox docuprint 4512 printer, which makes me mad.
The printer is connected to the network via a NIC, and I created a printer spool for it on a unix server which is on the same subnet where the winXP clients are located.
Now local unix users can print to the printer via the spool, but the same users cannot print to it if they try it from a winXP client.

What is most strange is the fact that yesterday everything was OK, although then the printer was connected to the network in an other subnet.
So, when the printer was on an other subnet, the winXP clients could print to it; now when it is on the same subnet where the clients are, they suddenly cannot. Meanwhile the printer spool did not changed, it was on the same server in both cases.

I suspected that it may be a samba issue, but it should not be, since the same users could use the same spool yesterday.

Anyone has an idea why this happens?

I must correct myself a little bit:
Sometimes the job just sleeps in the spool even if it was started by a local unix user. But sometimes it is printed.
This never happened when the printer was connected outside the subnet.

This subnet is protected by a firewall.
Is it possible that the firewall blocks printing requests sent to the printer, even if the request comes from machines on the same subnet?
Whilst the same firewall does not block printing to printers outside this subnet (and firewall)?

Latest finding: the printer cannot be pinged from hosts outside that subnet while other hosts on the same subnet can be pinged from the outside.

So, maybe a misconfiguration?

I was the greenest newbie not the printer stupid.

So the solution was:
put the IP address of the printer into /etc/hosts.lpd.