Skip to main content

What is a VPLS?

A VPLS (Virtual Private LAN Service) is a network protocol that allows users to connect many different ethernet-based local area networks together over long distances. VPLS uses MPLS data packets and the Internet in order to forward information from one or more computers in one network to one or more computers in another network and then expand that to include even further networks that are all connected via the VPLS. Businesses and government agencies that have branches in many different locations generally use VPLS systems. However VPLS systems can also be used for gaming and other purposes that require networks to send and receive data outside of each network’s physical operation range.

How VPLS Works
VPLS networks work in similar to both LAN and MPLS networks. In a VPLS system, data is arranged in packets and labeled according to what it is, where it came from, and where it is going. Each packet is then sent to the nearest computer within the network in alphabetical order. As each computer receives the data packets, it forwards them to the next computer in line until the data reaches the end of the network. While an MPLS network prevents the data from travelling any further, a VPLS network allows the last computer in the network to forward the data to the nearest network in the system. This expands the primary network’s physical operation range to both the primary and secondary networks’ physical operation range.


VPLS networks have many uses, but are generally connect a business or institution’s individual network together over long distances. This allows those institutions to efficiently archive and sort through all of the data being generated by their overall efforts, rather than being dependent on their individual branches to forward data to a central database and then requiring staff members to organize all of that data.


VPLS networks have several critical advantages over other types. They connect many different computers over a much further distance than local area networks, wide area networks, and wireless networks. VPLS networks emulate physical connections even though they are only connected via the Internet and can be scaled to work with any network size.

Popular posts from this blog


The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N