G
Guest
I've seen a number of questions around this topic, but I can't seem to solve my issue. Here goes
We have a Windows 2000 Server that has worked for quite a while using our ASP.NET app that is set up with cookieless=true
We recently built a new Windows 2000 Server machine, but when the app is run, once the page to switched to a page with the sessionID imbedded in the url, the browser returns a 404 error. If you remove the sessionID from the url, the page is found. It appears to be either an IIS issue, a config issue or a security issue. It could be a build issue or a pathing issue also
Also, the name of the computer was changed after the software was installed. I changed it back, but this didn't seem to matter. We are all out of guesses
We have a number of hours in this setup, and I don't wish to start over and get the same results
Any help would be greatly appreciated
Rick
We have a Windows 2000 Server that has worked for quite a while using our ASP.NET app that is set up with cookieless=true
We recently built a new Windows 2000 Server machine, but when the app is run, once the page to switched to a page with the sessionID imbedded in the url, the browser returns a 404 error. If you remove the sessionID from the url, the page is found. It appears to be either an IIS issue, a config issue or a security issue. It could be a build issue or a pathing issue also
Also, the name of the computer was changed after the software was installed. I changed it back, but this didn't seem to matter. We are all out of guesses
We have a number of hours in this setup, and I don't wish to start over and get the same results
Any help would be greatly appreciated
Rick