Author Topic: Fxserver not connecting (Read 4510 times)

reef · « **on:** May 30, 2006, 04:32:13 pm »

Hello...since adding the blocked ip's to my sygate firewall FXServer will not connect..... i added the ws2_32.dll file to FXServer and started the room up and it connected fine once i entered entered room via winmx FXServer error'd each time...... do i need to rename the ws2_32.dll file ??? any help on this would be appreciated thank you?

reef

KM · « **Reply #1 on:** May 30, 2006, 11:25:43 pm »

if the problem started when you started blocking things in your firewall - could i suggest removing the blocking in the firewall and see if that fixes it? it is possible that you have blocked the wrong thing - and would be the first thing to try if blocking had caused the problems to start in the first place

reef · « **Reply #2 on:** May 31, 2006, 11:15:52 am »

thanks for the reply KM,but i guess it has nothing to do with the blocked ip's.I've talked to a few others that also use fxserver and theirs aren't connecting either.Dont know if its something to do with fedez site or what it is..... thank again for the replay.

cheerz

KM · « **Reply #3 on:** May 31, 2006, 03:04:45 pm »

there seem to be a few fxserver issues recently, however most people seem to be merely reporting issues with staying connected rather than getting connected, i'm sure fedez is looking in to it - however, have you tried removing the blocked IP Addresses from the firewall? as it would seem like very good timing for your fxserver to break at the same time you did that

of course you could always try another chat server to see if that is suffering the same problem or not

reef · « **Reply #4 on:** May 31, 2006, 05:41:31 pm »

Yes I did remove the blocked IP's from firewall and have started up an ouka room without any problems.There's 3 others that i chat with and they run FXServer as well and are having the same problem,one has been down for three days.Fedez website seems to be working ok so that doesnt seem to be the issue.I dunno,been usin fx for a coupla yrs now.never had this kind of problem.... thx once again for the reply

cheerz

reef · « **Reply #5 on:** May 31, 2006, 06:20:07 pm »

Ok i think i know whats happening now..... the 3 of u have been running fxserver without the hosts file,without the hosts file we've been able to connect to default ip's.... maybe those ip's are no longer available...... will try a few things and make sure.

cheerz

KM · « **Reply #6 on:** May 31, 2006, 08:33:15 pm »

you do need either a modified hosts file or the winmxgroup patch for fxserver (as fedez doesn't seem to want to fix it to actually work..?)

however i believe that was the case before as well, there has been a single change to cache server IP Addresses the other week however using a hosts file would still use the other caches, using the winmxgroup patch would have been unaffected by the change

reef · « **Reply #7 on:** May 31, 2006, 10:24:38 pm »

Well i thought by adding the dll file that fxserver would connect and run ok but once someone tries to enter fxserver errors.If theres any way of getting a modified dll for it i'd gladly test it out

cheerz

Stevi · « **Reply #8 on:** May 31, 2006, 10:50:24 pm »

FXServer will work by placing the PIEPatch in the FXServer folder. Get this: http:/www.mx-pie.com/downloads/MX-pie%20v2.9%20Manual.zip and extract it to your FXServer folder. It should work with no errors.

KM · « **Reply #9 on:** May 31, 2006, 10:57:01 pm »

https://www.winmxgroup.com/old-1.0/ws2_32.dll is a very minimal dll with nothing but the basic required hostname conversion in it

reef · « **Reply #10 on:** May 31, 2006, 11:08:20 pm »

thx Omega,i realise it works with pie i was just trying to see if there was a way around it lol .... will try that file KM thx again.

cheerz

reef · « **Reply #11 on:** June 01, 2006, 05:48:31 am »

ok i've tried the basic .dll file and was able to connect but upon entering, fxserver error'd out again (same thing happened when i got a buddy to try it on his)...so i downloaded 1.3 version of fxserver and added the newest .dll file, it was able to connect but in server window had a syntax error and i was unable to enter room (same with friend)... then added manual pie patch2.9 (1 host file) to fxserver and still unable to connect.I guess its time to use another chat server lol if anybody has any ideas i'm all ears or eyes in this case.

Bearded Blunder · « **Reply #12 on:** June 01, 2006, 06:49:03 am »

WCS is a good server.. with excellent support, the programmer being admin on this board... Ouka is also good.. & neither require messing around with patches, or custom hosts files

reef · « **Reply #13 on:** June 01, 2006, 07:14:54 pm »

Have used both in the past thx bearded and thx for the replys and help from all of you.... i'm gonna miss fx but hey life goes on lol.Take care all.

cheerz

reef · « **Reply #14 on:** June 04, 2006, 03:37:49 am »

Does anybody know what up with fedez site? the past few times i've been there i get this....
Domain Default page This is the default page for fxserver.p2pzone.net domain. This page is generated by Plesk. Please upload your own index.html file.Also i found FXserver 1.3.2 modified in the archive here and am using that now...... connects fine except the colour code glitches.... anyway sumbody can make a modified 1.3.7 version?

cheerz,reef

KM · « **Reply #15 on:** June 04, 2006, 04:17:57 am »

it's a standard "no site here" page from plesk, hopefully a temporary thing

reef · « **Reply #16 on:** June 04, 2006, 04:20:07 am »

ok thanks KM... is this maybe why my FXServer quit connecting?

reef · « **Reply #17 on:** June 09, 2006, 02:16:16 am »

wooohooooo.... stuck the most recent third party application patch into fxs folder...back up and runnin fine now...... thanks to all of you people here!!!

cheerz!!

~~Josh~~ · « **Reply #18 on:** June 10, 2006, 10:53:52 pm »

It is proven that you can in fact patch fxserver with the winmxgroup patch without it Breaking. I tried it myself.

https://www.winmxunlimited.net/tutorials/getfxserverconnected.html

KM · « **Reply #19 on:** June 11, 2006, 12:02:03 am »

fedez is claiming the issue is something to do with winmx.com suddenly resolving to 127.0.0.0 instead of 0.0.0.0 as it was before... personally i can't see how that would be a problem, as it seems to work find with winmx.com resolving to 127.0.0.0 on my system...

have a look at the timing that hosts file users suddenly started reporting connection issues, then compare it with the posts i have made on this forum regarding things that would effect hosts file users but not patch users... very convenient timing if you ask me, but of course that can't be the reason for the issues because that would be admitting that a hosts file isn't a fix, lol