IIS6 Fresh Install, permissions/front page extensions issue

[Plater]

Background:
About 5 years I purchased a server and installed "windows server 2003 web edition" on it. It uses IIS6. I'll call it webserver (http://webserver/)
I used a seperate PC (XP Pro) with visual studio 2005 to create a website and after some configuring i used the "Publish website" menu item to publish my website to http://webserver (no subdirectories or anything, it was published into the default website's spot)
Both of these computers are members of the same domain (not workgroup, domain)

Yesterday the harddrive died in the server2003 computer. A brand new harddrive and an install of 2003 webedition was done on it. It is also now on the domain.

I can no longer publish my website to the webserver.
I get the following message:

Unable to create the Web 'http://webserver/'.  You are not authorized to perform the current operation.
Error: Unable to create the Web 'http://webserver/'.  You are not authorized to perform the current operation.
 

On the server 2003, I have made sure (in add windows features) that the aspnet and webdav/frontpage extensions were installed. In the IIS admin I made sure they were both allowed.
I even rand the aspnet_regiis -i command from the v2.{whatever} folder and it said it installed fine. The regsvr32 on spnet_isapi.dll said it couldn't find a server install point, but i figured i hadn't made it to using the aspnet stuff yet.
I have also made sure that port 8- is open on the firewall (the development computer can see the default webpage for the http://webserver)

What settings/permissions do I need to set?
I gave the IUSR_webserver and aspnet users full access to c:\inetpub\wwwroot But I cannot think of what all else I had to do years ago to get this to work.
Anyone have any ideas?

[Plater]

It seems to be that removing and uninstalling webdev and front page extensions, then RE-installing them did the trick.
Suddenly I had far more options in the administration section and I was able to publish.
I am sure a reboot or two didn't hurt either.

[Frinavale]

That is very strange.
Thanks for posting the answer...even though it seems like it should have worked from the start.