[Pidgin] #3617: doesn't work properly if mdnsresonder is installed in a non-standard location
Pidgin
trac at pidgin.im
Sat Dec 22 12:45:13 EST 2007
#3617: doesn't work properly if mdnsresonder is installed in a non-standard
location
------------------------------+---------------------------------------------
Reporter: blaydman | Owner: datallah
Type: defect | Status: new
Priority: minor | Milestone:
Component: winpidgin (gtk) | Version: 2.2.1
Resolution: | Keywords: bonjour
Pending: 0 |
------------------------------+---------------------------------------------
Comment (by datallah):
I've done some further investigation and testing on this.
It turns out that the presence is being advertised successfully with the
standalone mDNSResponder and it is receiving notifications of other
clients, however, it can't perform the DNS lookup successfully for the
presence "remotehost.local" name.
{{{
(10:37:47) dnsquery: Performing DNS lookup for rutherfordium.local.
(10:37:47) dnsquery: Error resolving rutherfordium.local.: 11001
(10:37:47) bonjour: host resolution - callback error.
(10:37:48) bonjour: service advertisement - callback.
}}}
It turns out that resolving such things is the job of `mdnsNSP.dll`,
however, it needs to be
[http://msdn.microsoft.com/library/default.asp?url=/library/en-
us/winsock/winsock/name_space_service_providers_2.asp registered with
Windows] before it can do so.
Apple provides a tool that can be used to do this (I'll attach a binary to
this ticket), the syntax for doing follows:
{{{
NSPTool -install "mdnsNSP" "B600E6E9-553B-4a19-8696-335E5C896153"
"C:\Program Files\Pidgin\mdnsNSP.dll"
}}}
When you're done, you need to unregister mdnsNSP:
{{{
NSPTool -remove "B600E6E9-553B-4a19-8696-335E5C896153"
}}}
After following these steps, Bonjour seems to work correctly.
--
Ticket URL: <http://developer.pidgin.im/ticket/3617#comment:4>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list