Naming Network Connections

by Mitch Tulloch [Published on 12 April 2006 / Last Updated on 12 April 2006]

Take a moment to name your network connections appropriately and save yourself time when troubleshooting later on.

If you have a server with more than one network card in it, then it's a good idea to give descriptive names to your network connections instead of the default Local Area Connection, Local Area Connection 2, and so on that Windows creates for you. For example, if you have a server with one network interface on the internal (private) network side and the other interface connected to the Internet, you could rename the first connection Private Network and the second one Public Network. Taking simple steps like this can save you precious seconds when troubleshooting a networking problem on a critical server since its easy to forget in the heat of troubleshooting things which network interface Local Area Connection stands for, public or private.

The Author — Mitch Tulloch

Mitch Tulloch is a widely recognized expert on Windows administration, networking, and security. He has been repeatedly awarded Most Valuable Professional (MVP) status by Microsoft for his outstanding contributions in supporting users who deploy and use Microsoft platforms, products and solutions. Mitch has published over two hundred articles on different IT websites and magazines, and he has written or contributed to almost two dozen books and is lead author for the Windows 7 Resource Kit from Microsoft Press. For more information, see www.mtit.com .

Latest Contributions

Featured Links