Does the "test-bucket" exist? Once I changed the source to this it worked for me locally:

var conn = new CouchbaseClientConfiguration();
conn.Urls.Add(new Uri("http://127.0.0.1:8091/pools/"));
conn.Bucket = "default";
conn.HttpRequestTimeout = new TimeSpan(0, 1, 0);

If does exist, then it's probably something that's blocking the streaming http connection from establishing. I usually see this with Fiddler/Charles on startup, but once the client has established it's connection you can run the http debugger with no problems. Is there something else that's possibly blocking the connection?

Yes, I created a bucket called 'test-bucket' with default settings, and created one record in it:

UniqueID1

What happens when you change 127.0.0.1 => localhost? You mentioned you are using Hyper-V? That could be the problem...have you tried running VS using admin credentials ("run as adminstrator")?

Also, try changing the Get<string>(...) to ExecuteGet<string>(..) and then checking the result.Message property.

Hi Jeff,

I've been running VS as admin the whole time, changing loopback address to localhost incurs the same result, and here is the response I get when using ExecuteGet:

Unable to locate node

If I run the app inside of one of my Hyper-V vm's (pointing to the host machine) it works.

Nick

Hi Jeff,

Looks like it was my anti-virus after all. I use BitDefender, and after disabling the firewall, anti-virus, and every other service that could be disabled I looked for other causes for this problem. I decided to try uninstalling BitDefender from my system, and it seemed to work after that. I'll be opening a ticket with them to see why this is happening, so thanks for your help, and sorry to waste your time.

Nick

No problem, just close this ticket

Also, could you please update your question with the answer? http://www.couchbase.com/communities/q-and-a/windows-81-machine-will-not-connect-couchbase

It helps the next person who encounters the problem down the road.

Thanks,

Jeff

User resolved.