I think I'm encountering the same problem with a different ASP program. If your tests are fine on four computers, and you stick on Page B with one, it's a problem with HOW your redirect is executing on that machine, right? I'm still a novice with ASP, but doesn't Response.Redirect call a header? If your client's machine has an over-active privacy setting in its anti-virus (blocking headers - Zone Alarm will block headers), one would anticipate that the form on page A would post to page B, and the Redirect method calls the header to Page C, which is blocked, so the browser stops at Page B. Am I over-simplifying this? Disable your client's anti-virus or firewall and see what happens. IEAN, would Server.Transfer be a better method for directing to Page C? Is there any disadvantage to this? My program is a login program which writes session cookies and redirects using Response.Redirect. It works on 5 of 7 machines I've tried. I just wanted to get a second opinion before I started manipulating code.