Solution: Windows Server 2003 comes with a service "ASP.NET State Service". It is set to manual by default. You need to do a few things to configure it to be used as a central State Server.
- click start - services.msc - ok
- find "ASP.NET State Service" change its startup type to automatic and start it
- open command prompt
- netstat -ano | find "42424" | RESPONSE TCP 127.0.0.1:42424 0.0.0.0:0 LISTENING 5640
- run REGEDIT
- NAVIGATE to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\aspnet_state\Parameters
- Change "AllowRemoteConnection" Value Data from 0 to 1
- Restart the service
- Re-run the command from step 4
- netstat -ano | find "42424" | RESPONSE TCP 0.0.0.0:42424 0.0.0.0:0 LISTENING 1240
- Now that it is listening on 0.0.0.0 it means it can receive requests from other servers.
Then of course - inside your app's web.config file you'll need to add two things:
1. Machine Key: made up of a validation key & a decryption key.
2. reference to your new state server you configured above