Why is a VERY long story, but the physical setup is very easy to explain.
The external network in question is ethernet. Our internal network is also ethernet. We have a VAST array of hardware we could potentially throw in between - ranging from purpose-built PC routers, to consumer routers, to Cisco 2500-series routers. However, our situation requires us to restrict traffic through those routers to stations where certain authorized users are logged on. Unauthorized users will use the same stations, so authorization CAN NOT be done on a per-PC basis.
We have an ActiveDirectory setup in place which we would like the authentication to be based off of if possible (though this is by NO means neccessary), and by the time this goes to implementation, will run Windows Server 2003 R2 on all our domain controllers and servers. We are not in a position to purchase any further software (i.e. ISA server), though we are willing to double up roles on one of our existing Win2k3 servers, and can use as many Unix/Linux/whatever is neccessary systems to accomplish this.
We also have a programmer available who learns quickly - if we need to code anything in any language, we can get him to do it. And it is COMPLETELY AND TOTALLY ESSENTIAL that this be a 100% bulletproof method. If they don't have an authorized user account, they won't get a single packet through the router.
The external network in question is ethernet. Our internal network is also ethernet. We have a VAST array of hardware we could potentially throw in between - ranging from purpose-built PC routers, to consumer routers, to Cisco 2500-series routers. However, our situation requires us to restrict traffic through those routers to stations where certain authorized users are logged on. Unauthorized users will use the same stations, so authorization CAN NOT be done on a per-PC basis.
We have an ActiveDirectory setup in place which we would like the authentication to be based off of if possible (though this is by NO means neccessary), and by the time this goes to implementation, will run Windows Server 2003 R2 on all our domain controllers and servers. We are not in a position to purchase any further software (i.e. ISA server), though we are willing to double up roles on one of our existing Win2k3 servers, and can use as many Unix/Linux/whatever is neccessary systems to accomplish this.
We also have a programmer available who learns quickly - if we need to code anything in any language, we can get him to do it. And it is COMPLETELY AND TOTALLY ESSENTIAL that this be a 100% bulletproof method. If they don't have an authorized user account, they won't get a single packet through the router.