Well, the support specialist at WebHost4Life still couldn’t get it right.  I almost dropped them as my hosting provider.  My web sites seemed to be running just fine, then they migrated my hosting account to a new platform and server, and all went to hell in a hand basket as my previous post implied.  Every few days or a week they would say everything was fixed and working, but after a few hours it was broken again.  Sometimes when they said it was fixed, some sites reported error “403.6 – Forbidden: IP address” and some others reported error “Parser Error Message: It is an error to use a section registered as allowDefinition=’MachineToApplication’ beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.”

 

After playing around with some default page settings, I was able to resolve the “403.6 – Forbidden: IP address” error.  After checking virtual directory and application settings on these folders, I was able to resolve the “Parser Error Message: It is an error to use a section registered as allowDefinition=’MachineToApplication’ beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.” error. 

 

So, WebHost4Life support specialist failed miserably with this migration and resolving their mishap.  Clearly default page settings, virtual directory settings and application in IIS settings did not migrate from one server to the next.  Clearly WebHost4Life technical staff did not test all sub-domain sites when the migration was complete.  Clear the support specialist don’t have a clue what they are doing… which is a shame, because I have been with them for 5 years and support in the past was a lot better then this.

 

41 days after migration, I finally got fed up and resolved it my self.  All sites are now working nicely… except those that were hacked by some lame Muslim that clearly has too much time on his hands… 

 

Update, when I started this post, my sites were working… now they are not… same 403.6 error… again.

 

5 Minutes later, able to make the post.