SP2013 Distributed cache issues

I have read through any possible solution so far.

I cannot get Distributed cache started properly thus giving me the 6sec timeout before getting pages, newsfeed doens't work etc.

I have tried:

Remove/Add-SPDistributedCacheInstance and several other scripts as found on the internet.

Changed account which I had setup for this service to farm account.

Removed appfabric and reinstalled it manually with /gac switch

ICMP echo and firewall rules added manually to firewall / disabled firewall altogether.

Also i found a reference in my localhost file 127.0.0.1 MACHINE and removed it.

Any cmd-lets show a good configuration, reg information corresponds with distributedcache.exe.config

Installed seperate host for the distributed cache and set it up properly then the following error is produced on the machine hosting the website but MACHINE is changed to MACHINE2

This is the exact error message as produced by ULS:

Unexpected Exception in SPDistributedCachePointerWrapper::InitializeDataCacheFactory for usage 'DistributedLogonTokenCache' - Exception 'Microsoft.ApplicationServer.Caching.DataCacheException: ErrorCode<ERRCA0017>:SubStatus<ES0006>:There is a temporary failure. Please retry later. (One or more specified cache servers are unavailable, which could be caused by busy network or servers. For on-premises cache clusters, also verify the following conditions. Ensure that security permission has been granted for this client account, and check that the AppFabric Caching Service is allowed through the firewall on all cache hosts. Also the MaxBufferSize on the server must be greater than or equal to the serialized object size sent from the client.) ---> System.ServiceModel.ProtocolException: The requested upgrade is not supported by 'net.tcp://MACHINE:22233/'. This could be due to mismatched bindings (for example security enabled on the client and not on the server).    Server stack trace:     
 at System.ServiceModel.Channels.ConnectionUpgradeHelper.DecodeFramingFault(ClientFramingDecoder decoder, IConnection connection, Uri via, String contentType, TimeoutHelper& timeoutHelper)    
 at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.SendPreamble(IConnection connection, ArraySegment`1 preamble, TimeoutHelper& timeoutHelper)    
 at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.DuplexConnectionPoolHelper.AcceptPooledConnection(IConnection connection, TimeoutHelper& timeoutHelper)    
 at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)    
 at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)    
 at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)    
 at Microsoft.ApplicationServer.Caching.CacheResolverChannel.Open(TimeSpan timeout)    
 at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)    
 at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)    Exception rethrown
 at [0]:     
 at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)    
 at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)    
 at Microsoft.ApplicationServer.Caching.CacheResolverChannel.OpenDelegate.EndInvoke(IAsyncResult result)    
 at Microsoft.ApplicationServer.Caching.ChannelContainer.Opened(IAsyncResult ar)     -
 -- End of inner exception stack trace ---    
 at Microsoft.ApplicationServer.Caching.DataCache.ThrowException(ResponseBody respBody, RequestBody reqBody)    
 at Microsoft.ApplicationServer.Caching.DataCacheFactory.GetCacheProperties(RequestBody request, IClientChannel channel)    
 at Microsoft.ApplicationServer.Caching.DataCacheFactory.GetCache(String cacheName)    
 at Microsoft.SharePoint.DistributedCaching.SPDistributedCachePointerWrapper.InitializeDataCacheFactory()'.

The only thing i can think of left to try is:

Move website over the the secondly installed host and see if it is a host specific problem or that the problem returns.

Perhaps you can think of other steps to take to troubleshoot this issue?