Win22 seems to be migrated, however when I point to the new IP I get on one of my domains asp.net runtime error.
So in external DNS I still point to the old datacenter to have the site up.
domain: pauwenburg.nl
old IP: 204.14.108.3
new IP: 173.0.133.178
Is there anything I can do myself, or wait, or have to create a ticket for this?
Regards,
Jan-Pieter
it is on 1.1 on the new server, it looks like DNN needing 3.5, so I moved you to 2.0(and 3.5).
It does really need a ticket, normally. The migration is not quite complete, but mountings are done on the new side. And DNS will start switching over.
This asp.net 1.1 to 2.0 change setup that was done before CP switchable is one of the more frustrating things, but at the time it was needed and best to do. It is causing some pain now however.
BTW the broadcom NIC controller on this server controls multiple interfaces and it is failing, this is the reason for migrating win22 on ASAP basis, as it is making the nic stop sending packets sometimes, the server is there up and running but can’t send packets. We’ve posted about it a couple times, swapping NICs did no good due to the controller controlling them both 
Hi Stephen,
Thanks for the quick asp2.0/3.5 enabling. Site loads now, but seems not to have full asp.net permissions yet, I get DNN disk write errors.
This was a manual step before, so I assume also now it has to be done again?
Should I open a ticket for this?
And another thing is dat db is of course still in the old dc. Can I vote for mssql3 (a lot win22 domains use this one) to be migrated asap?
Regards, Jan-Pieter
Can 't vote for it, but we are working to move all ASAP 
This does look like a manual permissions set. I’ll do it for this one but can’t readily check it (I know i could edit hosts file and all but i can’t readily reboot now on my pc, i am needing it for making changes, monitoring progress and all)
check is not neccessary, I wil do… 
Ok, works now. Thanks. I will open ticket for other domains on this server.
And I hope you can get some sleep!