-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need connection digagnostics #55
Comments
Thanks for the suggestion. As for your particular issue: is port forwarding in The Constructor successful? Also are you able to successfully build using the private/local IP of your build server rather than the public IP? |
The Constructor thinks the port forwarding works -- about to try locally to see if that works. Works fine using a bonjour address... |
Have you had success in getting this working? |
Nope, not yet. Will get out the network sniffer next chance I get DavidDavid HM Spector, Founder/Developer Zeitgeist Info Systems email: spector@zeitgeist.com
|
Same issue here. Getting a network time-out. The Constructor thinks the port forwarding is working fine. Compiling take a long time and then finally states host not responding without any diagnosis messages. Some type of progress monitor and some guidance would be great. |
@dhmspector Ok, thank you. @scottsquires So you had to manually set up port forwarding? The 3rd party website in the FAQ, portforward.com, has a number of guides for setting up port forwarding on a variety of routers. I'm not sure where you see lists of hundreds of games and software packages as when I follow the link in the FAQ there's a list of router brands (ignoring the adverts). When manually port forwarding you'll need to know that The Constructor uses TCP and the port you'll want to forward is the one you are using in The Constructor, by default 5461. Also, if you could both check that the port you are trying to forward is open using this website, that'd be great. |
Solved my issue - it was an ISP routing issue (they were port blocking). |
@dhmspector Glad to hear you solved it. If you don't mind sharing, how did you figure out in the end that it was an ISP issue? It would be useful for reference purposes so that others who see this can check too. Thanks. |
Follow that which then las a list of all the different routers from that particular company. Then follow that to a specific router and you'll see an entire long page of every game/app under the sun that you click on to configure for that specific one. I have used their guide (guessing at which app best matches) and the guide for the router with still no success. Linksys router and Time Warner ISP |
@scottsquires Ah I see what you mean now, where it is showing you the different services to configure for. Thanks for explaining. What were the settings you used for the port forwarding? Also from what @dhmspector said it might be worth checking if your ISP is port blocking. Have you checked using this that the port is open? |
It confirmed that it's not actually forwarding despite the Linkysys settings. Since I have 2 routers involved and contacting TWC is a wasted day I'll have to back burner this for the moment. |
I see, if you need any more assistance do just comment again and I'll be happy to help. |
Right now there's no way to debug a port-forwarding issue.
I have 25 yrs experience designing & working with firewalls, my firewall is configured to allow the traffic on the default port, yet I am unable to get Drigend to connect to my build server. (I know my settings are correct, my firewall allows other kinds of services thru.. but without any more diags from your app I have no way of knowing what's up).
The text was updated successfully, but these errors were encountered: