Shockwave flash files

One of my websites on my win2000, IIS 5 web server is
written in flash. It is mantained by our art dept - my
only job is to save the files out to the server.

The art dept just recently noticed a problem with some of
their pages. This problem only occurs when Netscape is
the browser. When they bring up the file as a .swf
extension, they get this error: The file ".swf" is of
type application/octet-stream (Untyped Binary Data) and
it doesn't know how to open it. Although, if the file is
embedded in html code, Netscape can pull it up just fine.

I pulled in a .swf file from another site to eliminate
file-level problems. Same error on the imported file.

I don't think the problem is the server, but as I can
find no information what so ever on this problem. I
thought I'd pose the question here, and see if anybody
had any ideas of what I can do server side that might fix
the problem?

Thanks in advance!

Not sure how to fix it, but here is my answer. The
problem is server side.

IIS contains a large list of default MIME types; if IIS
hasn't explicitly mapped an extension, it returns a MIME
type of "application/octet-stream."

 >-----Original Message-----
 >One of my websites on my win2000, IIS 5 web server is
 >written in flash. It is mantained by our art dept - my
 >only job is to save the files out to the server.
 >
 >The art dept just recently noticed a problem with some
of
 >their pages. This problem only occurs when Netscape is
 >the browser. When they bring up the file as a .swf
 >extension, they get this error: The file ".swf" is of
 >type application/octet-stream (Untyped Binary Data) and
 >it doesn't know how to open it. Although, if the file
is
 >embedded in html code, Netscape can pull it up just fine.
 >
 >I pulled in a .swf file from another site to eliminate
 >file-level problems. Same error on the imported file.
 >
 >I don't think the problem is the server, but as I can
 >find no information what so ever on this problem. I
 >thought I'd pose the question here, and see if anybody
 >had any ideas of what I can do server side that might
fix
 >the problem?
 >
 >Thanks in advance!
 >.
 ><!-- ~MESSAGE_AFTER~ -->