Server 2008 R2 Domain workstation keeps getting logged out of 1 website (Session expires)


Recommended Posts

I have a Windows 2008 R2 Domain server with 12 Windows 7 Professional workstations with Active Directory.  There is 1 website that non of the workstations can access.  When I try to login to this particular website it immediate logs me out.  Please help!

Edited by Nick H.
Malformed links.
Link to comment
Share on other sites

can we have a bit more information?  network info would help, where the website is located (internal/external), what your domain is in relation to the website domain.

Link to comment
Share on other sites

The hardware configuration is 2 DSL lines coming into a Cisco RV042G Dual WAN Router, which is doing the DHCP to the network, which feeds a 24 port switch, Windows 2008 R2 Server with Active Directory.  My domain is internal the website I'm having problems with is external.

Link to comment
Share on other sites

Try disconnecting/disabling one of the dual wan router dsl links.  See if that fixes the issue.  It could be an issue where the server does not like trying to figure out what side to connect back on and forces a reset on the page. 

Link to comment
Share on other sites

 

 

I'm just going to be hard headed.  I read your link but I still don't understand how load balancing causes the same external website to log the users out immediately after the login.  Just ONE website and the go to hundreds of different websites a day.

Link to comment
Share on other sites

The issue is simple.  when you send out a request to a website (it may not happen for all) on a dual link, it goes out one side and everything is ok, but when the computer tries to connect again it goes out the other, the web site then says woah!!!! I don't trust the information you are sending, you just sent from this other address....please logon again so I know you are you....and this keeps going around and around and around...and you are stuck with the issue you are facing.  You can sniff the traffic if you want to see if I am correct, you can disable one of the links to see if I am correct, or you can follow the instructions in the link I provided to see if I am correct.  So, how are you going to verify my theory?

Link to comment
Share on other sites

That makes sense.  I'll disconnect one of the dsl lines from the dual wan and see if that solves the problem.  BUT THEN, what do I do about connecting the disconnected dsl line and not causing the problem again?  Bind HTTP to one and HTTPS to the other?  I understand what you're saying, but why the 'same web site'?

Link to comment
Share on other sites

The solution is to bind the protocol to one or the other.  usually https and ftp are the ones that give you issues. I won't speculate as to why one and not all, I don't know the entire situation/setup on both ends.

Link to comment
Share on other sites

Start with the protocol you are having an issue with.

I mentioned ftp because that has issues with link balancers also.

Http usually not an issue.

Link to comment
Share on other sites

I know you've probably tried, but it is it the browser you're using? Have you tried accessing the website on a non-domain joined PC on the same network?

Link to comment
Share on other sites

HTTPS will give you issues on the RV042G with a 50/50 load balance; If you do fail over only, you'll be alright.

 

If you bind it to one WAN connection (just HTTPS) you'll be fine as stated before.

Link to comment
Share on other sites

I think the first change I'll make to the RV042G from everyone's comments, and I do appreciate your help, is change from 'load balance' to 'fail over'.  It's just one simple setting change and then see what happens.  I like to adhere to the saying, 'Keep It Simple Stupid'.

Link to comment
Share on other sites

Changing the dual wan router from load balancing to smart link backup or failover worked.  It had to be a DNS issue but I don't know why.  Thanks for everyone's help.  I really appreciate it.

 

Mike

Link to comment
Share on other sites

dns doesn't work like that on the client level.  once the address is cached it retains that for a while, a restart or a manual flush would be 2 ways to immediately clear the cached entries on the local computer level.

 

It wasn't a DNS issue. Glad it is sorted for you, if you decide to change it back, follow the instructions to bind https (only https, not http, not port 80) to one of the links.  If you are having an issue with http on a specific site, bind communications to the site to a link.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.