NZFF

Posted: **Mon Jul 02, 2007 8:51 pm**

Hi guys,

Me, Creator2003. Mattnz and HCP are having some trouble connecting with default FS2004 multiplayer.

If possible, could you try logging on to '203.114.130.15' this evening and see if you have any issues- then posting here if you do, so we can try and figure out what the problem is? We are on TS too if you would like to chat.

Cheers.

Posted: **Mon Jul 02, 2007 8:59 pm**

I'll see if I can pop on in about 20mins, after I've landed. Even if the most we might ascertain from me being there is IVAO stuff doesn't make the difference.

Alex

Posted: **Mon Jul 02, 2007 9:05 pm**

I'll see if I can pop on in about 20mins, after I've landed. Even if the most we might ascertain from me being there is IVAO stuff doesn't make the difference

I'v used inspire many times, even with IVAP running too (don't ask

), and there have been no problems with my conecting or others.

Its much more likely conection problems Id say, its unlikely software in your sim will effect the multiplyer. Even IVAp and SB3 just use the multiplayer engine, they don't change it or anything, hopefully :ph43r:

James

Posted: **Mon Jul 02, 2007 9:43 pm**

All going fine for me, looks like you're all sweet as well.

Alex

Posted: **Mon Jul 02, 2007 10:41 pm**

This really is a strange problem!
I think tonight we managed to narrow it down to a problem with mine and Trolly's computers connecting to each other. At no point was I able to be in the same multiplayer session as Trolly, but for some reason, my connection with Evil1 was fine, which it wasn't the other week for the mission!

I did a little search on Google, and found the same article as Trolly:

This error is displayed by FS2004 when trying to connect to a session. Usually it happens when someone else that's already in the session is using a router and hasn't forwarded the correct ports. When your FS2004 tries to join, it gets a list of all the players currently in the session and tries to connect to them. But when it tries to connect to the player with the bad router, it isn't able to communicate with it, so FS2004 aborts the connection (note that FS2002 would happily connect anyway and just not show that player, but FS2004 now uses newer DirectX functions that return an error in this case, so FS2004 actually isn't able to connect this way anymore). Unfortunately there's not an easy way of figuring out which player is causing the problem, but if you ask everyone if they're using a router, and one of them says they are, and doesn't know about port forwarding, it's a good chance it's him :-)

The person using the router needs to configure it so that certain ports are forwarded to the machine running FS2004. Typically the port is UDP 23456, but you should ask the person hosting the session if they're using the default hosting ports, or something different. If things still aren't working, try also forwarding UDP 6073 and the range of UDP 2300 to 2400, since these are the DirectX "alternate" ports, which are sometimes used when the host is using something other than 23456. Sometimes enabling or disabling UPnP (Universal Plug-n-Play) can help also -- I've received reports from users saying both ways have helped, although I'm not sure why.

This is the problem we have been experiencing.

I think you said (Trolly) that you were using a Router (Orcon possibly :unsure:

), and I was just wondering if you had the "port forwarding" turned on. I turned it on earlier in the evening, and this should have worked. The fact that the problem was still there leads me to think that your Router (not Zone Alarm Firewall) may not have this configured; but I may be wrong......I think it only works if you're on a network, and I'm not sure if you are.

Posted: **Mon Jul 02, 2007 11:31 pm**

Thanks to all who turned up. Me, Jimmy, Mike and Craig managed to stay logged on for a few hours without any hassles, it only appears that me and Matt were having problems.

Sorry that me and you could not fly together Matt- it sounds like this port forwarding is the problem. Have you got any idea what settings I/we need to change in order to fix this? I turn off ZA and still have the same issue with you- and thats where my port forwarding settings are configured..

Posted: **Tue Jul 03, 2007 9:07 pm**

I have set up the port forwarding correctly (I think) on my router.
What type of Router are you using, Trolly?
There is a good list here and that tells you exactly how to set up port forwarding on many routers. I don't know if yours is there.
It was really easy to set up on my router, because there is already a custon setting for "MSN Gaming Zone" which is what FS uses. I also opened port 23456 in this program as well as my other firewall.
I had port forwarding configured in my firewall already (ie all the correct ports open), this was on the week of the mission. Last night, I enabled port forwarding before we started, which may have been why I was able to connect to Evil1, whereas I wasn't able to the other week.

