locked
Domain Resolution - Strange Behavior RRS feed

  • Question

  • User-1918245185 posted

    We are seeing some strange behavior in our environment.  Our environment consists of .NET 3.5 sp1, IIS7 and Windows 2008.

    When we access our internal site, we typically type in http://mywebserver/.  Most times, this will bring up our website and you are able to navigate throughout the pages.  However, there are times when navigating throughout the site that 'all of sudden', you get thrown back to our login page.  NOTE:  The reason you go back to the log page is because the app thinks you have lost your session.

    To get around this problem, we type in http://mywebserver.company.com/.  By fully-qualifying the address, the website remains stable and user's do not get thrown out of the application.

    I am not sure if this is an IIS issue?  a network issue?

    Any thoughts or bits of wisdom would be welcomed.

     Thanks.

     Steve

    Wednesday, January 5, 2011 2:35 PM

Answers

  • User299556178 posted

    My first guess is that you have a link somewhere to http://mywebserver.company.com/. So when you use http://mywebserver/, the session is lost, because the browser is unwilling to share between the two URIs (it thinks they are different servers).

    Does the problem happen at the same place all the time? You could use a proxy in your browser such as Fiddler, to inspect the requests that are sent to the server. This should give you valuable information.

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Friday, January 7, 2011 5:03 AM
  • User-1918245185 posted

     I found the problem.  Our app was setting a static variable that contains the Url for our site.  So the first user to connect to our site would set the static variable. 

     Thanks to the community for your help.

    Steve

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Monday, January 24, 2011 5:23 PM

All replies

  • User-1672167363 posted

    Hello,

    I suggest before declaring who or what is a fault you need to

    gather a bit more information.

    For the IIS server turn on Advanced Logging and look for times when sessions atart stop or teminated.

    For the IIS server turn on Failed Request Tracking and set in to enabled and logging.

    The IIS Server does have session settings and keep-alive settings.

    I would also suggest that you get "wireshark" and make some captures for selected times of the day.

    I then suggest that you look to see if start,stop, or terminted sessions have an event in the network or other resaons.

    I then suggest that you look at what an average session time is and look is the max time is too low in IIS server.

    With some kind of  Forensic information your just guessing.

    For the logs you gather it is best if you look at the information.

    The persons using your site would object to some of the logging going in to this Forum.

    If you need help with settings just post he question and we help.

    Hope this helps

    Martin :)

    Wednesday, January 5, 2011 3:27 PM
  • User299556178 posted

    My first guess is that you have a link somewhere to http://mywebserver.company.com/. So when you use http://mywebserver/, the session is lost, because the browser is unwilling to share between the two URIs (it thinks they are different servers).

    Does the problem happen at the same place all the time? You could use a proxy in your browser such as Fiddler, to inspect the requests that are sent to the server. This should give you valuable information.

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Friday, January 7, 2011 5:03 AM
  • User-1672167363 posted

    Hello,

    Have you checked the web site bindings in the IIS Manger you may need to remove

    a duplicate binding.

    If your still having problems post the questions and the information for previos post

    to  this thread.

    Martin :)

    Saturday, January 8, 2011 5:21 AM
  • User-1918245185 posted

    Hi All,

     I downloaded Fiddler2 to try and determine what may be the cause of our of 'lost sessions'.  Fiddler2 exposed an interesting tidbit on why we may be getting out timeouts.

    Here are the steps that cause this situation:

    1.  In IE, go to http://mywebserver.company.com/MyAppDomain/Home.aspx
    2.  Home.aspx has navigation links.  I click on the link to open NewPage.aspx.
    3.  Home.aspx loads NewPage.aspx into an iFrame.  The iFrame is located in Home.aspx.
    4.  Notice how the host name changes from mywebserver.company.com to mywebserver.  When name change occurs, the NewPage.aspx does not display correctly in the iFrame.
    5.  If repeat the steps above and use http://mywebserver/MyAppDomain/Home.aspx, then I don't not experience the lost session.  Everything works as expected.

     Here is a snapshot of the results I get from Fiddler

    200  mywebserver.company.com   http    /MyAppDomain/Home.aspx
    302  mywebserver                         http   /MyAppDomain/NewPage.aspx

     

    Any thoughts on what may be causing this change in host names?

    Thanks.

    Steve

    Wednesday, January 19, 2011 1:08 PM
  • User-1918245185 posted

     I found the problem.  Our app was setting a static variable that contains the Url for our site.  So the first user to connect to our site would set the static variable. 

     Thanks to the community for your help.

    Steve

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Monday, January 24, 2011 5:23 PM