Das kann ganz n�tzlich werden... Text reinkopiert, just in case falls der Link mal stale wird.
****************
Generally, if you want to share session state between servers in a web farm, you set up a separate state server (with the ASP.NET State Service started), and point the servers in your web farm at it. I have also seen sites that enable the state server on the local web server simply to keep session state from being dumped when the worker process recycles (which happens any time you touch web.config). Here's the problem. There's no security on the state service, and it can be remotely attacked.
With V1.1 of the Framework, you can configure the state server to not allow remote connections by setting the following registry key to 0 (the default is 1, to allow remote connections):
HKLMSYSTEMCurrentControlSetServicesaspnet_stateParametersAllowRemoteConnections
You can also change the port that the state service listens on with the following key:
HKLMSYSTEMCurrentControlSetServicesaspnet_stateParametersPort
If you're using the state server in a web farm, it's important that you put it behind a firewall or otherwise prevent anything but the web servers from talking to it.
****************
_______________________________________________ Asp.net mailing list [EMAIL PROTECTED] http://www.glengamoi.com/mailman/listinfo/asp.net
