Opened 3 years ago

Closed 3 years ago

Last modified 5 weeks ago

#755 closed defect (wontfix)

term-printer is not visible in printer browser with OSX

Reported by: Hans Kuhn Owned by: hak@…
Priority: minor Milestone: ietf-090
Component: printers Keywords:
Cc: randy@…, sra@… My Current Location:
My MAC Address: My OS: OSX

Description

Both randy@… and sra@… can't see term-printer in the bonjour browser. I think we have the appropriate DNS entries to make dns-sd (wide-area) work, but I'm still investigating.

Attachments (2)

smime.p7s (3.7 KB) - added by Hans Kuhn 3 years ago.
Added by email2trac
Screen Shot 2014-07-21 at 4.31.48 PM.png (113.3 KB) - added by Bill Fenner 3 years ago.
Billo's mac on ietf-a sees term-printer under "Nearby..."

Download all attachments as: .zip

Change history (17)

comment:1 Changed 3 years ago by Hans Kuhn

Cc: randy@… added

comment:2 Changed 3 years ago by Hans Kuhn

Status: newaccepted

comment:3 Changed 3 years ago by llynch@…

Owner: changed from Hans Kuhn to ralfvin@…
Status: acceptedassigned

comment:4 Changed 3 years ago by ralfvin@…

Owner: changed from ralfvin@… to hak@…

comment:5 Changed 3 years ago by Bill Fenner

Do Randy and Rob have VPNs active? Wide Area Bonjour only works to your primary DNS search domain.

comment:6 Changed 3 years ago by Hans Kuhn

They claim no. I did ask about VPN.

On 7/21/14, 4:02 PM, IETF Meeting/NOC wrote:
> #755: term-printer is not visible in printer browser with OSX
> ---------------------------+--------------------------------
>        Reporter:  hans@…    |                Owner:  hak@…
>            Type:  defect    |               Status:  assigned
>        Priority:  minor     |            Milestone:  ietf-90
>       Component:  printers  |           Resolution:
>        Keywords:            |  My Current Location:
> My MAC  Address:           |                My OS:  OSX
> ---------------------------+--------------------------------
>
> Comment (by fenner@…):
>
>   Do Randy and Rob have VPNs active?  Wide Area Bonjour only works to your
>   primary DNS search domain.
>
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/755#comment:5>
> IETF Meeting/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting - NOC pages
>

smime.p7s

Changed 3 years ago by Hans Kuhn

Attachment: smime.p7s added

Added by email2trac

Changed 3 years ago by Bill Fenner

Billo's mac on ietf-a sees term-printer under "Nearby..."

comment:7 Changed 3 years ago by Bill Fenner

Cc: sra@… added

There's a MacOS X limitation that if you have an explicit domain search list configured, that it won't look for the dhcp-provided domain. While this provides for a bit of a bummer of a user experience, there's not a whole lot that we can do about it other than document it.

You *can* add by IP explicitly, use term-printer.meeting.ietf.org, and allow it to figure out the rest - there's still automagic stuff working there.

comment:8 Changed 3 years ago by Hans Kuhn

Billo solved the case of the missing printer. Way to go Billo!

It turns out that both Rob and Randy had manually overridden their DNS search path so OSX wasn't accepting the DHCP-offered search path, meeting.ietf.org.

I was unable to find a way to prepend the DNS search path, but I found some other interesting links that might amuse people.

http://www.makingitscale.com/2011/fix-for-broken-search-domain-resolution-in-osx-lion.html
http://spockwithabeard.blogspot.co.uk/2006/11/setting-dns-domain-search-path.html

comment:9 Changed 3 years ago by Hans Kuhn

Resolution: wontfix
Status: assignedclosed

comment:12 Changed 3 years ago by sra@…

Resolution: wontfix
Status: closedreopened
For some of us, letting the local DHCP server have any influence
whatsoever on a laptop's DNS search path is a non-starter.  When I
type a DNS name I want it to mean what I think it means, full stop.

Any service discovery mechanism which depends on DNS search paths is
broken by definition.

comment:13 Changed 3 years ago by Bill Fenner

Rob,

What action would you like the IETF NOC to take here?

Again, my proposed action is to document how to manually configure the printer, for the benefit of users for whom Apple's service discovery mechanisms are undesirable.

I do not think this is the venue in which to discuss how wide-area Rendezvous is broken.

comment:14 Changed 3 years ago by Bill Fenner

My apologies, I overlooked that the directions are already present in the network information sheet:

Instructions for Mac OS X using manual configuration

Open System Preferences -> Print & Fax -> "+" below printer list
Select the "IP" icon at the top of window
Select the "HP Jetdirect - Socket" from the drop down
Enter "term-printer.meeting.ietf.org" in the Address field. Leave the Queue field blank.
Print Using should autopopulate
Click Add

so my new proposed action is to add "Note: if you have an explicitly configured DNS search list, you must use the manual configuration method."

comment:15 Changed 3 years ago by sra@…

Sorry, that comment crossed in the mail with Hans's attempt to close.
I wasn't trying to reopen the ticket, nor did I open it or report the
issue originally.  The printer worked fine for me, just not in the way
that others appear to think I should have wanted it to work. :)

I think documenting the mess is a reasonable solution.

comment:16 Changed 3 years ago by Bill Fenner

Resolution: wontfix
Status: reopenedclosed

comment:17 Changed 5 weeks ago by Rick Alfvin

Milestone: ietf-90ietf-090

Milestone renamed

Note: See TracTickets for help on using tickets.