VMware Workstation Bridged Networking failures post install of Citrix Access Gateway

I’ve been a long time user of VMware Workstation and it’s Bridged Networking features for guests.

It was my surprise that once I installed the latest Citrix Access Gateway (which we need installed to use work’s VPN) that the VMware Workstation Bridged Networking between my guest and my physical client stopped working.

Guest can get DHCP IP from my router on my network no problem and access the internet and other computers/resources. Except it cannot talk over the bridged network interface to the IP being used by the physical host. Nor can physical host talk to guest over the bridged network IP address.

This all use to work fine on previously releases of Citrix Access Gateway, but since going to version, this no longer works. I’ve reinstalled Windows twice and both times no change. Soon as the VPN software goes on the communication breaks. You can uninstall it and it comes good.

I’ve narrowed it down to the DNE Lightweight Filter that gets installed onto the primary network card.

Currently awaiting confirmation from Citrix as I asked my work to log a support call to them to confirm if this condition is known and/or possible to workaround at this time.

I tried with VMware Workstation 9 and 10. Same condition.


  • gmiller January 30, 2014 Reply

    I’m having the same trouble with the DNE Lightweight Filter. Were you able to get any help from Citrix and/or VMWare?

    • michaelf January 30, 2014 Reply Author

      I can’t raise a ticket with VMware as I don’t have up to date support, however I was trying to get my work helpdesk who provide Citrix VPN client to raise a ticket, however that still hasn’t happened due to missing details on whom to raise it with.

      If you have a channel to raise it, please do so, and let us know details so I can let my work know so if they raise it too, we can reference it.

      I will chase up my end now, as I haven’t heard anything in a while.

      I bet your annoyed with it like me. It broke a very large lab I used too where I make use of bridged interfaces to create 2 seperate networks and use routing between them

  • michaelf April 29, 2014 Reply Author

    Unfortunately this issue is not resolved post an upgrade to Client version, will test it out on a machine that gets a fresh Windows install in a few weeks. But this client revision don’t resolve it. So the upgrade my employer has done on the Appliance that forces the client version above to be installed just doesn’t address the introduced fault (yet).

  • michaelf January 3, 2015 Reply Author

    I recently built a Windows 8.1 Pro system and using the same version of the VPN client above on that system, the same problem still exists. Very disappointing.

    • gmiller January 4, 2015 Reply

      I have not been able to find a solution either. Thankfully, for now, I don’t need the VPN very often, so I end up disabling the DNE Lightweight Filter except when the VPN is required.

      • michaelf January 5, 2015 Reply Author

        I am using VPN on a different machine. This use to all work, and that’s what annoys me. I think it might of been an update from Microsoft that impacted it around the same time the VPN software changed.

        Not about to narrow it down further, just work around it. Unfortunately.

Leave a Reply

Your email address will not be published. Required fields are marked *