Yes that's classic asp

what sort of server is it on windows?

What sort of webserver IIS? if so what version, if it is 7 or greater it is very easy to do your redirects if you have access to the controlpanel

you are correct, it want do the index.html or default.asp

but this rule will solve all your domain problems, not the "!" mean not, so if not the desired domain, then redirect to the desired domain not matter what the domain is. this will fix non www, or any other secondary domain you may have such as oldDomain.com or mergedSite.com

Options +FollowSymLinks RewriteEngine On
RewriteCond %{HTTP_HOST} !^www.domain.com$ [NC]
RewriteRule ^(.*)$ http://www.domain.com/$1 [R=301,L]

but if you have a page called default.asp. your site is a classic ASP site, ASP is a Microsoft technology and would be on a Microsoft web server IIS. if so 301 redirects are very easy to do.

Is your site ASP.is it on a Microsoft IIS server?

Depends on the site, if the site is Microsoft.com with a link from the home page, you can expect it to appear same day.
If its on boringoldsite.com then it could take a week or more.
But mostly a few days

Agree with Paul here.

A 301 is a directive to the crawler, while a canonical tag is only a hint and is not always followed. Bing for one will ignore canonical tags if it believes they are misused.

as for the mention of "multiple 301 redirect" .

You do not need to have a 301 redirect for every url, just follow the logic
if HTTP_Host is not myPreferredDomain then redirect to myPreferredDomain

I read a post by bings Duane Forrester where he explained that they will lose trust in your site map if it has errors more then 2%. all entries should return status code 200, no 404's or redirects.

He also said that you should not include all pages, just places where you want bing to start crawling from, or where you want to discover links.

I agree with mike, but I am curious why you cant have a xml sitemap, maybe you need to chage hosting