this post was submitted on 15 Aug 2024
48 points (92.9% liked)

Mildly Infuriating

35045 readers
1 users here now

Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.

I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!

It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.


Rules:

1. Be Respectful


Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.

Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.

...


2. No Illegal Content


Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.

That means: -No promoting violence/threats against any individuals

-No CSA content or Revenge Porn

-No sharing private/personal information (Doxxing)

...


3. No Spam


Posting the same post, no matter the intent is against the rules.

-If you have posted content, please refrain from re-posting said content within this community.

-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.

-No posting Scams/Advertisements/Phishing Links/IP Grabbers

-No Bots, Bots will be banned from the community.

...


4. No Porn/ExplicitContent


-Do not post explicit content. Lemmy.World is not the instance for NSFW content.

-Do not post Gore or Shock Content.

...


5. No Enciting Harassment,Brigading, Doxxing or Witch Hunts


-Do not Brigade other Communities

-No calls to action against other communities/users within Lemmy or outside of Lemmy.

-No Witch Hunts against users/communities.

-No content that harasses members within or outside of the community.

...


6. NSFW should be behind NSFW tags.


-Content that is NSFW should be behind NSFW tags.

-Content that might be distressing should be kept behind NSFW tags.

...


7. Content should match the theme of this community.


-Content should be Mildly infuriating.

-At this time we permit content that is infuriating until an infuriating community is made available.

...


8. Reposting of Reddit content is permitted, try to credit the OC.


-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.

...

...


Also check out:

Partnered Communities:

1.Lemmy Review

2.Lemmy Be Wholesome

3.Lemmy Shitpost

4.No Stupid Questions

5.You Should Know

6.Credible Defense


Reach out to LillianVS for inclusion on the sidebar.

All communities included on the sidebar are to be made in compliance with the instance rules.

founded 1 year ago
MODERATORS
 

I got a new printer. Auto-discovered, added, and prints fine from Windows in 2 minutes. Auto discovered, added, and prints fine from OSX in 30 seconds. Auto-discovered and added on Linux, but trying to print results in "printer is unreachable at this time" - even after 50 re-installs, different configs, different drivers, different protocols.

I recognized that some computers were on different subnets, but couldn't figure out a pattern. It turns out that the printer has a setting called "Restricted Server List" and the default setting is null. Here's its description in the admin interface: "Comma-delimited list of IP addresses that are allowed to make TCP connections. Example: 157.184.0.0/24. where 0 is a wildcard and /24 is the network prefix."

It also has a setting called "Restricted Server List Options", set to block all ports by default. Here's its description: "By default, addresses not in the restricted server list will have all access blocked. When Block Printing Only is selected, addresses not in the restricted sever list will be blocked from printing only. When Block Printing and HTTP Only is selected, addresses not in the restricted server list will be blocked from printing and HTTP. "

Admin interface doesn't say this anywhere, but the default setting of no restricted servers apparently allows access from other networks, but not from the same network as the printer. I set the restricted servers to "192.168.132.0/24" and then I could access the printer admin web page and print to the printer from my Linux box, but not from any of the computers that were working before. So I set it to "192.168.0.0/16" and every computer on all subnets in my house can print and access the printer admin.

The default setting of no restricted servers was extremely non-intuitive in that it actually only restricted servers on the same subnet. And there was no such documentation.

What a crappy waste of 7 frickin' hours!

top 23 comments
sorted by: hot top controversial new old
[–] [email protected] 20 points 2 months ago (1 children)

Correct me if I’m wrong, but this was 100% caused by printer settings conflicting your LAN topology and has nothing to do with Win/Mac vs Linux, right?

[–] [email protected] 1 points 2 months ago
[–] [email protected] 13 points 2 months ago (1 children)
[–] [email protected] 2 points 2 months ago (1 children)

“Paper jam detected in tray 1”

[–] [email protected] 2 points 2 months ago (1 children)

That's probably too clear of a message for a printer.

[–] [email protected] 1 points 2 months ago

“PC LOAD LETTER”

[–] [email protected] 12 points 2 months ago* (last edited 2 months ago) (2 children)

