D
D Witherspoon
We are moving from a Windows 2000 Server to a Windows 2003 server. Our
ASP.NET web applications work fine on IIS 6.0 on the Windows 2000 and
Windows 2003 server.
All of our no touch deployment .NET Windows applications work fine on
Windows 2000 server but when we move them to Windows 2003 Server / IIS 6.0
the following happens:
1) User access the EXE via URL... (ex:
http://new2k3webserver/somefolder/someapp.exe)
2)User is prompted to enter user name and password
3)User can click cancel and the application will run normally, or user can
type in their domain account information and the application will run
normally.
This is a big nuisance. Does anyone have any suggestions. This happens
with out most complex applications and our simple applications. As a test,
I wrote a .NET 1.1 WinForms application with no lines of code and only a
Form at start up and the same problem occurs when I post it to Win2K3 / IIS6
as a no touch deployment app.
All suggestions welcome.
D.
ASP.NET web applications work fine on IIS 6.0 on the Windows 2000 and
Windows 2003 server.
All of our no touch deployment .NET Windows applications work fine on
Windows 2000 server but when we move them to Windows 2003 Server / IIS 6.0
the following happens:
1) User access the EXE via URL... (ex:
http://new2k3webserver/somefolder/someapp.exe)
2)User is prompted to enter user name and password
3)User can click cancel and the application will run normally, or user can
type in their domain account information and the application will run
normally.
This is a big nuisance. Does anyone have any suggestions. This happens
with out most complex applications and our simple applications. As a test,
I wrote a .NET 1.1 WinForms application with no lines of code and only a
Form at start up and the same problem occurs when I post it to Win2K3 / IIS6
as a no touch deployment app.
All suggestions welcome.
D.