NORTEL VPN Client problem
Hello!I'm having a problem with NORTEL VPN ClientEverytime i try to connect: "EACFILT DRIVER MUST BE BOUND TO ACTIVE INTERFACE: Broadcoam NetXtreme Gigabit" Anyone have the same problem?Regards,
April 13th, 2007 1:53pm
I guess Notel have difference VPN client, please make sure you are using the one which support Vista.
April 14th, 2007 10:48am
It's the version for windows vista....
April 14th, 2007 10:49pm
Hi, is that a beta version? http://993399.com/resources/nortel_contivity_vpn_client_for_vista Seem Nortel not yet have a release version.... Did you check their forum for any compatibility issue?
April 15th, 2007 6:42pm
I think my Windows Vista isn't Beta version... I think my Windows Vista it's the final release...Probabply it's a problem with EACFILT protocol working on Windows vista... maybe i can download it somewere...
April 16th, 2007 4:58pm
HI, I am not saying your Vista is beta. I said your Nortel client may be still in beta stage. Try to geta latest version of it from Nortel. thx.
April 16th, 2007 6:58pm
I has made the last version of nortel to windows vista here: http://993399.com/resources/nortel_contivity_vpn_client_for_vista What do you think?... Cud be the version of my Windows Vista?
April 17th, 2007 11:18pm
I don't think so. Please reference here for 3rd party client support schdule of Vista: http://support.microsoft.com/kb/929490 I would suggest you to contact Nortel support to get a VPN client from them.
April 20th, 2007 10:05am
I have the same probelm except I am using XP not vista. I work for Nortel and cannot get any help with our IS people because they don't support windows yet only Blackberry applications for VPN.
May 9th, 2007 6:23am
ha? Nortel don't support Windows Client? Oh...
May 9th, 2007 8:16pm
I have XP and am getting the same message after successfully installing Nortel VPN Contivity Client 7_01.031. I don't work for Nortel. Any thoughts? Thanks in advance.
May 16th, 2007 3:20pm
I have the same problem. My Nortel VPN client was working fine before I installed web cam driver for A4Tech 35N to my XP Client. After installation of AS4Texh driver it fails to connect via Contivity.
May 28th, 2007 2:36am
Unal YILDIRIM wrote: I have the same problem. My Nortel VPN client was working fine before I installed web cam driver for A4Tech 35N to my XP Client. After installation of AS4Texh driver it fails to connect via Contivity. If you remove the driver/system restore, did the problem solve?
June 3rd, 2007 9:25pm
I'm ALSO having the same problem. The irony is that I actually had everything working on my older work laptop, was assigned a new work laptop, and now I can't recall how I actually resolved the problem on the old laptop (it was almost 2 years ago and probably an older release of the Contivity VPN client). I'm using WinXP Pro SP2 and Nortel Contivity v6.01.014. I've tried uninstalling the Nortel client and reinstalling it while my Windows Mobile device (a Dell Axim 51v) is docked, still no ceegar. If I (a) dock the Axim while the Nortel Contivity VPN client is loaded, the session is immediately terminated with the message Connection Terminated. Eacfilt driver must be enabled on interface(s): Windows Mobile-based Device #2. If I (b) try to load the Nortel client while the Axim is docked, I get the same message, and the client never loads. Any suggestions?
July 16th, 2007 6:47pm
There is a problem with that link. The instruction says to set the installation file eac607d.exe to XP compatibility mode. If you do that and run it, it will complain saying this version is meant for Vista only and will not let you continue. You have no choice but to take out the XP comp mode. If you do that, then it will install okay but running it brings back the error "Eacfilt must be enabled on the active interface...."
July 27th, 2007 1:56am
Tiago Roxo wrote: I has made the last version of nortel to windows vista here: http://993399.com/resources/nortel_contivity_vpn_client_for_vista What do you think?... Cud be the version of my Windows Vista? I was actually referring to this link. This vesion of Nortel VPN is made for Vista already so setting the installation file to XP comp mode will prevent you from installing it in your vista as it will complain this is meant for Vista only. If you dont set the XP comp mode, it will install but still when you run it afterwards, it sill give the error about EACFILT
July 27th, 2007 2:11am
I was able to fix this problem easily on Vista by going into Network Connections, selecting Properties on the Local Area Connection, UNchecking the Eacfilt Driver, selecting OK...then going back after a moment (otherwise, there is an error about it already being open)...REchecking the Eacfilt Driver and selecting OK. Again, it takes a moment or two to finish Identifying, then it's good to go. Hope this helps. OH, and for the record, IPSec Policy Agent service was Disabled on the client too -- so that has nothing to do with it.
November 21st, 2007 8:04pm
I had asimilar problem with a HP iPAQ 111 running Windows Mobile 6.0. I am using Contivity VPN Client version 6_01.014. The error message I received was: "EACFILT DRIVER MUST BE ENABLED ON THE INTERFACE(S): WINDOWS MOBILE-BASED DEVICE" I was able to resolve the issue by performingthe following: 1. On the device, go to Settings, Connections, and look for "USB to PC" option. 2. Go into the USB to PC option 3. Uncheck the Enable advanced network functionality checkbox and then, OK. 4. Warm boot the device (hit the reset button). 5. Power the device back on. 6. Once the device is booted up, dock and try again.
March 13th, 2008 11:16pm
Melric, Thanks for your solution. Unchecking and rechecking worked for me as well.
April 23rd, 2008 11:23am
RE: CH@BC's Enable advanced network functionality solution:Thanks for that - that allows the PPC to remain connected whilst using the Nortel VPN. I noticed that in Device Manager, when viewing hidden devices (View -> Show Hidden Devices), most Network adapters have a corresponding Eacfilt Miniport driver installed by the Nortel VPN client, however the "Windows Mobile-based Device #15", the adapter installed for my PPC, doesn't have one. I assume that this is the reason why, when viewing the Services installed for that network connection in [Desktop -> Control Panel -> Network Connections -> Windows Mobile Connection], then [right-click -> Properties -> "The connection uses the following items:"], the Eacfilt Driver doesn't appear, and can't be installed either, even when correctly pointing to the Eacfilt driver location in c:\Program Files\nortel Networks\FilterDrivers\.The only other adapter that I can't use when connected to the Nortel VPN is the Microsoft Loopback adapter, but I can live without that. I just go into Network Connections, select that connection, and right-click -> Disable. (Can be reenabled once again after disconnecting from the VPN)
July 21st, 2008 12:22am
I read all the threads here and it did not solve my issue. I found the below that did work. Problem: After installing a webcam on a Windows XP SP2 PC my Nortel VPN client could not connect and I received the error "Eacfilt Driver must be bound to active interfaces(s): Microsoft TV/Video Connection". http://www.geeklobby.com/index.php/2008/12/07/eacfilt-driver-must-be-bound-to-active-interfacess-microsoft-tvvideo-connection/#comments Eacfilt Driver must be bound to active interfaces(s): Microsoft TV/Video Connection Posted on December 7, 2008 with 1 Comment Recently I got this error on my computer when I started the Nortel VPN Client for my wife. After doing some research online, I found out that it was the Logitech Webcam software that messed up this. But, this issue can be resolved easily. But, it requires windows registry tweaking. It worked for me. It might work for you too. 1. Type regedit in Start->Run… window. 2. Select HKEY_LOCAL_MACHINE\SYSTEM 3. Search for Microsoft TV/Video Connection 4. When you see “Driver Desc = Microsoft TV/Video Connection” registry entry, look for a subfolder Linkage. 5. Select the “Linkage” on the left hand side and “Upper Bind” registry key. 6. Add “Eacfilt” to the values of this registry key. 7. Save the changes and reboot the system. It should work fine.
January 12th, 2011 12:11pm