Author Topic: FX Server Connection problems (Read 22885 times)

PenMax · « **Reply #20 on:** July 05, 2007, 06:51:33 pm »

And BTW ... It worx with WinMX Secondary Connection >>> WOO HOO !!!

tig · « **Reply #21 on:** July 06, 2007, 03:00:58 am »

Ok Guys

Great News 24 hour Test is complete for fx server. I am able to see it in room listing and I have had connection for the last 24 hours. Also I have been on secondary for the 24 hours and it does work.

Ok here is how to fix it
1. go here https://www.winmxworld.com/tutorials/connection.html
2. download the 3rd party connection fix.
3. open fx server
4. replace the host file to this ws2 file
5. close it and open fx server

And that is it

Happy winmx chatting all.

PenMax · « **Reply #22 on:** July 06, 2007, 04:26:59 am »

Quote from: silicon_toad2000 on July 06, 2007, 03:00:58 am

Ok Guys

Great News 24 hour Test is complete for fx server. I am able to see it in room listing and I have had connection for the last 24 hours. Also I have been on secondary for the 24 hours and it does work.

Ok here is how to fix it
1. go here https://www.winmxworld.com/tutorials/connection.html
2. download the 3rd party connection fix.
3. open fx server
4. replace the host file to this ws2 file
5. close it and open fx server

And that is it

Happy winmx chatting all.

Nope ... my 'FXSv1.3.10Beta11' using your new 'ws2_32.dll' is dead as a doornail! (WinMX connected in Secodary)

I'm afraid it's back to the trusty Caches which were working quite well before I tested out you new 'ws2_32.dll'. Anyway credit where credit is due, thanx heepz 'Î¥Îî¢rôÎ¥Îê¢¢â'!! C\;^))

PS: It's working like a gem again with the Caches, and with WinMX in Secondary n all n all!

dazco · « **Reply #23 on:** July 06, 2007, 06:02:02 am »

iam running fx server 1.3.9 the old ws2_32.dll is not connecting it to wpn and the new one is not either but the last host file released on this site when added to fx programme folder is connecting it

GhostShip · « **Reply #24 on:** July 06, 2007, 07:25:30 am »

It seems to me that folks are not understanding how the ws2_32.dll is supposed to be used, contrary to whats beeen said here it does work and has been tested by many, I believe those claiming its not working have not restored their FX to its original state when conducting the tests.

The winsock acts as a redirecting tool and for it to intercept the traffic it requires you use the DNS addresses that the program was built to use not any other or it will fail, this then is my suspicion for the failures.

With certain versions of FX its a struggle to make it work properly as it was modified by sabre and co to not work with the dll, something they received a lot of bad publicity for, so please try to use the latest version where this problem was fixed.

dazco · « **Reply #25 on:** July 06, 2007, 03:23:52 pm »

i have run fx 1.3.9 almost a year on the previous ws2_32.dll with no problems very stabel, the beta new version of fx was in testing stages when fede went awol i would rather stick with 21.3.9 as most others would also as it has proven the most stable version of fx so why does the new ws2_32.dll on this site not work in it and now also the original version of ws2_32.dll

Micromecca · « **Reply #26 on:** July 06, 2007, 05:21:10 pm »

Quote from: PenMax on July 06, 2007, 04:26:59 am

Nope ... my 'FXSv1.3.10Beta11' using your new 'ws2_32.dll' is dead as a doornail! (WinMX connected in Secodary)

I'm afraid it's back to the trusty Caches which were working quite well before I tested out you new 'ws2_32.dll'. Anyway credit where credit is due, thanx heepz 'Î¥Îî¢rôÎ¥Îê¢¢â'!! C\;^))

The dll will work perfectly if, as GhostShip says you undo the settings we created by adding the caches manually..
for the dll to function correctly your config options would need to be.

Code: [Select]

/setWpnOption UseLocalWinmx=0
/setWpnOption LocalWinmxPort=
/setWpnOption UsePeerCacheList=0

