Comment 26 for bug 57957

It's been a while since I worked through this so I can't say I exactly recall how I found the offending file. I think I just worked backwards from the fact that the /etc/init.d/vmware-player script was throwing the error. Reading that file I think it was relatively simple to track down the other files it called. Then it was just a matter of searching in the file for the text of the error message.

If you're really at a loss, one brute force way to find files that throw specific error messages is to do something like the following:
# sudo find / -iname "*vmware*" -type f -exec grep -H "Bridged networking on" {} \;

This will search all files that have vmware in their name (case insensitive), then grep through them for a specific piece of text, in this example "Bridged networking on".

Hope that helps.