Dotnetpanel Forums

Hi, Does anyone have any info on getting IISPassword to work with DNP IIS7 Windows 2008 x64. There is no way to specify the dll location from within the iis7 module. I am in the process of moving a number of servers from Helm to DNP and require secured folders. If IISPassword does not work, what other options do I have for secured folders on iis7???..... If this is not possbile i may have to rethink 3 weeks of work. Any assistance appreciated. Regards, CD for Uggle

If I remember correctly, IIS7 provides that functionality out of the box (the ability to secure folders with just a text file). Therefore, there should not be a need to configure IISPassword in the IIS7 module/provider as it probably does not use it.

Hi, I am ware that there are ways of securing folders, however an interface within DNP is required for our customers. We are moving from HELm and need this functionality within the DNP control panel. Regards, CD

Please go to the website you want to secure. In the Website Properties screen you will see a Secured Folders tab. Here is where you can manage security for folders in DNP. And again, I don't think you need to configure IISPassword for this to work in IIS7.

Let me know how things go.

Hi,

 I have checked the settings on this hosting plan and can confirm that the secured folders is ticked however no tab is present.

regards,

 CD

Hi

Could someone for DNP please confirm whether secured directories are possible using iis7 (if not, is there likely to be in the near future, and why have the option of enabling secured folders from within the control panel if it is not possible).
Any info appreciated as this is a basic requirement for most hosts.
Regards
CD

I am running into the same issue - Secured Folders is checked in the Web Service for the server however no Secured Folders tab exists in the properties of the web site.

In my case the server is Win2k8 32bit / IIS7.

 

We have spent 6 months using Windows 2008 x64 and are really disappointed a lot of things don't work. So we are going to migrate back to Windows 2003 32-Bit where EVERYTHING works, IIS Password, Perl, Frontpage, ASP, ASP.Net 1.1, Python, Coldfusion, Access databases, Reboots twice as fast, etc...

It's like upgrading Windows XP to Vista. A lot of things broke, drivers don't work, software don't work. Man do we regret upgrading to Windows 2008. DotNetPanel was awesome under Windows 2003. Everything just kinda crapped out in 2008. Also, another big mistake was upgrading to SQL 2008. More than 1/2 of the applications in the Application Installer are gone. I read somewhere that IIS6 outperforms IIS7. As far as I can tell there is really no reason to use Windows 2008 or IIS7 because there really isn't any new features, just a bunch of incompatible software.

Stick to 32-bit Windows 2003 and everything will work perfectly. It can still handle 8 cores and 64GB of ram (enterprise edition) without having to be on x64 edition. We are switching back this weekend,.HUGE task!!!