Note: Bridging will only work
with the Windows XP and the Windows
Server 2003 family of operating systems. Also, be advised that for Windows Server 2003 R2, you may need to force the TAP NIC into compatibility mode per this article. (Thanks, Luther!)
From the Control Panel, go to Network Connections. To keep things
organized, rename "Local Area Connection n" (TAP-Win32 Adapter V8) to
Select both OpenVPN and your normal physical adapter (typically
named "Local Area Connection"), right-click, and select "Bridge
It normally takes 15-45 seconds for the process to complete.
Rename "Network Bridge (Network Bridge) n" to "OpenVPN Bridge".
Once the Bridge has been established, it is important to realize that
all TCP/IP settings are now controlled through OpenVPN Bridge adapter
(as opposed to Local Area Connection adapter). Check to make sure
that all of your settings are correct. If you originally had a
static IP Address, etc., these settings will probably need to be
duplicated into the OpenVPN Bridge adapter. Right-click "OpenVPN
Bridge" and select "Properties":
...then go into the Internet Protocol (TCP/IP) Properties:
These are the defaut settings of a newly created OpenVPN Bridge
adapter. If your "Local Area Connection" settings are identical,
you're good to go -- otherwise you must make the applicable
changes here or your net will not work!
As soon as you can access the
Internet, et al again, it's time to start building your config
Since there are so many guides/HOWTO's available, I won't get too deep
into it here. For your convenience, here are mine:
OpenVPN Server (Windows XP
Professional, Multiple Clients)
ifconfig 192.168.0.1 255.255.255.0
ifconfig-pool 192.168.0.110 192.168.0.119
push "route 10.0.0.1 255.255.255.0 192.168.39.1"
duplicate-cn #use this for testing only
push "ping 10"
push "ping-restart 60"
(Windows XP Professional)