Hi, make sure .exe and .rem are allowed - but the easier way is to check the urlscan.log which says what why was diallowed...
you find it at : \winnt\system32\inetsrv\urlscan... there is also an option on urlscan which allows everything but writes to the log what would have been denied in normal operation...very useful...but don't ever forget to reset that switch :) greetings dominick -----Urspr�ngliche Nachricht----- Von: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] Im Auftrag von Todd Hickerson Gesendet: Montag, 24. M�rz 2003 07:36 An: [EMAIL PROTECTED] Betreff: [ADVANCED-DOTNET] URLscan and no-touch remoting app not working Does anyone have the checklist on how to configure URLscan for no-touch windows forms apps (deployed by IIS)? I've tried tweeking the urlscan.ini file, but to no avail. I am getting a 404 error when trying to make a remoting call from the client. I ran the IIS lockdown 2.1 wizard with the "Static Web Server" template, and that seems to work. But when I also install the URLscan, remoting fails. I have not tried upgrade to URLscan 2.5, however. Thanks, Todd Hickerson =================================== This list is hosted by DevelopMentor� http://www.develop.com You may be interested in Guerrilla .NET, 24 March 2003, in London and Boston http://www.develop.com/courses/gdotnet View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor� http://www.develop.com You may be interested in Guerrilla .NET, 24 March 2003, in London and Boston http://www.develop.com/courses/gdotnet View archives and manage your subscription(s) at http://discuss.develop.com
