So long as cookies are enabled....<BR><BR>Then its probably how you programmed that page...<BR>Do you perform a check to see if the Session exists and use the session values...<BR>And if they dont exist, set new sessions...<BR><BR>Or do you call Session.Abandon anywhere on that page??<BR><BR>Do you do anything like that on this page...<BR><BR>Post the code you have on that page and we can take a fast look...<BR>
So what you are saying is that the only<BR>ASP/VBS Script on this entire page is the following line...<BR><BR><% Response.Write "<BR><font size=1>ID " & (Session.SessionID) & "</font>"%><BR><BR><BR>There is no more asp coding done?<BR>Are you directed to this page from another page?<BR>Or this is it as far as coding goes?<BR>
well, this is the front page where the user starts. the only reason I'm response.writing the ID was to try and figure out whats going on. And it changes everytime I refresh. I have anouther site where I also wrote out the session Id and that worked fine, so its not my browser.
this is the front page where the user starts<BR><BR>So at this point "On this page" you have not used your own asp/vbs code to set a session correct?<BR><BR>You are just checking to see what session was assigned by the system?<BR><BR>
Ive seen this happen sometimes...<BR><BR>Might be firewall related or if your behind a proxy...<BR>What you should do just to make sure is to just set a cookie with some value (Dont set a session)<BR>And just test to see if the cookie and value is being set...<BR><BR>that being first thing to look at...<BR>Want to be sure you are actually accepting cookies and thats the only way to be sure 100%<BR>