You can enforce certificates using the certificate server, and then
permissioning netbio based on certificates.

The best way it to shut down their network if it doesn't have a valid
certificate:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/S
erverHelp/69d8484b-8e31-408c-a127-0042d47d4613.mspx

Personally if a user did that, I would just not give him admin
anymore. Another option is a "disconnected" VM for them to develop
in, they can have admin there.

You can easily scan the network, and any box which doesn't accept your
credentials is consitered "rogue".

On 6/9/05, Kevin Green <securityfocus (at) kevin.3drealms (dot) com [email concealed]> wrote:
> Hello focus-ms,
>
> Does anyone know how to prohibit computers from connecting to a Windows 2003 Server share unless the
> system they are connecting from is a member of the domain.
>
> I a few "power users" and developers who keep removing there systems from the domain, and just
> connecting to the server by browsing and using there domain credentials to login. There access is
> allowed and needed for them to do there work. If I don't allow them to connect unless there system is
> a part of the domain, that will solve the problem.
>
> Kevin
>
>
> ------------------------------------------------------------------------
---
> ------------------------------------------------------------------------
---
>
>

------------------------------------------------------------------------
---
------------------------------------------------------------------------
---

[ reply ]