During Installation of WAN emualtion on the remote machine,suddenly connnection to the remote gets disconnected.I found that remote machine got crashed due to Wan emulation driver.So is there any alternative method for installing the driver?
This issue may happen on virtual machines. On some cases NeoLoad is able to detect that it's a virtual machine and in that case it does not allow the installation of the WAN driver.
The fact that the machine crashed seems to indicate that you are on a virtual machine. Could you confirm?
We know that some Amazon machines could have such behavior. But it may depend on the OS.
The issue is not with the installation process but the fact that your machine can't have the driver. So even if you try different installation method it will probably lead to the same result.
Well it's not an answer but I have ran into similar situation where I have made fresh installation of Neoload 7.0 and it has not installed WAN emulation. Even If I tried manual install of the module from C:\Program Files\NeoLoad 7.0\tools\ipfw\win64_wlh it installed successfully but Neoload doesn't recognize it. I'm running it on Windows Server 2016 x64 OS. Strangely I have a similar VM running same OS and it's working there with a standard installation. How do I explain this?
Be careful on Windows 2016 there's no installation of the WAN driver since there's no such driver anymore. Ipfw is only used for older Windows versions and not for recent ones like 2016, 10 etc...
NeoLoad now uses windivert as WAN emulation tool that does not require any installation. If WAN status is not enabled then it might be a signature issue or you may have an anti-virus that is blocking the loading of that file or worst it has removed it. Please look at the <install_dir>\lib\x64\ folder if you do have a Windivert64.sys file.
If you do have that file then right mouse click on it to display the properties and check if the signature status is valid.
Hello Nouredine A.
I have recently installed Neoload 7.1 and WAN emulator is not installed by default..i followed the steps yo mentioned and verified that WinDivert64.sys file's digital signature is valid. Can you please let me know what are the next steps to install WAN emulator.
@Divya What is your Windows version?
Could you look at your Windows event for any information related to Windivert signature issue?
Thanks for the reply. I see below in the logs. My windows version is 10. How ever i see that WAN was successfully installed on Windows server 2019 VM.
The WinDivert1.4 service failed to start due to the following error:
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
My purpose is served since it's installed successfully on windows server 2019 VM but just want to know the root cause so in case we move to different environment it will be stable and installed successfully
@Divya it seems that it's a signature issue. On some Windows the signature does not seem to be accepted. It's not linked to the version since it may work fine on Windows 10 or others.
You can download the Windivert version from the link below as the signature is different.
https://reqrypt.org/download/WinDivert-1.4.3-A.zip
https://reqrypt.org/download/WinDivert-1.4.3-B.zip
Replace the Windivert64.sys file from the NeoLoad installation folder first by the A one and restart NeoLoad. If you still have the issue try with the B one. Of course make sure that the above pre-requisites are correct i.e agent.properties correctly setup and BFE service started.
thanks Nouredine A, let me give it a try and update you
Sorry to say but either didn't work..i haven't changed anything on agent.properties...do I have to change something? also BFE is running. thanks.
