AWS connection always giving "Authentication Failure"

AhmedKamal · Tue Nov 12, 2013 5:25 pm

Hi,

I'm really interested in testing this out, I want to demo it for a client as well who was asking about the feasibility of cloud based Auto-desk software. I keep getting Authentication failure when I connect with firefox. I'm pretty sure my GUID is correct! I rebooted the instance from AWS console, I got a new GUID .. This too results in Authentication failure

Can anyone help me please .. Thanks

Wed Nov 13, 2013 12:36 am

Hi Ahmed,

I will send you a PM shortly.

J.

robrob12 · Wed Nov 13, 2013 8:43 am

Hi,

I have the same issue. Ip is correct, guid too.

"Authentication failure"

Thank you

robrob12 · Wed Nov 13, 2013 9:19 am

A few more details:

- AMI-OTOY-OCTANE-WINDOWS_1.0-1765694b-3372-4e71-9d75-0703468ad20d-ami-8f5d16e6.1 (ami-488c6b3f)
- Security group "Octane Cloud Workstation-1-AutogenByAWSMP"
- no modifications
- Location EU (Ireland)
- tried own guid - no success

Hope this helps to find my mistake...

robrob12 · Wed Nov 13, 2013 10:18 am

Found the mistake. By typing the URL by hand everything works well.

AhmedKamal · Wed Nov 13, 2013 3:11 pm

robrob12 ... Interesting! I'll try to manually type it then .. Did you spot the error in the copy/paste'd URL ?

@Jax .. You guys should probably create a cloud-formation script that launches the VM, and spits out a one-click URL that has all the parameters needed already built in. If you'd like to work with us (http://cloud9ers.com) to create that for you (We're a AWS consulting partner) I'd be happy to. It'll just make your customers life easier

Wed Nov 13, 2013 5:58 pm

Ahmed,

Most of our support issues come from people copying the connection string from the PDF initially. We've asked Amazon to let us put up an HTML version and are waiting to hear back from them.

AhmedKamal · Wed Nov 13, 2013 8:21 pm

Thanks Goldorak .. The good news is, typing in the URL by hand, did resolve the issue and I got connected (woohoo!)

The bad news is, the "tcpsvcs" program kept crashing every 5 mins .. especially it seems when CPU load was at 100% (rendering) .. Should I consider the current state of the code as experimental, or should it be close to production ready, but maybe I'm hitting some weird bug ..?

Thu Nov 14, 2013 3:51 am

You should not use CPU rendering on all 8 cores. Limit the CPU rendering (via affinity settings) to at most 6 cores. We will enforce this in the host automatically to cover high CPU user mode applications.

kotaKat · Tue Dec 24, 2013 2:58 pm

I'm running into the authentication failure issues on my instances too. So far I've tried terminating and relaunching my instances, setting my own GUID, not setting my own GUID, using my IP, using my DNS... no matter what, it fails to authenticate (but will let me in on RDP).

Does it matter if I'm using Spot Instances? I know I'm not being terminated when I connect -- they're well alive.

AMI - AMI-OTOY-OCTANE-WINDOWS-ADSK-1.0r1-e0e7f1f9-4a16-4477-8fd0-df949f1b8947-ami-53eeb03a.2 (ami-a91d44c0)
Instance type - g2.2xlarge