Can't cpnnect using the client software

[Victoroos 205]

hello all

 

After some pain, we are able to connect using fsx over the wbe.

However, desk pilot doesn't want to connect using the same ip adress.. but it doesn't work

We opened the 60000 ports.. but still didn't work.

Any more advise? on what we can try?

 

vkr

victor

[RIPJAW 9]

Put the ip address and password directly in ClientSettings.ini file inside the quotes. Instead of using the entry boxes.

[Victoroos 205]

That has already been tried :/

[RIPJAW 9]

Have you tried a port checking site like www.canyouseeme.org ? or better yet the PFPortChecker software from http://www.portforward.com/help/portcheck.htm to make sure that port 60000 is actually open?

[Victoroos 205]

Sorry.. Also done, and green light :/..

So, I mean it shows open, but doesn't work..

Is it TCP or UDP?

[RIPJAW 9]

Just to be certain are you using the server or the client? The user hosting the server is required to open the port and not the client. If you are indeed using the server, have you checked your firewall? Otherwise it would seem that your internet service provider is blocking it (yes it can happen) or you have misconfigured your router and forwarding the port to the wrong computer on your local network.

 

To confirm the above - have a friend host the dp server and fsx session. The protocol is UDP.

[Victoroos 205]

HM.. Yepp. We tried both.. Him running the server, and me. We both opened the ports obviously..

And I don't think I forwarded wrong.

I will try to contact my ISP and see what they say

[RIPJAW 9]

Well since you're certain that port 60000 is open. It comes down to a firewall blocking it, possibly Microsoft's built in firewall.

 

Are you running a third party firewall like Symantec? If so you might need to add the client and server to its incoming & outgoing allow list. You may also need to do the same to the default windows firewall.

 

The following will cause the same issue:

 

1: Port is blocked, closed and/or misconfigured on the hosts modem/router.

2: Firewall is blocking the client and/or server.

3: Internet service provider is blocking incoming services.

4: Wrong ip address and/or known bug in the ip address/password entry boxes

5: Network congestion. http://en.wikipedia.org/wiki/Network_congestion

[Victoroos 205]

The Microsoft firewall actually has it listed as allowed.. So that can't really be it, and I don't run a second one.

Is the password.. Are there any requirements for?

And also.. Does the host also better put the password and IP in an .ini file?

 

I don't think it is network congestion. Seeing as there weren't any other things running..

[RIPJAW 9]

As long as the password is less than 20 characters it should be fine. Although there's limited error checking going on with the ip/pass entry boxes, so there could be a issue. Since all of my time is consumed by the pro edition and it's projects. I can't search for the problem code wise.

 

Just keep the password short and with no capitals. Yes the password needs to be added to the ServerSettings.ini as well.  B)

[tobick 0]

So.... i've been reading only 2 forums for troubleshooting the Desk Pilot program. Me and my friend are trying to connect but nothing happens. Attempt failed it says. We've done the port forwarding, both tried Captain and FO. Nothing helps. It just won't connect. 

 

1: Port is blocked, closed and/or misconfigured on the hosts modem/router. > should be fine

2: Firewall is blocking the client and/or server. > is open

3: Internet service provider is blocking incoming services. >it isn't

4: Wrong ip address and/or known bug in the ip address/password entry boxes > correct IP from ''myip''

5: Network congestion. http://en.wikipedia.org/wiki/Network_congestion > also not the problem.

 

Please mr Ripjaw, help us out..