We have a newly configured Windows 2003 server and we have installed our ASP.NET 1.0 application to it. This ASP.NET application is already running on another Windows 2003 server without any problems.
Here's the scenario. Users log-in from another ASP.NET application from another server, Server1, and then gets redirected to the second web server, Server2. The entry/default page of Server2 simply sets up some session variables then redirects to another page. The problem is that on the second page, the session variables that were set-up in the entry/default page is not available. The session variables are all NULL.
The weird part is if we go straight to the entry/default page of Server2 without going through Server1, the session variables become available on the second page.
How can we overcome this problem? For us we believe this is IIS 6.0 security-related and we just don't know which settings to look for.
Hope this is clear enough and thanks in advance.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
How is your authentication configured? Almost sounds like when you go directly you're hitting the server as a specific user and retaining session state. When you cross from Server1 you may be authenticating as Network Service or another generic account that isn't maintaining session.
If you aren't sure, try displaying the user credentials on your Server2 page and hit it both ways to see the difference.
You may be running into a problem where if you come off of a redirect, then you are getting a new SessionID as opposed to going to the page directly after the session variables are set up.
So I would also try to display the SessionId of both scenarios, show it when you redirect to the page, and then see what it is when you browse directly to the page.
My bet is that they will be different.
Session.SessionId.ToString
Ben.
Using the same application on another server (Windows 2003/IIS 6.0), it doesn't give us any problem. Basically we have three web servers. The first one is where users will initially connect, Server1. Then the other 2 servers, Server2 and Server3 will contain the same application. That application is already running without any problems in Server2. We just configured a new server, Server3 and we are trying to run the same application to it. But we are getting the problem described above in Server3 but not in Server2.
Hope this gives some more light to my problem.
I understand, and fundamentally the Session variables are getting set it seems, but it appears that the settings are different on Server3 than they are on Server2 because you are running into a problem.
I have never seen an application or done this kind of thing so I am not sure what you could be running into.
Business Accounts
Answer for Membership
by: naveenkohliPosted on 2006-04-21 at 10:58:56ID: 16509696
Two applications can not share sessions.