I really like the concept of IP Binding. Now, if I can get some help to figure out how to do it...
I have an application where several users are using the same database and, in fact, the same pages. So I want to use IP Binding to create an instance of the application server for each user. The main reason is to use the new ServerSetting variables in the filter for each user. That way, I think, whenever the server instance is running, the filter will work...don't have to worry about the session expiring. Some of those pages are public pages...no login... so I need the filter active all the time.
So, I have a dedicated server out on ZebraHost with a primary IP and a couple secondary IPs. I created three versions of the config file and set the IP binding in each, all on the same port ( 80 ).
Problem is, the instance on the primary IP starts up just fine (green dot, web access...everything good), but the two instances on the secondary IP's begin to start up, then stop before completing. They don't get as far as creating the log files before they stop so i don't get any error messages, just a red dot and no joy. I've tried all the usual things..rebooting, starting in a different order, but doesn't work.
Has anyone had success with this using multiple IPs on the same port? Did I miss something?
thanks,
Pat
I have an application where several users are using the same database and, in fact, the same pages. So I want to use IP Binding to create an instance of the application server for each user. The main reason is to use the new ServerSetting variables in the filter for each user. That way, I think, whenever the server instance is running, the filter will work...don't have to worry about the session expiring. Some of those pages are public pages...no login... so I need the filter active all the time.
So, I have a dedicated server out on ZebraHost with a primary IP and a couple secondary IPs. I created three versions of the config file and set the IP binding in each, all on the same port ( 80 ).
Problem is, the instance on the primary IP starts up just fine (green dot, web access...everything good), but the two instances on the secondary IP's begin to start up, then stop before completing. They don't get as far as creating the log files before they stop so i don't get any error messages, just a red dot and no joy. I've tried all the usual things..rebooting, starting in a different order, but doesn't work.
Has anyone had success with this using multiple IPs on the same port? Did I miss something?
thanks,
Pat
Comment