<div>
What impact would this have on AD? This doesn't sound like a wise thing to do........I know creating a GPO is the way to go, but I can't do it at this time......
</div>


What impact would this have on AD? This doesn't sound like a wise thing to do........I know creating a GPO is the way to go, but I can't do it at this time......

<div>
Govnah<br />
If the server is your AD DC then this is a BAD THING. However if the server is just another member server, then hiding it from the browse list will not cause issues, unless it hosts services that the users have to get to.<br />
<br />
A GPO may well be &quot;a sledge hammer to crack a nut&quot; in this case.<br />
<br />
Cheers<br />
<br />
JamesDS
</div>


Govnah
If the server is your AD DC then this is a BAD THING. However if the server is just another member server, then hiding it from the browse list will not cause issues, unless it hosts services that the users have to get to.

A GPO may well be "a sledge hammer to crack a nut" in this case.

Cheers

JamesDS

<div>
Yes it is actually our payroll server not a DC......So if the users no the names and shares it shouldn't be a problem........
</div>


Yes it is actually our payroll server not a DC......So if the users no the names and shares it shouldn't be a problem........

<div>
Govnah<br />
Ok, so it sounds like you want to disable NetBIOS but LEAVE DNS. That way the users will be able to access the machine by name, if they know the name, but it will not appear in a browse list.<br />
<br />
Cheers<br />
<br />
JamesDS
</div>


Govnah
Ok, so it sounds like you want to disable NetBIOS but LEAVE DNS. That way the users will be able to access the machine by name, if they know the name, but it will not appear in a browse list.

Cheers

JamesDS

<div>
<div class="content wysiwyg-content">
Just curious if it was possible to prevent a Windows 2000 domain server from being advertised on the network. In other words I do no want users to be able to browse to the server via network neighborhood. I know I could create a GPO that would prevent users from browsing the network, but I can't do that because of other issues......<br />
<br />
<br />
TIA
</div>
</div>


Just curious if it was possible to prevent a Windows 2000 domain server from being advertised on the network. In other words I do no want users to be able to browse to the server via network neighborhood. I know I could create a GPO that would prevent users from browsing the network, but I can't do that because of other issues......


TIA

Prevent a Windows 2000 Server from being advertised on the network

Windows 2000 is an operating system for use on both client and server computers. It is the successor to Windows NT 4.0, and is the last version of Microsoft Windows to display the "Windows NT" designation. Four editions of Windows 2000 were released (Professional, Server, Advanced Server, and Datacenter Server) that shared a core set of features, including many system utilities such as the Microsoft Management Console. All versions of the operating system support NTFS 3.0, Encrypting File System, as well as basic and dynamic disk storage. The Windows 2000 Server family includes support for Active Directory services, Distributed File System and fault-redundant storage volumes.