Discussion:
all outbounds time out
(too old to reply)
Matt Ferrari
2015-02-28 01:28:34 UTC
Permalink
using cable connection with wireless router

all my outbound connections seem to time out.
I havent seen one file go out successfully recently.

is there a guide to improve the settings or advice?

Matt
hp
2015-02-28 22:25:56 UTC
Permalink
Post by Matt Ferrari
using cable connection with wireless router
all my outbound connections seem to time out.
I havent seen one file go out successfully recently.
is there a guide to improve the settings or advice?
Matt
have you double checked your router settings??

Are You still suing the default winmx ports??

Lots of ISP's used to traffic control those ports.

Generally users are advised to change the ports,
if you change them, you can usually try a test
by using the chat rooms features to visit a room
and seeing if you can get a 'whois' of your self,
you can also browse yourself while in a chat room to
see if that is working also. Generally if I fail
a 'whois' test and can't get a browse of myself
I totally close winmx and have another go at it once
it is back up and running, My ports are set and once
set and drilled thru the router, I don't mess with them.
There are times after starting winmx that the program
seems 'invisible' to others, and that's why I adopted the
chat room testing.
Matt Ferrari
2015-03-08 20:50:12 UTC
Permalink
Post by hp
Post by Matt Ferrari
using cable connection with wireless router
all my outbound connections seem to time out.
I havent seen one file go out successfully recently.
is there a guide to improve the settings or advice?
Matt
have you double checked your router settings??
Are You still suing the default winmx ports??
Lots of ISP's used to traffic control those ports.
Generally users are advised to change the ports,
if you change them, you can usually try a test
by using the chat rooms features to visit a room
and seeing if you can get a 'whois' of your self,
you can also browse yourself while in a chat room to
see if that is working also. Generally if I fail
a 'whois' test and can't get a browse of myself
I totally close winmx and have another go at it once
it is back up and running, My ports are set and once
set and drilled thru the router, I don't mess with them.
There are times after starting winmx that the program
seems 'invisible' to others, and that's why I adopted the
chat room testing.
Thanks for the help.
I was able to get it to work by
running the cmd prompt entering netstat -a
and looking for a port that was marked as "listening"

I entered one of those port numbers into the winmx incoming tcp connections
and i finally was able to send out a file.

Matt

Loading...