OTOY Forums

One of the problems with timeout is that something is wrong with the client link in OTOY-EC2-AMI.pdf.
If you copy/paste that link, you will need to manually retype all semicolons. You can see that something is wrong if you paste the link in Firefox address bar and then copy/paste it again. All semicolons will be replaced with %CD%BE except the ones you typed manually.

One other thing that can also create timeout problem is that if you are using automatic GUID, it can change while connecting and disconnecting with the client. Safest thing is to have an open RDP connection and copy or retype GUID from process list, just before connecting with the client.

You are correct on both of these issues.

The GUID is a security requirement requires by AWS. The best way to use it is to put it in the metadata so it never changes and you have it ready to go without using RDP/SSH.

The PDF document issue with copy and paste is also correct. We have asked Amazon to let us publish the document as HTML, we will do so as soon as they give us the green light.

I'm having the same issue, yesterday I been able to get just a green screen but today it's not working at all.

I created mine from the east us version, created it with GUID and it worked, to a point. I can see a very pixelated screen and it kind of connects, but it is a starting point!

Simon - where are you connecting from, what browser do you use, and how much bandwidth is available on your connection?

Hi all,

I am having exactly the same timeout problems as other users in trying to access the Autodesk AMI. I've tried Europe and US East regions (I am based in the UK).

I tried using the automatically generated GUID and specifying it in the user data fields in AWS.

I have specified the URLs correctly and tried with Chrome, IE and Firefox.

Other than sending a PM to turn off the GUID check is there a proper solution to this?

I don't want to keep starting and stopping g2 instances and associating/disassociating IP addresses since this is costing me money and I don't have anything working yet!

Dan

Goldorak wrote:Simon - where are you connecting from, what browser do you use, and how much bandwidth is available on your connection?

My instance is in the US, and my connection from home is around 2MB. I have tried this from work today and get significantly better results, the screen is still a little blotchy, but at least readable. Not sure if there are settings I can change to improve things?

danh wrote:Hi all,

I am having exactly the same timeout problems as other users in trying to access the Autodesk AMI. I've tried Europe and US East regions (I am based in the UK).

I tried using the automatically generated GUID and specifying it in the user data fields in AWS.

I have specified the URLs correctly and tried with Chrome, IE and Firefox.

Other than sending a PM to turn off the GUID check is there a proper solution to this?

I don't want to keep starting and stopping g2 instances and associating/disassociating IP addresses since this is costing me money and I don't have anything working yet!

Dan

Did you create the instance with the GUID in the user data before you launched? This seemed to work for me, whereas adding the userdata afterwards didnt work?

Mine also only seems to like Chrome for some reason

The latest thing I have noticed is that you have to have logged on to the machine for it to pick up the desktop? It appears the act of logging on, gives you a desktop to view.