On Thu, 2010-10-14 at 19:11 -0500, cnbiz850 wrote: > OK. Thanks. > > In order to run independent sessions of Wine, either Wine or the > bottle management should have mechanisms to remap the ports. Since > Wine already provide some independent mechanisms using the prefixes, > and Wibom is just simple wrappers using the prefixes, Wine should > consider handling the port remap issue. > > Anyone agree, disagree? > Disagree. If the program is a listener, it specifies what port it will listen on. If the port is already in use it can't open it and must be configured to use another port. If a program is making a connection to a listener it doesn't specify the port: the OS chooses an unused port, opens it and passes the open port to the program. As Vitamin says, this is how TCP/IP works, regardless of the OS being used. As far as the OS is concerned, Wine is merely another application that obeys the instructions it is given by the Windows program its running, so as long as Wine does what the Windows application says about port assignments its doing the right thing. Any confusion about port numbers is down to you or the Windows application. To resolve this problem you need to see what ports your Windows application is using and what ports are open before it is started. Use lsof for this. It shows you what ports are open and what program owns them: it is a standard utility on Fedora and is probably standard on Ubuntu: if not, use your package manager to install it. lsof must be run as root and produces huge amounts of output, so use this command: sudo lsof -P | grep -E '(UDP|TCP)' | less By default lsof will show port names. The -P option forces it to show port numbers. Martin
