Best practices for network interface naming conventions

There is nothing more frustrating than logging into a Windows Server and seeing interfaces named Local Area Connection, Local Area Connection 2, and Local Area Connection 3 and not knowing which is which. Since Windows 2000 Server, we’ve been able to give names to interfaces. This has enabled us to do a few things, including using an icon to identify the Active Directory domain connection (only Windows 2008) within Group Policy and using clear names for interfaces. The best way to name a network interface is to make something that is self-documenting, repeatable, and easy to understand.

image

Read the entire tip at TechRepublic.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: