Hmmm... I tried the same exercise using my "Watchguard" client and firewall. Aothough, when I create my virtual adapter, the system assigns it a 02:xx:xx MAC address and when I connect to SEPM, I can see, even though connected through the VPN, the REAL MAC address of the network card, in this case wireless MAC address regitering in the system.
I think the limitation is in the software or virtual adapter, moreso than with Symantc itself.
- If Symantec is not installed, do you have a MAC address on the Virtual Adapter?
- Some VPN software, allows you to assign a MAC manually...
-> Device Manager -> Network Card -> Properties -> Advanced (tab) -> Network Address: Enter MAC address.
* * * * * * *
I suspect however, that because you are using DUN from Windows, you have fallen into a M$ blackhole. Dating back to nearly 10 years.
Others, have tried and successfully fixe this problem with the following commands, to wipe out the IP stack and fix the Socket in the System for the Virtual NIC to create itself properly...
**Windows XP**
netsh int ip reset reset.log
netsh winsock reset catalog
** Windows Vista and above ** (run as administrator)
netsh winsock reset catalog
netsh int ipv4 reset resret.log
netsh int ipv6 reset reset.log (If applicable)
Reboot system. All configured parameters of Static IP addresses on all Cards will be lost... SO take note, BEFORE performing.
There is always a chance that uninstalling and reinstalling the NIC drivers could help... But because it is Windows being Windows...
Also, very interesting is the fact that it works without Symantec installed... Does it have a MAC without Symantec??