Hello, I could use a little help about now.

I opened up an account with seekdotnet.com, and installed and configured a DNN 4.0.2 installation. Got the main portal set up, then created another portal named 1412. I spent a lot of time getting the second portal set up, and then late last night I went poking around the host's control panel (copanel?). The way the DNN install was sorking, to get to the second portal the URL looked like www.mydomain.com/1412. I wanted it to look like 1412.mydomain.com instead, and so I created a "virtual subdomain" named "1412". Bad Move.

From that point forward, I could only get 404 errors when I tried to access either the main site or the second portal. After a few hours, I gave up and turned in a support ticket for them to fix it. They came back and said that it was fixed and that it was due to a "bad virtual subdomain definition". That sounded about right, so I continued.

The problem that I have now is that I cannot reach my second portal, 1412, at all. I have tried every URL variation that I can think of, but I get a 404 error. Next, I tried creating a new portal to see if I could get to that one. I created a portal named "Temp", and set the alias to www.mydomain.com/Temp, but I still cannot get to the portal. Finally, I noticed that the URL for the 1412 portal showed up with "/tabid/39/..." in it, and I remembered that before I messed it up it was 74, so I changed the 39 to 74 and it worked!

Can anyone tell me how DNN can get messed up like this? Is it a database row that points to the wrong tabid? Is there a way to fix it, given that I cannot access my SQL admin interface on seekdotnet (Don't ask)?

Help! I'm about to just go get a host that has a telephone in their support group and start over.

Desi