We have an ASP-application that uses an ActiveX server component (ATL). We
have developed the component ourself. The component opens a file in a
directory on the server, creates a socket (uses port 5001) and connect to a
socket-server program we developed, get data and write it to the open file.
When the transmission is done the file is closed.
This works fine with win2k and win2k3 except at one site running iis6 and
win2k3. There are a lot of client-pc (winxp) that are communicating with the
socket-server so that works. We logged in as administrator at the server and
executed a program that does just the same as the ActiveX-component and that
worked fine too.
Normally when the ActiveX-component don't have the right to write data or
something like that an exception is thrown and you get an error-message so
it seems like the error handling is working.
It this case no error is reported.
The user Internet Guest Account has full controll in the directory where the
file should be created.

What could be wrong ? Do iis use any port filtering software ?

Lars Lundkvist
IT-enheten
Södersjukhuset
Stockholm
Sweden

[ Post a follow-up to this message ]