up and down loads do not work

[citojaso]

i 'm an ex-pie user.  that being said, i've just switched over to winmxworld and can not get any d/l's or u/l's to work.  they time out.  also, when in a chat room, i can browse anyone in the room except myself.  my job requires i travel and i stay in motels so access to the router is out of the question.  i use the secondary connection option with the 'unable to....' buttons in udp and tcp boxes checked.  while using pie i had no problems and cannot understand why i have problems now.  i have winmx enabled in all firewalls on this machine and have even tried with all protection disabled.  i'm at a loss.  any sugestions will be greatly appreciated.

[Me Here]

Hi citojaso,

Welcome to the site!
I'm not 100% sure whats caused this for you, so lets go through a few things..
First a few questions I have for you..

Did you uninstall WinMX and Peerguardian (if you had PeerGuardian) and then reinstall the WinMXGroup patch version?
What Operating system are you using?
What does the update bar say on your WinMX?  Patch Operational, Please Be Patient, or is it White blank bar under your version details and connection details located at the very top.
What firewalls are you using ?

If you could tell me that, it would help us to help you..

[citojaso]

i'm sorry for the delay in answering...been on the road a lot.....i think i've gotten it straightened out.   the problem seemes to be in the settings.  with no access to routers i have to leave checkmarks in the "unabel to" boxes in "incoming tcp" and "in/out udp" even though i have to use a secondary connection.  with these settings about 30% of people requesting u/l's get the message "both users firewalled".

[Bearded Blunder]

Yes unfortunately with those settings that is ineviable, you could possibly drop by the help room & ask if anyone has a capy of the uPnP enabled beta of the patch available (Merlin aka myself does for one). This would forward ports for you on any router which supports uPnP forwarding & has it enabled regardless if you have credentials to login to it or not on starting winmx. 
Were you to use that, you'd only have to set yourself unable in situations where this failed (can check if the port opened by visiting Sheilds Up! at grc.com, dropping in help room & using the bot's tcp test or possibly running the setup wiz so the ports test ran) any of those tests is I know extra hassle on startup in any new location, but if your stops are regular you'd soon know which places you got ports & which not.