Re: IAS as RADIUS




"Phillip Windell" <@.> wrote in message
news:ebvtlIr0GHA.1288@xxxxxxxxxxxxxxxxxxxxxxx
First, IAS is RADIUS. IAS is just MS's name for their deployment of it.
Second, RADIUS is not the solution for anything that I have read here yet.
RADIUS still requires Domain Accounts to be on the domain,...which you
already said you don't want to pull users from. If you create local
accounts on a particular server (like maybe the ISA Server) then RADIUS is
not used for that.

Let's go back to the beginning.

Define "access".
Access to what? Access from what? Access to where?
Is access simply getting an IP# from DHCP?
Is access retrieving a resource on the LAN?
Is access opeing a web page on the Net?
What is not considered "access"? (that may sound silly but it is not).

We can not figure out a way to stop something if we don't know what it is
we are trying to stop.


Let's define access as haveing access to any resource. web, network,
anything. if they are unauthorized, i want it to be like they're not even
plugged into to that ethernet port. Ideally, i'd like a group that once
granted access is only allowed out of port 80(and maybe 443, or mail ports
if they need it). this way they cant wreak havok on our network, but they'd
be able to browse and read mail as needed. But i need to get a system in
place to restrict access all together before i can get fancy and try to give
them limited access.


From Neteng:
The "supplicant" is a piece of software on the client PC. Windows XP is the
only MS OS that comes with a 802.1x supplicant (but a poor one). 802.1x was
developed to prevent unauthorized PC's from being placed on the network.
Note I said PC's, not users. Do you want to prevent non-corporate PC's from
being on the network and/or unauthorized people from getting on the
network?
MAC ACL's would be horrible to manage so I would try and stay away from
that.


Ah ok, i get you on the supplicant thing now. I dont anticpate anyone
trying to plug into our network with a pre-XP machine, however if i have to
configure 802.1x on each PC trying to plug into our network that could be as
much of a management nightmare as MAC filtering.
Preventing unauthroized PC's from being placed on the network is exactly
what im going for, i'd much rather these outside users use one of our
workstations, but i think you and i both know that isn't going to happen.
i'm compltely open to idea's, if you have any links that will get me going
that'd would be much appreciated.


.



Relevant Pages

  • Re: IP address assignment problem
    ... I have a little problem and seek for ur thoughts, let's assume I'm in a very open environment where everyone can very easily try to get his/her laptop on the network and IP addresses are assigned by a DHCP server and we are in a domain environment, how do I prevent machines that are not part of our domain to be assigned an IP address? ... This approach doesn't stop your rogue clients from connecting to other clients, but merely doesn't give them the information they normally need to do so. ... Using 802.1x, your workstations authenticate through the switch to a radius server before they are allowed any connectivity. ... This authentication can use X.509 certificates, computer account credentials from AD, or whatever else you'd normally configure radius to authenticate with. ...
    (Focus-Microsoft)
  • EAPOL, VLANs and network drives
    ... I decided to separate my network on some VLANs. ... I use EAPOL with RADIUS for that. ... as VLAN X untagged member. ...
    (Security-Basics)
  • Re: Prblm: Radius, WLAN, roaming profiles and software install via group policies
    ... >> The thing is that since we use Radius to authenticate to the ... >> assigned file server. ... >> WLAN it seems like the network connection is prematurely terminated, ... > encrypt traffic between wireless client computers and wireless access ...
    (microsoft.public.internet.radius)
  • PEAP Authentication in IAS
    ... I'm using a Procurve 2650 as Radius Client, ... Authentication in the network configuration of Windows XP and CHAP ...
    (microsoft.public.windows.server.active_directory)
  • How to Change Win 2000 Cached Account Password?
    ... They only have domain accounts. ... First PC has direct network connection. ... and still can access network via VPN. ...
    (microsoft.public.win2000.security)