Yes.

13 hours down is unacceptable, just make sure that it was their problem, not yours, before making the switch. Otherwise, you just move your problem elsewhere.

---

Eric Swanzey
www.swanzey.com

duchoangle,

A few comments regarding your situation.

I have a tutorial about backing up and restoring a DNN site available at http://www.mitchelsellers.com, you have the general idea of backing up ALL website files and migration to the new server.  You will then need to properly configure IIS and file permissions on the new server. 

If you switch to a different hosting provider I would also strongly recommend moving the database to a new hosting provider as well.  Having the database in close physical proxmiity to the webserver helps cut down on database connection latency and helps keep a solid performing site. 

If you are looking for a new provider, I highly recommend 3Essentials, their support is awesome and the plans are resonably priced.  (If you are interested please click my referral link in my signature here....it is appreciated).

Regarding your machine key values, those MUST remain the same.  if they get changed no users will be able to login to the site....

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services