another with a connection problem

[rayrhino]

Hi

I'm having similar problems that others are describing on this thread. Used mx for years, but over past two weeks, not been able to connect (flashing yellow, doesn't go green). Was running version 3.53. Found your website and tried the patch - no luck. Installed 3.54 - no change. Uninstalled and re-installed twice - no difference. Tried some of the tips from other posts on this thread - still nothing (i.e. i'd also got confused with the SOCKS proxy thing - added it, then removed it)

Can someone help please?

(3.54 still installed, DSL, Windows 98SE, with D-link G604T router)

[Me Here]

Hi rayrhino

Make sure that under the WinMX Settings > Outgoing TCP you have set to Do Not Use Proxy, make direct connection.  If its set other wise set it like this and restart.

It might also be worth mentioning at this time that if you have any software firewalls installed to remove WinMX from the allowed rules completely.  Then restart and allow it to ask for permission to access the internet again.

Post back and let us know.

[rayrhino]

Thanks for the reply. Me Here.

No, it's not a firewall problem, and I reset back to make a direct connection after trying the SOCKS 4 option.

what else should I try?

[rayrhino]

...another thing i've just noticed, is that, in Program Files/winmx, the winmx program itself gives the "modified" date as 12/12/04, even though I've uninstalled and re-installed a couple of times today. Could this mean that it didn't reinstall properly? And if so, how can I remedy this?

[]-[êll.Ôñ.ËÀR'][']-[.]

best way  is to delete the whole thing from your c/drive and do a fresh install that way you will know for sure its installed properly use the Install for WInMX v3.54 Patched from here


                                     https://www.winmxworld.com/tutorials/connection.html

[Me Here]

I agree with HellOnEarth's advice rayrhino,

But just to clarify things for you, the dates you see on files such as the winmx.exe file or the patch file OLEDLG.DLL have dates on them when they were made.  When you hover your mouse over them or on the windows explorer if its in details mode.

The WinMX your using was released on Dec. 12, 04 and that date will stay there since they have left WinMX and the only changes since are to the patches we use to connect, last one offered on this site being dated July 12, 07.

[bughunter]

I'm having similar problems that others are describing on this thread. Used mx for years, but over past two weeks, not been able to connect (flashing yellow, doesn't go green). Was running version 3.53. Found your website and tried the patch - no luck. Installed 3.54 - no change. Uninstalled and re-installed twice - no difference................

so for the last two years what patch have you been useing, since oct of 2005 you will have needed a patch for winmx to work anyways ?
could you check add/ remove programmes accessed by start / settings / control panel / add remove programmes......... look for either peer guardian 2 or peer guardian lite and or pier auto updater.........if any of these programmes are installed remove all of them.........then check in your c:/ drive programmes to make sure any folders containing these programmes have been removed also...........
if you have a registry cleaner  run that to remove any registry keys involving these programmes, if you dont have one then google for registry cleaner   there free  and are good for general house keeping of your pc........
the above programmes should be removed and NEVER installed  as they dont work never have and will only break your winmx at some point .......pie patch is only malware disguised as a patch and only promoted by a bunch of self confessed liars and winmx scammers.........winmx works much better without pie or peer guardian installed period..........
then try reinstalling winmx as per the instructions all ready posted...........

if non of the above is installed then make sure winmx is running as a passive secondry connection..........in winmx goto settings incoming tcp  select unable to accept incoming tcp   do the same for incoming udp    this will take  your router out of the equation as a potiential source of the problem,  as has already been susgested  remove any access rules in any firewalls for winmx and then let them be readded as winmx attempts to access the internet..........this is very important.........because any good firewall uses md5 checksums for all proggies accessing the internet, this is how firewalls can determine if any programme has been hijacked by a trojan / worm etc as these nasties cannot  copy the md5 checksum and so the firewall will block that programmes access even if the rules say to allow access.........and so of course the patch makes alterations to winmx and any good firewall will detect these changes and block winmx.............

also try doing a dns flush   start / run / type cmd   then hit the enter key    you wil get a black pop up box with a command prompt   type   ipconfig /flushdns    then hit the enter key  you should get a message saying the dns cache has been cleaned..........close that black box    reboot your  pc     hopefully winmx will now work...........
if not   in winmx were the rooms would normally list   there is a black bar  with the word filter on the left of it paste this room addy in there WinMXWorld.com Help_6444D04ABABE          winmx will connect to this room even if its not connected   someone in there will help try to resolve  your connection issues      good luck and let us know how you get on

[rayrhino]

Hi bughunter,

sorry it's taken me a few days to get back to you, but I waited until a friend was available to help me, as i'm not too good with the technicalities.

Firstly, I did instal a patch in Oct 2005 - I can't remember where from. All I did was find a website, followed instructions, and winmx worked again. I searched thru Control Panel, and there was nothing called peer guardian at all - the only thing similarly named is a file called 'peer points manager'. However, in Program Files I also found a PIE patch (dated 12/10/05), so i uninstalled this.

I then uninstalled mx and reinstalled. Still no connection!

re next paragraph - am running a secondary connection, and checked no firewall problem.

I then tried the DNS flush. This didn't work, as ipconfig didn't recognise flushdns as a command, so I never got the 'dns cache cleaned' message.

Finally, looking on one of the other threads, I installed the 3.0noMX that Bearded Blunder advised from the "connection fix under King Macro" - no difference.

Anything else I can try??

[Bearded Blunder]

did you also follow 3.0 Nomx by re-running the current patch only installer? no mx fixes a small issue my installer misses, but you still need the .dll file from the new installer

[rayrhino]

Is that the 3.0mod 3 Patch Only setup? Yes i did, and still no connection - the only difference is that it says 'patch online' in the top left hand corner above the connection status, whereas previously there was just a long blank white bar.

Also, I notice on other connection threads references to hosts files - what are these?

[Susan067]

my internet told me they blocked me from using winmx on my wireless internet...is there anyway i can bypass them to connect to it through my linksys router?

[Bearded Blunder]

if your provider is blocking it the only solution would be a change of provider

[rayrhino]

Well, I went to bed despairing i'd ever get win mx back in operation last night, then this morning I tried again and...it connected straight away! Have restarted the computer a couple of times since, and win mx connects each time.  Clearly one of your tips worked, it just needed a bit of time to filter through. So THANKS so much, BB, Bughunter, and all the other people who helped me. What a helpful bunch.

rayrhino.

[Bearded Blunder]

i should have mentioned 9x & me require rebooting to load the changed setting sorry