http://bugs.winehq.org/show_bug.cgi?id=25377
--- Comment #16 from Erich Hoover ehoover@mines.edu 2010-12-06 09:21:30 CST --- (In reply to comment #15)
... the address shown was 0.0.0.0.
That fixed it! I had to uncompress source again to get rid of the mess already made and start fresh. Uninstalled (make uninstall) and installed again with the first two optionals (tools/make_requests and autoconf), and voilà! Filemaker can find remote servers and databases. ...
Excellent news! However, it sounds like it's not the interface-specific bind patches since the address shown is 0.0.0.0 (INADDR_ANY). When you originally patched and installed (make && make install) how did you launch Wine? If you had been running from a terminal with a distribution-provided copy of Wine and then installed a new custom Wine and ran from the terminal again then the terminal will not use the new Wine, you need to launch a new terminal in order for it to detect the new Wine. So, if you could try going back to just the first two patches and see if that fixes it for you then that would be greatly appreciated. For future reference, you can tell what terminals are using which Wine by running "which wine". Distribution installed copies will report "/usr/bin/wine" and custom installations will report "/usr/local/bin/wine".