[Pidgin] #12643: Pidgin/Bonjour doesn't send Instant Message to another Pidgin/Bonjour client, both running on Windows
Pidgin
trac at pidgin.im
Fri Sep 24 11:15:53 EDT 2010
#12643: Pidgin/Bonjour doesn't send Instant Message to another Pidgin/Bonjour
client, both running on Windows
-----------------------------------------------------+----------------------
Reporter: v.plessky | Owner: datallah
Type: defect | Status: pending
Milestone: | Component: Bonjour
Version: 2.7.3 | Resolution:
Keywords: Bonjour Windows firewall proxy presence |
-----------------------------------------------------+----------------------
Changes (by datallah):
* status: new => pending
Comment:
Replying to [comment:17 v.plessky]:
>
> Tried method you described. See log attached.
> two comments on it
>
> 1) first two attempts "from 192.168.1.2" - coming from wireless
computer 192.168.1.51
<SNIP/>
>
> Last attempt (also via telnet) from wired connection, computer
192.168.1.149
>
> Pls also note that both computers are Linux machines.
> Therefor problem is not specific to Windows.
> And I doubt in this scenario that problem may be caused by Linux- (or
Windows-) networking configuration.
Yes, I don't think it is an OS-related thing, it'll be the router config
most likely.
> 2) I have questions on this part of log
<SNIP />
> Why, for the Heaven's sake, Pidgin making query to 192.168.1.2?
>
> Than 'Attempting connection to 192.168.1.2; Connecting to
192.168.1.2:1780 with no proxy; Connection in progress'
>
> There is no Bonjour client on that host/IP address.
> Why Pidgin connects it and what negotiates?...
>
> Last part: "Connecting to 192.168.1.2:1780; Connected to
192.168.1.2:1780; request constructed" even more confusing.
> What kind of request it constructed?..
This is not at all related to Bonjour, Pidgin is querying information from
your router for UPnP.
You can disable that by unchecking the "Use automatically detected IP
address" and "Enable automatic router port forwarding" checkboxes in the
"Network" section of the preferences.
> P.S. probably we need more detailed logging to fix reported problem.
There isn't really any more logging that you're going to get out of
pidgin.
I suggest you use something like Wireshark to capture the network traffic
during one of these connection attempts for further debugging, but at this
point, you really are going to have to look at the router configuration as
there isn't anything that can be done from the Pidgin side.
--
Ticket URL: <http://developer.pidgin.im/ticket/12643#comment:18>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list