Re: DHCP Question
- From: Leythos <spam999free@xxxxxxxxxx>
- Date: Fri, 2 Oct 2009 19:56:48 -0400
In article <eWtSfj4QKHA.4568@xxxxxxxxxxxxxxxxxxxx>, townsend@xxxxxxxx
says...
We frequently have outside companies come into our office and they need
Internet connectivity. While we always have a Comcast line availalbe, many
times these external users use our LAN line and get an IP from our DHCP
server, so they have access to our network. Is there someway we can
configure DHCP to only hand out addresses to those computers on our domain
(possibly using our FQDN with a wildcard as the client name --
*.mydomain.com) and prevent outside users from accessing our network?
Guests should be on a different Wireless access device, so they are not
on your network at all. Either put them in a DMZ area, since some
firewalls have more than one DMZ (and I'm not talking about the FAKE DMZ
you find in linksys/home NAT routers), setup rules for HTTP/HTTPS and
DNS, possibly SMTP and FTP and RD, and only give them the key to your
GUEST wireless network.
Never allow an unmanaged decice on your LOCAL network.
--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
spam999free@xxxxxxxxxx (remove 999 for proper email address)
.
- Follow-Ups:
- Re: DHCP Question
- From: AllenM
- Re: DHCP Question
- References:
- DHCP Question
- From: Kate Townsend
- DHCP Question
- Prev by Date: Re: Add Domain Admins to Local admin group
- Next by Date: Re: AC for servers
- Previous by thread: Re: DHCP Question
- Next by thread: Re: DHCP Question
- Index(es):
Relevant Pages
|