reef · « **Reply #27 on:** July 07, 2007, 06:33:35 pm »

ws2_32.dll is workin for FXServer here..... shareguard is now connecting also.... thx guys

PenMax · « **Reply #28 on:** July 09, 2007, 11:22:45 am »

The 'ws2_32.dll' worx fine in my FXServer since rebooting my PC.

And, yes Î¥Îî¢rôÎ¥Îê¢¢â those r d settingz i had b4 i rebooted.

Thanx Guyz for persisting, all's well that endz well.

®Ð£-MÜSÏÇ*MÂÑ · « **Reply #29 on:** July 11, 2007, 02:27:22 am »

hmm dunno if this sounds right but i deleted the host file and dlll file out of my fx server and replaced it with the dll newest one from the winmx patch rebooted the server and immediately got 4 green lights.worked for me anyhow good luck. M.M.

ÐØØMÊ® · « **Reply #30 on:** October 26, 2007, 02:43:37 pm »

my FXServer works perfectly (FXServer just came on three connections when i was doing stuff with the settings

)

lovejoy291 · « **Reply #31 on:** November 21, 2007, 01:26:40 pm »

last couple of days my fx has not been connecting has any 1 else had any probbs 3.9 dont seem to find any ip,s and 32dll in 3.10 has never worked for me

J a M e S · « **Reply #32 on:** November 21, 2007, 04:07:34 pm »

i didnt have time to read all the posts but reading the first few i found a solution for a freind.. i used the last version of FXS before the beta with a hosts file i just changed the IP's to the working ones from WinMX Group

lovejoy291 · « **Reply #33 on:** November 21, 2007, 05:41:52 pm »

where would i find them plz james and do i open host file in fx3.9 with note pad ??

J a M e S · « **Reply #34 on:** November 22, 2007, 12:36:32 am »

well look in the WinMX world archive for FXS download the one above the beta version and add this hosts file in with it

http://www.tpateens.co.uk/files/fxs/fxs/hosts.zip

J a M e S · « **Reply #35 on:** November 22, 2007, 12:41:18 am »

Download This,

httpss://archive.winmxworld.com/Fx%20Server/FXServer%201.3.9%20-%20210606.zip

Replace the default config with the one from your old FXS server

then download the host file form my server, unzip it, and add it to the same folder as the FXS files..

http://www.tpateens.co.uk/files/fxs/fxs/hosts.zip

i have altered this host file to work with the currently operational peer caches, this should make your FXS work, allthough this is nor permament, the IP's of the per caches might change or the users might stop operating them,

*DONE (silicon_toad)

tig · « **Reply #36 on:** November 22, 2007, 02:41:23 am »

Thankyou James for that hosts file updates.

lovejoy291 · « **Reply #37 on:** November 22, 2007, 09:08:03 am »

thank you james works just fine

)

J a M e S · « **Reply #38 on:** November 22, 2007, 11:36:46 am »

Your welcome, just trying to help out a little n thanks toad

Lagerlout666 · « **Reply #39 on:** November 22, 2007, 02:12:16 pm »

Im a little lost with that hostfile. you have a refrence to 205.238.40.51 as the winmx.com domain.
That is a Pie refrence an if for some stupid reason somebody decided to place this in their hostfile directory they would receive updates to a Substandard connection solution, Im sure that is just a error and for the most part that bit is completly irelevant to the operation of FX serve an could it be removed. Also a few other caches would be better added incase that one isnt running, seen as the complaint is the server having connection problems that might be a little oversite.

Also i havent looked back but what is up with the ws32.dll, i thought that this worked perfectly with FXserve an i am sure that it has been modified. Thats as simple as placing in the same folder an fire up the server.

If you need a ws32.dll please post back, ill hunt one out for you, and if you need a list of static ips for your hostfile james log on msn ill give you a few.

Author Topic: FX Server Connection problems (Read 22885 times)

dazco

dazco

Micromecca

®Ð£-MÜSÏÇ*MÂÑ