HELP
Ok. its now working. N058BE was on the server while i was trying to connect.. So i dont know.
IS your multiplayer working
55 posts
• Page 1 of 3 • 1, 2, 3
by ZK-MAT » Wed Sep 20, 2006 6:39 pm
I tried earlier too and it failed.
I think I mentioned in the How to Connect tutorial that when you use FS Multiplayer it interconnects all PCs together, so if one plyer's PC is blocking ports then no one else will be able to connect. So, NO58BE, you may want to take a look at your settings
From the FS Host FAQ page HERE
What is the error "Unable to connect to all players"?
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.
I think I mentioned in the How to Connect tutorial that when you use FS Multiplayer it interconnects all PCs together, so if one plyer's PC is blocking ports then no one else will be able to connect. So, NO58BE, you may want to take a look at your settings
From the FS Host FAQ page HERE
What is the error "Unable to connect to all players"?
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.
-
ZK-MAT - Senior Member
- Joined: Sun Apr 30, 2006 11:41 pm
- Posts: 1690
- Location: Papamoa
by bardos » Fri Sep 22, 2006 9:21 am
Sorry folks, but I don't know who NO58BE is.
I am flying under Bardos, PH-ELS (my company) or MB1803NL (my former Alaska callsign.)
I have no problems with the 203.114.130.15 server for logging in, but had problems with the chat box.
This saturday I have to go to a show with my dogs, next time I 'll try to join you at a NZOX party...
Have a nice flight saturday ( I saw plenty of beer behind the hangars.....)
Max
I am flying under Bardos, PH-ELS (my company) or MB1803NL (my former Alaska callsign.)
I have no problems with the 203.114.130.15 server for logging in, but had problems with the chat box.
This saturday I have to go to a show with my dogs, next time I 'll try to join you at a NZOX party...
Have a nice flight saturday ( I saw plenty of beer behind the hangars.....)
Max
-
bardos - Forum Addict
- Joined: Fri Jul 14, 2006 12:19 am
- Posts: 152
- Location: N52.58.29 E06.50.37 The Netherlands
by Pedro » Fri Sep 22, 2006 9:37 am
Will the real N058BE stand up!!!
Gentlemen it is I.
I am at your mercy so to speak.
Please help a newbe get this sorted.
My humble apologies if I have raised the blood pressure of some fellow aviators.
I was certainly unaware that I was at fault.
Question?
What are the port settings for the host server or is this not my problem.
Please help.
If you are to kick my backside do it quickly
Pedro
Gentlemen it is I.
I am at your mercy so to speak.
Please help a newbe get this sorted.
My humble apologies if I have raised the blood pressure of some fellow aviators.
I was certainly unaware that I was at fault.
Question?
What are the port settings for the host server or is this not my problem.
Please help.
If you are to kick my backside do it quickly
Pedro
- Pedro
by ZK-MAT » Fri Sep 22, 2006 12:18 pm
ahhh the mystery is solved!!
Hi Pedro and welcome!
The fault is usually due to interconnection problems as outlined in my earlier post. Maybe let us know what sort equipment you have to connect - that is, are you on broadband and do you use a router (connected to your computer with a network cable) or an USB modem, do you use Nortons or ZoneAlarm (or similar) as a firewall to block any internet traffic coming to and from your PC?
You could firstly go to GRC Unplug n Play's site and run the small applet to see whether Unplug and Play is disabled. It can cause problems if enabled.
Also look at your firewall's (if used) allowed programs and allow all access to FS2004 - it's unlikely that you will get viruses or anything sinister by doing this - I haven't ever had a FS related virus (apart from being addicted to it at times ..)
The host server uses the default port, 23456 but will also connect using 23455. I would ensure the UDP port range say from 23450 to 23460 is open as well as 6073. It will depend on how you connect though, so let's see how you connect before offering more advice.
Finally, one way to test would be to get on the server and talk to someone else on messenger to see if they can connect. One sure fire way of knowing there's a problem is if you see someone join then leave straight away ... often several times. If that happens and there's only you on the server you know it's you. If there's a few others on the server then it's anyone's guess who has the problem.
My msn is splatty@orcon.net.nz if you want to contact me. I should be on later tonight (at work at the moment)
Cheers
Matt
Hi Pedro and welcome!
The fault is usually due to interconnection problems as outlined in my earlier post. Maybe let us know what sort equipment you have to connect - that is, are you on broadband and do you use a router (connected to your computer with a network cable) or an USB modem, do you use Nortons or ZoneAlarm (or similar) as a firewall to block any internet traffic coming to and from your PC?
You could firstly go to GRC Unplug n Play's site and run the small applet to see whether Unplug and Play is disabled. It can cause problems if enabled.
Also look at your firewall's (if used) allowed programs and allow all access to FS2004 - it's unlikely that you will get viruses or anything sinister by doing this - I haven't ever had a FS related virus (apart from being addicted to it at times ..)
The host server uses the default port, 23456 but will also connect using 23455. I would ensure the UDP port range say from 23450 to 23460 is open as well as 6073. It will depend on how you connect though, so let's see how you connect before offering more advice.
Finally, one way to test would be to get on the server and talk to someone else on messenger to see if they can connect. One sure fire way of knowing there's a problem is if you see someone join then leave straight away ... often several times. If that happens and there's only you on the server you know it's you. If there's a few others on the server then it's anyone's guess who has the problem.
My msn is splatty@orcon.net.nz if you want to contact me. I should be on later tonight (at work at the moment)
Cheers
Matt
-
ZK-MAT - Senior Member
- Joined: Sun Apr 30, 2006 11:41 pm
- Posts: 1690
- Location: Papamoa
by Pedro » Fri Sep 22, 2006 1:14 pm
Hi Matt,
Thanks for the quick reply. I took a bike ride to the airport in a one off chance you worked with Bay Flight. But I drew a blank. The only reason I made that connection was The cessna (MAT) on your Forum letters.
Any way down to business.
I am on broadband using a D-Link DSL-302G which is connected through the network connection to my PC.
I must confess that Zone Alarm was connected last night and possibly this could be the root of the problem.
The port settings on FS2004 are default in both cases (connect & Host).
I thought there were some strange things happening last night and was about to make comment on it this morning until I read this post on me and my errant intrusion (cringe!!).
I am not that far from my computer at any time during the day and I will try again later to see if I can make a valid connection. But I will wait and see if you can offer a bit more advice on the info that I have given you.
Cheers
Peter
Thanks for the quick reply. I took a bike ride to the airport in a one off chance you worked with Bay Flight. But I drew a blank. The only reason I made that connection was The cessna (MAT) on your Forum letters.
Any way down to business.
I am on broadband using a D-Link DSL-302G which is connected through the network connection to my PC.
I must confess that Zone Alarm was connected last night and possibly this could be the root of the problem.
The port settings on FS2004 are default in both cases (connect & Host).
I thought there were some strange things happening last night and was about to make comment on it this morning until I read this post on me and my errant intrusion (cringe!!).
I am not that far from my computer at any time during the day and I will try again later to see if I can make a valid connection. But I will wait and see if you can offer a bit more advice on the info that I have given you.
Cheers
Peter
- Pedro
by ZK-MAT » Fri Sep 22, 2006 1:34 pm
Gidday Peter,
No I'm not connected to Bay Flight apart from them stealing my reg for their plane lol. I have recently enquired into PPL training with them I hope they don't put two and two together if they recall you going there and asking for me .... B)
I take it you are local? I spend about 30% of my day sitting in my office in Devonport Road, Tga, and the other 70% driving around the countryside, then get home and play (aka mess up usually) my PC...
It could be Zone Alarm, perhaps look in the permissions there and give FS2004 permission to allow traffic in and out.
I am not overly familiar with the Dynalink modem port forwarding, if in fact it even needs it.
I shgould be online at home later in the evening if you are around.
No I'm not connected to Bay Flight apart from them stealing my reg for their plane lol. I have recently enquired into PPL training with them I hope they don't put two and two together if they recall you going there and asking for me .... B)
I take it you are local? I spend about 30% of my day sitting in my office in Devonport Road, Tga, and the other 70% driving around the countryside, then get home and play (aka mess up usually) my PC...
It could be Zone Alarm, perhaps look in the permissions there and give FS2004 permission to allow traffic in and out.
I am not overly familiar with the Dynalink modem port forwarding, if in fact it even needs it.
I shgould be online at home later in the evening if you are around.
-
ZK-MAT - Senior Member
- Joined: Sun Apr 30, 2006 11:41 pm
- Posts: 1690
- Location: Papamoa
by Pedro » Fri Sep 22, 2006 1:57 pm
Hi Matt,
Yes I,m a local . Live in Orkney Rd. at the Mount so I,m just around the corner from the airport so to speak. Msn this end is fire1@xtra.co.nz.
Hope I din't reveal too much at Bay Flight
Hope to catch you later. I will have a look on line about 1700 but rest assured I will be only stay long enough to test the water so to speak.
Might get another kick up the backside from Crazy Craig
Peter
Yes I,m a local . Live in Orkney Rd. at the Mount so I,m just around the corner from the airport so to speak. Msn this end is fire1@xtra.co.nz.
Hope I din't reveal too much at Bay Flight
Hope to catch you later. I will have a look on line about 1700 but rest assured I will be only stay long enough to test the water so to speak.
Might get another kick up the backside from Crazy Craig
Peter
- Pedro
by Craig » Fri Sep 22, 2006 1:59 pm
Pedro wrote: Hi Matt,
Yes I,m a local . Live in Orkney Rd. at the Mount so I,m just around the corner from the airport so to speak. Msn this end is fire1@xtra.co.nz.
Hope I din't reveal too much at Bay Flight
Hope to catch you later. I will have a look on line about 1700 but rest assured I will be only stay long enough to test the water so to speak.
Might get another kick up the backside from Crazy Craig
Peter
I didnt touch ya 
. If you want, we can try ur multiplayer now???- Craig
55 posts
• Page 1 of 3 • 1, 2, 3
Who is online
Users browsing this forum: No registered users and 2 guests