EDIT: I have been doing a bit more research into the issue, and suspect that Port Forwarding may not be the issue with this. I found a link here which is a list of steps for troubleshooting issues on multiplayer programs. There is an interesting section there about firewalls, and I think that this could well be the problem.
I am running McAfee Security Centre, and this has caused problems with multiplayer before (But this was on Windows Vista), and caused multiplayer to not work. In the end, the problem was narrowed down to it being a problem with the Security Centre.
Simply disabling the firewall didn't have any effect, as the program was still running in the background, even with it shut off.
So, when I had a multiplayer problem on Vista, I uninstalled McAfee, and installed another security centre, and bingo! I was able to connect to a multiplayer session. This is what I am thinking could well be the problem.
Although, I am slightly doubtful, because I am able to connect with some users, and not others in this case. Maybe this can be put down to a conflict between certain firewalls, or security programs. Anyway, I am in the process of uninstalling McAfee again (shame, it was a good program!), and am going to just use the windows default firewall to see if I am able to connect with Trolly. I'm not available tonight to try it, but will be anytime tomorrow.

Posted: **Fri Jul 06, 2007 2:03 pm**

I am running McAfee Security Centre, and this has caused problems with multiplayer before (But this was on Windows Vista), and caused multiplayer to not work. In the end, the problem was narrowed down to it being a problem with the Security Centre.
Simply disabling the firewall didn't have any effect, as the program was still running in the background, even with it shut off.
So, when I had a multiplayer problem on Vista, I uninstalled McAfee, and installed another security centre, and bingo! I was able to connect to a multiplayer session. This is what I am thinking could well be the problem.

Hmmm, I've never had McAfee on my system, only ZA and AVG- but I had AVG when I had dial-up and had no issues with it??? :blink:

Posted: **Fri Jul 06, 2007 2:14 pm**

yeah ive got sygate firewall/AVG/no adware,spywatchers,and none have ever stop me and more than four ever joining up for abit of fun flight on the server .

Posted: **Fri Jul 06, 2007 2:20 pm**

I think, from reading on other forums, that there are quite a few programs that cause this error, I was just using my McAfee as an example. I know that Norton has also been causing problems, so if anyone here is using Norton, and is able to connect to multiplayer, that would be good to know

I'm not sure if there are any issues with ZA, but I think it would be worth a try testing now that I have uninstalled my Security Centre, and see if that has made a difference.

I am not entirely sure if this is the problem, just a suggestion

Posted: **Fri Jul 06, 2007 2:32 pm**

yeah ive got a couple of scenerys to reinstall before tonights mission so how about we get online again about 6-onwards ,it would be good if anyone else will be able to make it
to help again but it is a must really to have teamspeak running as thats the best way to chat about whats happening to others testing
cheers mike

Posted: **Fri Jul 06, 2007 2:36 pm**

Yeah, I'll try and be there for around 6, but it may be a little bit after

Posted: **Fri Jul 06, 2007 2:47 pm**

I used to run McAfee and had no trouble on Multiplayer.

Was using XP and on Dialup if this makes a difference.

Posted: **Fri Jul 06, 2007 5:09 pm**

It's still port forwarding or interconnection issues, it's just that either:

The data doesn't know where to go when it gets to your PC or doesn't know who to send it to

or

Something is blocking data on certain ports (ie Firewall etc)

You generally only need one person with a bottleneck and it's hard for others to join. The thing to look for is someone repeatedly joining and leaving straigh away. Sometimes the culprit can still re-join after leaving to allow the newcomer in, which makes it harder still to find out 'who' has the problem.

I've been through this by joining and hosting FS Host servers, at the end of the day the system, as basic as it is, is not designed to be fool-proof.

Matt

Posted: **Fri Jul 06, 2007 6:04 pm**

Well, I've uninstalled my Security Centre, and we'll see if that has any effect tonight

NZFF

Inspire Test