ODR conflict with IIS?

tgerber

We have a situation. Our security folks won't let us publish over any port other than 443 to our Internet servers (due to gov't regulations for security).

So we have ODR configured to its own IP and port 443.

It seems that when the server is restarted the ODR starts first then IIS. What seems to happen is that any HTTPS traffic to the web sites doesn't get routed to IIS properly even though they are on different IP's.

If we make ODR start after IIS is up and running things appear to be Ok.

Has anyone heard of anything like this? or know why this might be happening? Is this a bug I need to open with Interwoven?

Thx

Edited by tgerber on 07/05/05 05:41 AM (server time).

stefanmaier

Hi,
you say, that you have configured an own IP adress for OD.
Did you configure your IIS correctly, so that its listening on another IP adress and not on all interfaces?

Anyway, I don't know if it's really working to give an network interface two
IP addresses and connect two different applications two the same port on these.
You should open another port for OD on your server like 20014.
An application will not be safer in principle only when its running on port 443.
To control the requests on your server you can use your installed firewalls (I think, you will have some...)

Regards
Stefan