Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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)?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.