Back to Board Index
Back to Board Index
Forum help
| Unable to connect direct - but okay going through GameSpy | |
Neil Murray  7th Jun 2011 15:03:31 | It was suggested to me that Dave Wave might be the man to contact about this problem.
I registered as a member of FSOpen a couple of weeks ago. At that time the direct connect IP address was 78.150.110.93 and I had no problems using direct connect. Ports 6112 - 6122. After the change to IP 92.25.46.87, it was only very occasionally that I was able to connect direct and on these occasions I felt it could be related to the fact that there were few users. However it was not easy to come to any solid conclusion as I could not easly repeat. Please Note: There was no problem logging using GameSpy user, 'Free Flight' and JOINing www.fsopen.co.uk. This worked practically every time, weather loaded and the client and I could position aircraft etc. Today IP is 92.25.38.188 and when I started testing (Users 2-3)the results were; impossible to 'direct connect' while GameSpy 'joining' www.fsopen.co.uk worked every time. I was tipped-off by a posting on this forum and I think I may have found a solution - at least while there are few users in the fsopen session - it remains to be tested with many users. If I change the ports from 6112-6122 -> 6112-6112, direct connect works and GameSpy login works. Port setting 6122-6122 GameSpy okay, direct connect fails. Port setting 6112-6122 only works with GameSpy Log. |
| Colin Lansley 7th Jun 2011 16:59:02 | same problem i tried direct connect with 92.25.38.188 as listed on web site but failed to connect , i to am new here so any direction would be helpfull
|
| Neil Murray 7th Jun 2011 19:06:59 | Hi Colin,
I heard yesterday that Dave was away (I don't know what that means or when he is expected back). It might be less confusing if we waited untill he got back as I feel he has some experience in these type of problems especially in this area - rather than I start to mislead you - you may not have exactly the same problem as I have. What worked for me and I have just verifed a couple of times just now - still working - I went to multiplayer - clicked on 'network settings' button - this brings up the 'port range' - mine was 6112 - 6122 (note what you have incase you need to change back). I then set this range to 6112 - 6112. OK button on this and back to multiplayer screen. Then click 'Local Network (LAN)' fill in you real name (not teamspeak userid) and click 'Sign in'. On next screen click 'connect directly' - this takes you to the enter IP address 92.25.38.188 and click 'Find Sessions' you need to expect to wait a bit and either to see things loading or you end up with 'cannot create connection to host. If this doesn't work for you I suggest you wait untill Dave is available he's most likely got bags of experience in this exact area. |
Joe Clifford  7th Jun 2011 20:32:50 | Hello,
May be something to do with your firewall or Router Settings (services, port forwarding blah blah, although I highly doubt it) Try now with the new IP address: 2.100.194.213 |
| Neil Murray 7th Jun 2011 20:52:04 | Joe, thanks for tip about the IP change.
UPDATE, I have now been able to 'direct connect' every time with port setting 6112 - 6112 and have been 'listen in' on the 'evenings session' parked at EGPO. So at this point its looking good. I hope Dave or someone can provide a rational explanation. Reading back through the forum I believe someone else has experienced the same - this is what tipped me off to try this change. |
| Colin Lansley 8th Jun 2011 13:25:46 | Well i reset the port range from 6112-6122 to 6112-6112 and followed instructions filled in on connect direct the 2 i.p.s given i.e. 92.25.38.188 and 2.100.194.213 but still failed to locate session ? i can find FSOPEN >CO >UK in free flight sessions but require a password to be entered to conect / i cannot find a password on the FS web site can anyone enlighten me further as to what i need to do to connect to the Server please , yours getting desperate now Colin lol. |
Dave Wave   8th Jun 2011 17:47:07 | Ports should be left as default 6112 to 6122
If you still can't connect then its likely to be a firewall issue. If you need help with this grab me on teamspeak. |
| Colin Lansley 8th Jun 2011 20:25:07 | Ok Dave Thanks will try again tomorrow if no joy will call you on TS |
| Neil Murray 9th Jun 2011 08:17:31 | Dave, thanks, I'll try to catch you at a quiet moment on TS. System is Win 7 (64), Norton Internet Securities 2011 but I don't believe this is the culprit as I have tried with smart firewall turned off and anyway FSX is under program control with allow. Most likey firewall in router or ISP. There seems to be many view points on the internet as what ports need to be open, TCP or UDP and direction for FSX. I saw from the forum that you were involved in a similar case 15 May 2010. Anyway there is no rush at the moment as multiplayer (direct) seems to be working okay just with port 6112. |
| Dave Wave 9th Jun 2011 08:45:07 | There is a lot of rubbish and opinions out on the interweb!
Fsx uses quite a few ports but if you are connecting to a server then all of these are outbound connections and just about all firewalls and routers allow this to happen by default. Hosting a server you just need to allow inbound connections on UDP 6112 to 6122 on your router and firewall. You will also need to tell your router the internal ip address of your server to route this traffic to. 6112 is normally ok just on its own, I'm guessing 6113 upwards is used in case these ports are already used by another app although I've never seen them used. |
You need to Log on to post a reply. |
Forum help