As a guess from your description - Proxy/cache servers and some firewalls
have a nasty tendency to consume your NTLM credentials, thus leaving nothing
to pass between client and server, thus your session is lost as your system
cant maintain the session. Turn on basic and NTLM for your site and see if
you manage to maintain your session to prove if its this.
--
Regards
John Timney
ASP.NET MVP
Microsoft Regional Director
"Egghead" <ro**************@shaw.ca> wrote in message
news:ew**************@tk2msftngp13.phx.gbl...
Hi UJ:
I have this funny behaviour, somehow, I lost the session variables as
well.
I know it have nothing to do with timeout or session state setting. I hear
it has something to do with the firewall and security setting.
Egghead
"Scott Allen" <sc***@nospam.odetocode.com> wrote in message
news:05********************************@4ax.com... Hi UJ:
No - no need to do databinding. Are you losing session variables? What
is happening?
--
Scott
http://www.OdeToCode.com/blogs/scott/
On Wed, 18 May 2005 10:34:23 -0400, "UJ" <fr**@nowhere.com> wrote:
>I've noticed some odd behavior so I thought I'd ask the question - when you >set a session variable, do you need to do a databind after that? It almost >seems like you need to.
>
>J.
>