I feel you. I spent an hour yesterday trying to figure out why half of my prints from my phone were cut off along the top edge of the page.

Turns out my phone defaults to A4 when printing and there's no way to set the default to US Letter so I have to do that for every single print.

[–] [email protected] 6 points 2 months ago

Oh god, I used to work IT for a company that had a European office so users getting documents set to A4 was not unusual. The problem came when they tried to print one of those documents and the office printer would sit and complain that it didn't have any A4 available and wouldn't print anything in the queue until that was fixed. And of course users had no idea there was any difference between letter size and A4.

[–] [email protected] 2 points 2 months ago (1 children)

Coincidentally, i constantly get documents randomly default to the US letter, which I don't even know what it means. I only ever seen A4 in my life. Annoying as hell.

Have you considered that you're a victim of a default country syndrome?

[–] [email protected] 0 points 1 month ago

they wanted to be able to CHANGE the default

[–] [email protected] 7 points 2 months ago

Every bloody single thing with printers is wrong, shitty, filthy, disgusting, assumptive, braindead, idiotic, and it makes me wonder if the printer industry only recruits people who are outsmarted by a pile of green potatoes.

So... OP, if it's any consolation, I know that feel. It is infuriating.

[–] [email protected] 3 points 2 months ago (1 children)

On linux: I take a printer, plug it in, it gets autodiscovered and prints. On windows: I spend forever doing random shenanigans to get it working.

Same goes for hardware upgrades, bluetooth headphones, etc etc.

I dunno what you're doing wrong. Maybe the distro? Any flavor of Ubuntu should work with most supported peripherals at zero effort. If it doesn't, it means the device manufacturer never bothered with a driver for linux and you're completely out of luck.

[–] [email protected] 2 points 2 months ago

The absolute most problem I have with printers and Windows is setting the adapter and printer settings.
Double so if I need it to configure uniformly across multiple systems.

Can't say I share your issue.

Now don't get me started about configuring a printer on a mac. Holy fuck is annoying to print stuff if you are not used to iOS/MacOS

[–] [email protected] 2 points 2 months ago

Sir, this is Wendy's

[–] [email protected] -5 points 2 months ago* (last edited 2 months ago) (3 children)

With gratis Linux we pay with our time. You did very good to go through all this hell in a mere 7 hours. Programmer creating those monstrosities don't understand our mundane concerns.

P.S. : still Linux has qualities that makes it superior in many ways.

[–] [email protected] 7 points 2 months ago* (last edited 2 months ago)

The problem as described has nothing to do with Linux.
It was a default printer setting that blocked access from all computers in the same network.

[–] [email protected] 2 points 2 months ago (1 children)

All of these replies made me feel a little bit better, but yours especially resonated with me. Thanks.

[–] [email protected] 1 points 2 months ago

Great post ! i felt my past Linux experiences where quite normal while reading it. So, thanks to you.

[–] [email protected] 1 points 2 months ago (2 children)

Honestly, this is a pretty good example of why this isn't an inherent Linux problem. It's a problem of using any OS that isn't popular enough to be supported by manufacturers. More people using Linux would cause problems like this to stop happening.

I realize that's a distinction without a difference to a lot of people, and that's totally okay. I'm not saying that's wrong, but it matters to me that the benefits of Linux are specific to the OS, while most of the problems are not.

[–] [email protected] 8 points 2 months ago (1 children)

None of this has anything to do with the operating system of the devices trying to use the printer.

[–] [email protected] 1 points 2 months ago

Huh, yeah, you're right. I missed that the first time, but it's how the computers are networked, not the OS.

[–] [email protected] 2 points 2 months ago (1 children)

More people using Linux would cause problems like this to stop happening.

i say the designers + programmers made it so and you say users made it so. ... it seems we disagree here.

[–] [email protected] 2 points 2 months ago* (last edited 2 months ago)

No. That's not what I said. I said the manufacturers not testing their equipment on Linux made it so, and more users would change that. Actually, looking at it again that isn't even true. This example has nothing to do with the operating system at all. It's caused by connecting with a computer on a different subnet (or I guess more accurately the same subnet as the printer), which would have happened even if the OS were Windows.