Yea, it’s ugly as heck to manage
though. Mac reservations for all, but anyone can spoof that if they have a wit.
Your problem is a common one, but not a simple one. If you hear of a slicker solution then
that, pray tell! jlc From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edwin Our domain is using a Win2K3 server which is also a domain
controller as its DHCP solution. Often I look at the DHCP tables and
notice that there are unauthorized machines that connect to our network.
This seems to occur from employees who bring in their laptop during the weekend
when the workload is light and management does not have as much a presence. The workstations within the domain all follow a naming
scheme. For example, ORL-RM3-204-2 which means, the server is located in So if I see a workstation in the DHCP tables that does not
follow that naming scheme, then I know that something else has managed to get
an IP Address from the network. Is there a way to prevent unauthorized machines from
retrieving an IP address? If so, is there also a way to make an exception
to the rule should a non-standard naming convention machine require authorized
access to the network? Thank you all for your replies. Edwin |
- [ActiveDir] Unauthorized DHCP Requests Edwin
- RE: [ActiveDir] Unauthorized DHCP Requests Joe L. Casale
- RE: [ActiveDir] Unauthorized DHCP Requests Coleman, Hunter
- RE: [ActiveDir] Unauthorized DHCP Requests Ayers, Diane
- RE: [ActiveDir] Unauthorized DHCP Requests Coleman, Hunter
- RE: [ActiveDir] Unauthorized DHCP Requests Ken Cornetet
- RE: [ActiveDir] Unauthorized DHCP Requests Tyson Leslie