Page 5 of 6
Re: Timeouts connecting to AMI via http://aws.otoy.com
Posted: Mon Nov 11, 2013 1:42 pm
by peteratabb
luma wrote:I'm experiencing much the same issues. I've placed the GUID=etc in the User Data per the documentation and am using the following link to get at my running instance:
http://aws.otoy.com/?connect=//<instanc ... 1;STATUS=1;
AUTOLOCK=0;WAN=12;GUID=<GUID>
I have yet to be able to successfully attach to the system outside of RDP.
Hi Luma,
I'm having the same issue also.
Similar to other posts, and to help narrow down the problem for other users, my setup is:
The GUID i set in the userdata instance setup is not the same as i can see when i RDP into the server (think this is the root problem).
Using the URL with either my GUID or the one supplied by the server itself does not connect, i get a timeout error message.
RDP onto the server is fine, and i can see the TCPSVCS.exe service running and the GUID it has created for itself.
I've changed my amazon instance firewall rules (security group) using the defaults supplied by the OTOY image, but to only allow my IP address instead of the world (0.0.0.0/32) supplied as default (this should be incoming traffic only?) -has anyone tested with the normal default security rules?
I'm using the Autodesk OTOY ami.
Tested with my Firefox browser.
Booted the instance once for my testing then shutdown, i've not retested since -but it should work on the first attempt.
Interestingly when i use the URL the page loads as a grey screen with a blue 'i' symbol at the top left of the screen, so i assume that it has started to work, before i then get the timeout message.
Re: Timeouts connecting to AMI via http://aws.otoy.com
Posted: Mon Nov 11, 2013 2:15 pm
by SimonG
peteratabb wrote:
Hi Luma,
I'm having the same issue also.
Similar to other posts, and to help narrow down the problem for other users, my setup is:
The GUID i set in the userdata instance setup is not the same as i can see when i RDP into the server (think this is the root problem).
Using the URL with either my GUID or the one supplied by the server itself does not connect, i get a timeout error message.
RDP onto the server is fine, and i can see the TCPSVCS.exe service running and the GUID it has created for itself.
I've changed my amazon instance firewall rules (security group) using the defaults supplied by the OTOY image, but to only allow my IP address instead of the world (0.0.0.0/32) supplied as default (this should be incoming traffic only?) -has anyone tested with the normal default security rules?
I'm using the Autodesk OTOY ami.
Tested with my Firefox browser.
Booted the instance once for my testing then shutdown, i've not retested since -but it should work on the first attempt.
Interestingly when i use the URL the page loads as a grey screen with a blue 'i' symbol at the top left of the screen, so i assume that it has started to work, before i then get the timeout message.
The GUID should be different. Have you set up all the ports suggest in the AMI documentation?
Firefox and IE wont work for me but Chrome does
Re: Timeouts connecting to AMI via http://aws.otoy.com
Posted: Mon Nov 11, 2013 2:27 pm
by peteratabb
Hi SimonG,
Maybe I've misunderstood something but i thought the purpose of supplying a GUID as part of the EC2 instance UserData was so that it would be used by the OTOY software to allow my connection from web browser, without the need to RDP into the server each time to get the new GUID?
All ports on my instance were set automatically during the set-up based on the Autodesk AMI settings,
21
80 (HTTP)
443 (HTTPS)
1000 - 1100
3389 (RDP)
5090
5900 - 5910
8090 - 8300
I'll have a go with Chrome later, strange that it seems to be browser specific? Or maybe Chrome is using one method and FireFox/IE another?
Re: Timeouts connecting to AMI via http://aws.otoy.com
Posted: Mon Nov 11, 2013 3:11 pm
by SimonG
Yes using the GUID in userdata does mean you shouldnt have to go into RDP to check the GUID. However if you do RDP in and check the processes, then the GUID assigned to the process will not match the one you supply.
I have also found that I needed to logon using administrator via RDP, before the browser will let me in. In chrome you can see it trying to send particular commands in the processes, but I am not sure why it should be more successul, it may just be local settings for me.
I now have ARMA 2 running as my test in the browser, lag etc, is low, however mouse inputs in this case are flaky. However it was only a test to see if I could get 3d rendered output.
Re: Timeouts connecting to AMI via http://aws.otoy.com
Posted: Mon Nov 11, 2013 5:08 pm
by SimonG
Otehr thing I will say is the FPS is way quicker than RDP as expected, i do have some trouble with the rendering (occasionally blocky, etc), but not framerate.
Re: Timeouts connecting to AMI via http://aws.otoy.com
Posted: Mon Nov 11, 2013 5:13 pm
by maya_man
I tried all of the stuff on this forum and have not been able to get this to work. I tried this out on the internal tests at Autodesk and it worked great. I would love to have some next steps as this is a great piece of tech.
thx.
cv/
Re: Timeouts connecting to AMI via http://aws.otoy.com
Posted: Mon Nov 11, 2013 8:33 pm
by danh
Oh well.. Tried everything on this forum again tonight and no luck.. Am at a loss as to why I can't get things up and running.. Still "timeout" errors..
Will keep an eye on the forum in the hope that the issues can get resolved.
Re: Timeouts connecting to AMI via http://aws.otoy.com
Posted: Mon Nov 11, 2013 10:42 pm
by rspeicher
After making the substitutions the trick for me to connect was to retype all the semi-colons; otherwise very vanilla. Prior to that I kept getting the timeout error.
Thanks all for the information!
Re: Timeouts connecting to AMI via http://aws.otoy.com
Posted: Mon Nov 11, 2013 11:20 pm
by Goldorak
Hi everyone - yes, on windows, if you copy and paste from the PDF, it will mangle the ";"s with unicode. We have asked Amazon to let us post the document in HTML format so this is not an issue. We'll keep you posted. We're also adding an FAQ.
Re: Timeouts connecting to AMI via http://aws.otoy.com
Posted: Thu Nov 14, 2013 6:04 pm
by thaithai
I also have the Timed out problem. Tried everything mentioned in this thread to no avail. This was with "Octane Cloud Workstation - Autodesk Edition". Security Group rules opened all ports from anyone.