Microsoft Protocols and Services

These services are only available on Microsoft operating systems. However, as they could cause problems for other Microsoft users, they are listed here to inform you of what you should and should not use.

Running Your Own Windows Domain

Due to a shortcoming in the Microsoft implementation of NetBIOS name lookups, running your own domain can cause additional network traffic for no real reason. When a user selects a domain to browse (i.e., "CAMPUS"), the client asks the local browse master for information on this new domain. If all domain controllers for the domain are unavailable, the client begins to send subnet broadcasts and malformed DNS requests looking for the domain controllers. After performing these lookups numerous times, it finally gives up and times out.

Because of the additional network load that can be created, the Network Group requires all Windows domains to be supported by at least two (2) domain controllers. This way, if one fails, another is there to back it up. These domain controllers must be available 24 hours a day. If one of the domain controllers is down for an extended period of time, we strongly suggest bringing another one up until the original is operational again.

As long as there are at least two domain controllers, a Windows domain should cause no additional traffic on our network.

Last Updated: 2/14/08