Under "some problems" I mean that the neighborhood is un-browsable if
NetBEUI is the only protocol used for workgrouping in windows.
It takes to specify the exact share's name, like "\\server\printer", to
find it. No discovery work at all.
That's not a tap-win32 bug; it's normal behavior with a routed VPN
unless you enable unicast-based discovery with WINS. This is discussed
in the HOWTO and the mailing list archives.
Openvpn-devel mailing list