http://bugs.winehq.org/show_bug.cgi?id=25377
--- Comment #18 from Erich Hoover ehoover@mines.edu 2010-12-06 14:48:20 CST --- (In reply to comment #17)
... Sorry, in fact, some of the addressess are 0.0.0.0, but there are at least other two different ones (loopback and someone from my LAN). That doesn't change throughout patches.
The "someone from your LAN" is either your ethernet or wireless IP address, as bind() only operates on local addresses. Any application that performs the behavior I discussed previously loops over all the available network adapters (which includes the loopback and INADDR_ANY) sending out a "are there any servers?" packet.
... I tested it unpatched, with first two patches and fully patched. Only the fully patched version could find remote servers automatically.
Ok, then this is definitely a duplicate of Bug #7929. It's nice to finally find an application that is not a game that is afflicted by this bug. If you could add 7929 to the affected versions of FileMaker Pro in the AppDB then that would be greatly appreciated. I do not have permission to mark duplicates, but when one of the Bugzilla maintainers stops by they'll likely take care of it.
... I also rm -(r)f everything concerning Wine I could locate.
That's a little excessive, but thank you for being so thorough.
... That is, if we already compiled from source with the two first patches applied, we have to start over from the unpatched source (expanding the tarball again).
Sorry about not explaining that, in this particular circumstance that is somewhat to be expected. The fourth patch includes a small addition to the wineserver component, which means that it must be applied against a clean source of the correct version. If you are interested in becoming more involved in Wine development then you can contact me privately and I will explain more.