If you set up IIS to only allow from certain IP addresses then you will only be able to access the web server from those IP addresses.
Probably what you should do is set up two virtual paths that point to one physical directory. One for of the paths is for the schools and is restricted to deny all except your legal IP range. The other should be set up to be password protected but open to access from any IP address.
Then just publish the two paths in different locations (ip protected on your BGFL portal) and the password protected one in the public domain.
Bear in mind though that you can fake ip addresses.....
Regards
Stephen [EMAIL PROTECTED] wrote:
er. yes thats the idea.
User comes to page. If they are in acceptable ip range they get page if not they must login
Thats what I want. Ideally done in IIS (but I don't think this can be done) or CFMX if all else fails
I am not IIS techy enough to get this going. I am reading the CFMX manual on this one to see what I can do.
Ideally I want to achieve this scenario.
Users in schools on our own network will not need to login (acceptable IP Address) Users on the web will need to login (unacceptable IP Adress) Users on the web that use our portal (BGFL+) won't need to login as they already have to gain access to porta and we know who they are. This info then passed to login security for whatever application needs it. The advantage here is that once the user is authenticated to BGFL+ we can use one IIS account to send the username password info. Otherwise its create thousands (I mean thousands) of accounts .... :(
-- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
