The modifications listed here are for you to use at YOUR OWN RISK! they have been tested to acheive their goal but their security has not this may infact leave your set up vulnerable.

im not going to explain what this is...you can google or even wikipedia it yourself.but heres the fix

the files we are going to be working with are as follows/etc/inetd.conf /etc/xinetd.conf (also uses PAM {can also google that yourself})/etc/xinetd.d/and for PAM we will also be usingetc/hosts.denyetc/hosts.allow

warning-leave everything in the config alone and only add the following lines (after you replace the < > with their values) otherwise your internet for all general purposes will go BOOM!

This manual page describes a simple access control language that is based on client (host name/address, user name), and server (process name, host name/address) patterns.

This means hosts.allow and hosts.deny only works for services using client host name/address and user name like ssh, ftp, vnc etc, NOT for general p2p.My hosts.allow only has very few entries in it and my hosts.deny contains ALL:ALL, so if this would be working for p2p I couldn't up- or download anything at all, lol

Of course IF you setup the service names in /etc/services correctly first so they're actually valid you might be able to add them in hosts.deny/hosts.allow, but then you wouldn't need ALL: as argument but the service name instead so you'd only control the access to those services ("wine" and "winmx" in your setup)

As to why spawning a daemon via inet.d/xinet.d is helping I'm kinda confused, lol.I've been using winmx under wine on debian for quite a while now (>4 years) and have yet to experience any uploading problems....

The only thing I ever noticed is winmx sometimes having troubles resolving addresses, this can be fixed by either installing the package "winbind" (part of samba) or what I've actually done is set winmx to use external dns instead of resolving through the OS, i.e. I put in one of the openDNS addresses in settings > host name resolution in "use external DNS server".

well, I was talking about resolving cache addresses etc, and putting those in the hosts file would be kinda weird since the patch works just fine under wine....It's just been my experience that putting the dns server into your winmx directly is faster than resolving the stuff through Linux, but then that's just me....

And winbind get's registered with NSS, so no need to configure stuff by hand - which is the reason for the post.

We all know there's athousand ways to configure stuff in Linux manually but I was suggesting fast and easy solutions for newbies, everything esle can be found elsewhere.Personally I don't think it's a good idea to staret messing with security sensitive stuff right away without even knowing what the stuff does and I'd advise strongly against it.

And I bet we've confused any newbies completely by now and this post was completely unnecessary for the knowledgable in the first place...

The post was for as the thread title says for people having this issue.90% of noobie freindly distros arent going to have any weird installation options that would "break" a system.And as always for anyone who is reading this thread, seek live help or find the advice+succesfull results on google three times before you try it.