>>>Hi,
>>>
>>>GoDaddy are telling me that this part of my web.config is causing my end users to hav eto log back in every 6 minutes:
>>>
>>>

    <authentication mode="Forms">
>>>      <forms loginUrl="~/Account/Login.aspx" slidingExpiration="true" timeout="120"/>
>>>    </authentication>

>>>
>>>Can anybody see any problem with this?
>>
>>Doesn't make sense to me. timeout is in minutes so you've got a couple of hours there.
>>Is this a shared server? If so I read somewhere that the machinekey may be regenerated at the server level which would leave you high and dry.
>>Can't find the detail but this refers : http://blog.falafel.com/asp-net-forms-authentication-times-out-on-a-shared-host/
>
>Hi Viv,
>
>I followed through from the link you gave me and found this link showing how to generate a machine key: https://support.microsoft.com/en-us/kb/312906
>
>I followed that and put the generated key in my web.config and recycled the app pool but it's still forcing me to log back in after 6 minutes.
>
>I would appreciate any advice on how to try resolving this.

Guess it would help to narrow down the source of the problem. Seems to me there are three (although maybe more) possibilities:

(a) App pool recycles - you could log application_start events to determine if this has happened.
(b) Cookie expires - you could check this on the browser (or with Fiddler)
(c) Auth ticket expires - maybe check this by code in application_beginrequest (or application_authenticaterequest)

Do you have access to the IIS logs ? I'd guess not but, if so, there maybe useful info there.

You could try going cookieless (providing you're not using UserData). That would also indicate whether the problem was with the cookie or not.

If you could give me uri and credentials I could look at what's happening on the client end.....