Guest Tom B. Posted July 15, 2008 Posted July 15, 2008 Hi. I have a user who uses a PC to connect to a terminal server for a specific application. He will be able to connect for a day or two and then after that any time he tries to connect he immediately gets 'session expired'. If he goes to another PC, he can work fine multiple days, the issue never occurs. If another user uses his PC the issue will happen to them. So it seems to be an issue occuring that's specific to the computer. If we rename his local profile (C:\Documents and Settings\xxxxxxxx) and have him log back in, he can then connect again for a day or two then the issue occurs again. Does anyone have any ideas what might be occurring? -- Tom B.
Guest Tom B. Posted July 15, 2008 Posted July 15, 2008 RE: Session Expired I have some more information. This doesn't seem to be a terminal server issue, so this post should probably be moved to IE7 or IIS. User has b.c.com set up as his home page. At that point there is a logon required to access the site. However, even without logging in, he'll go to a.b.c.com, then login there and when he tries to start the application gets Session Expired. (Treat the previous websites as litteral, a.b.c.com is underneath b.c.com on the same server). I simply changed his home page to something else entirely and had him go directly to a.b.c.com and open the application and the problem does not occur. There are no cookies saved during any of this process, so it has something to do with the first site, b.c.com, establishing a session, and the second site which is underneath the domain, a.b.c.com, having a problem with that open session. Any ideas? -- Tom B. "Tom B." wrote: > Hi. I have a user who uses a PC to connect to a terminal server for a > specific application. He will be able to connect for a day or two and then > after that any time he tries to connect he immediately gets 'session > expired'. If he goes to another PC, he can work fine multiple days, the > issue never occurs. If another user uses his PC the issue will happen to > them. So it seems to be an issue occuring that's specific to the computer. > If we rename his local profile (C:\Documents and Settings\xxxxxxxx) and have > him log back in, he can then connect again for a day or two then the issue > occurs again. > > Does anyone have any ideas what might be occurring? > > > -- > Tom B.
Recommended Posts