Re: Problem deploying forms authorization

Thanks for your reply Haim,

So no matter on development machine or production machine, the ASP.NET web
application and the SQL Server database are always on the same machine,
correct? If so, I'm feeling a bit confused since the error message contains
a "remote connection not allowed ...." info which should only occur when
there is db connecction and request from remote client.

Sure, I think the problem is related to the forms authentication part,
however, I don't think the problem is the code logic since the code logic
is quite straighfoward and most of them are calling some data access
component(TableAdapter ....). There should be something incorrect with the
security context.
When you run the application on development box, since it run in VS IDE
test server, the security context is the logon user, while host in IIS, the
security context is IIS worker process account, as you've also used
<impersonate ....> setting, is the username & password credential matches
the logon user on development machine?

Currently, I would still suggest you try simplify the problem application.
You can try pick some data access code (within the forms authentication
code logic) out and put them into a single page and run that page
individually(you can remove forms authentication when perform this test) so
as to repro the same error. If we can repro the problem like this, it would
be much easier to continue troubleshoot.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.


.

Relevant Pages

  • XMLHTTP and Windows 2000 server
    ... which will display data from SQL Server database by using ... Microsoft XMLHttp. ... matching with the development machine. ...
    (microsoft.public.win2000.general)
  • Copied Website windows authentication not working
    ... I just used VS2005 to copy a new website to a staging server within our ... The application uses Windows authentication. ... development machine, everything works fine, on the staging server, ...
    (microsoft.public.vsnet.general)