@peppyy :-
Umm.....right. O-kay.
One very common "misconception" here:-
peppyy wrote: Sun Dec 10, 2023 10:25 pm
I will look into if the epson ecotank will accept requests from port 9100. It appears that it will not accept a request from this port from a remote computer, I already have found that there is a problem on port 631 via cups.
It's not the printer itself that decides whether or not to accept port requests. All your printer does is to accept a formatted print-job sent to it from the the CUPS print-spooler (the bit that 'queues', formats - via the driver PPD file - and sends print-jobs off to the correct destination). It's CUPS that decides whether to accept a port request or not..... 
Anyways. Well, you're on the right track with what you've tried so far, but from the sounds of things you may have got a wee bit ahead of yourself, or maybe missed a step out, somewhere along the line. It's nowt to be ashamed of; it took ME a few tries at setting up p910nd before I had it behaving itself.
I find with all this sort of stuff that it pays to be very, VERY methodical about things. Take it one step at a time, and make sure that step is fully-functional - and doing what you expect it to do - before moving onto the next one.
The first step is to get the sharing mechanism installed, set-up and functioning correctly. At this point, you're not interested in the printer at all; you're putting background mechanisms in place that allow what you want to happen, TO happen.
Install p910nd at both ends; both on the client (the machine you want to print FROM) and the server (the machine that actually runs the printer). Once installed, bring up the GUI and use it to turn the server ON. Repeat this on both machines. (You can set it all to start at boot, but you can leave this step until after you've got it functional).
Now; next step is to ensure both firewalls are disabled while you're checking things out and setting everything up. You can add an exception for port 9100 in the firewall later, if desired; for now, it's simpler just to turn 'em off.
Okay. On the client machine, run Peasyport to check that port 9100 is in fact open on the server. It should be, but it never hurts to check. Assuming it is, you can now proceed to play around with the printer itself.....
I have to assume here that the machine that's going to be the print server - your wife's 'puter, yes? - has the printer all set-up and functional as a 'local' printer. That being the case, the next thing you need to do is to turn printer sharing OFF. Yes; I know it sounds counter-productive, but since in this case p910nd is controlling the share mechanism via port 9100, having the CUPS share mechanism enabled is actually getting in the way, is confusing the issue and isn't needed anyway.....because you're not sharing via port 631 as you would normally.
Now; it's time to "install" the remote printer at the client end. Before you go any further, if there's any other printers 'installed' apart from the local one that you're using, delete 'em. Very important we begin with as clean a sheet as we can.
Okay. Use "Add Printer"; "Find new printers" won't do anything because there's nothing for it to find (you've turned printer sharing OFF, remember?) Check the "AppSocket/JetDirect" option, then hit "Continue".
So; ya need the IP addy of the print server. In my particular case - using my current Pup as an example; this is Tahrpup64, with a static IP at present of 192.168.1.60 - this will be entered on the next page as
You'll enter your own IP addy in a similar fashion. Hit "Continue".
On the next page, give it a name, description, and location, etc. (Leave that 'Sharing' check-box ALONE. We don't want it!) Hit "Continue".
Add your driver. This needs to be the same architecture as the client; it's perfectly possible to send stuff to a 32-bit OR 64-bit print server, and to do so from either a 32-bit OR 64-bit client. Just make sure to use the right drivers for the client's architecture; when I originally obtained my Epson drivers through openprinting.org, many years ago, I made sure to get both arches. I didn't run a 64-bit Pup at the time, but I knew I probably would, sooner or later.
Moment of truth time. Test it out. It's no good trying to use "Maintenance -> Print test page", because CUPS immediately tries to send this via the standard port 631 interface....which of course fails, because you're now not set-up to do it the 'default' way. So; just try to print off a short text document, via Leafpad or Geany, or similar. Doesn't need to be fancy; all you need to do is prove that what you send is printed-off at t'other end.
What happens?
Mike. 
