Not too sure if this is the place for this, but I'll ask and see.
Our website supports many customers. we have 1 set of base pages that ALL customers access; the pages just display the proper information for that customer. They reside on the domain: 123.somedomain.com. When our customers log into their site, they have their own page which redirects them to this domain. So the company ACNE has a domain with us: acne.somedomain.com. This has been setup for years and working fine.
We added a page for internal users to log in to. The only difference with our page and a "customers" page is a.) it resides on a different sub domain (ourcompany.somedomain.com) and it displays a list of our customers. Here's the odd part; when a customer logs in, they are redirected to the 123.somedomain.com and everything works.....when we log in, we get redirected, but the ADDRESS stays the same, just has the page names appended to the url. So we see ourcompany.somedomain.com when we should see 123.somedomain.com.
This has recently failed us with links and other things that access the data drive on our server. We have pinpointed the problem to this URL issue. We do not use Server.Transfer, only response.redirect, so I do not see that being an issue. The server is a Win2003 box with all the updates.
This used to work without any problems, for about a year. Then it stopped working one day. It almost seems like Windows Update may have caused a change or something along those lines as we didn't change any of the code.
Sorry for the long-winded question but I thought it was important to know all the facts before guessing what could be wrong.
Our website supports many customers. we have 1 set of base pages that ALL customers access; the pages just display the proper information for that customer. They reside on the domain: 123.somedomain.com. When our customers log into their site, they have their own page which redirects them to this domain. So the company ACNE has a domain with us: acne.somedomain.com. This has been setup for years and working fine.
We added a page for internal users to log in to. The only difference with our page and a "customers" page is a.) it resides on a different sub domain (ourcompany.somedomain.com) and it displays a list of our customers. Here's the odd part; when a customer logs in, they are redirected to the 123.somedomain.com and everything works.....when we log in, we get redirected, but the ADDRESS stays the same, just has the page names appended to the url. So we see ourcompany.somedomain.com when we should see 123.somedomain.com.
This has recently failed us with links and other things that access the data drive on our server. We have pinpointed the problem to this URL issue. We do not use Server.Transfer, only response.redirect, so I do not see that being an issue. The server is a Win2003 box with all the updates.
This used to work without any problems, for about a year. Then it stopped working one day. It almost seems like Windows Update may have caused a change or something along those lines as we didn't change any of the code.
Sorry for the long-winded question but I thought it was important to know all the facts before guessing what could be wrong.