When installing Avaya IP Office Voicemail Pro 9.13.0, I came across this error, 1327 Invalid Drive:<driver letter of problem drive> and was unable to install voicemail pro.
Searching google suggested that a change is made to the registry to resolve this issue for office installs, and some suggested disconnecting the drive and disabling automatic reconnect.
There is, however, an easier solution:
Step 1: Create the local voicemail user
Step 2: Log in as that user,
Step 3: Run your installation application again. It should now complete without error. If you are asked to restart the machine, you must log in using the local account to continue installation.
Step 4: Once the install is completed, you can continue to use your domain credentials.
I hope this saves you some time.
This problem is not really Avaya related, but an issue with Microsoft Windows, so this procedure may or may not work for you if you are trying to install some other application, but it’s worth a shot. Let me know if it worked for you…
Not much happening today… here’s a detailed diagram of how a firewall filters traffic…
I promise I will / will not do this more often…
OK, lets start this off with a fairly uncommon problem that allows a VPN to connect but does not pass any traffic. The VPN profile and account are tested on another machine and found to be working, so the problem is (gasp!)… the client machine!
You can verify this problem by noticing an ‘error with call to iphlpapi.dll’ in the cisco client logs (you may need to enable them on the logs tab of the client).
The rather irritating resolution to this is:
1. Remove Cisco VPN Client
3. Download ftp://files.citrix.com/winfix.exe and run it
4. Reboot again!
5. download ftp://files.citrix.com/dneupdate.msi for 32-bit or ftp://files.citrix.com/dneupdate64.msi and run the relevant file..
7. Reinstall the VPN Client.
9. The Cisco VPN client should now connect and allow traffic to pass.
This seems to be a problem with DNE, which appears to do some pretty important things with VPN traffic, more information on it is available here: https://www.citrix.com/go/lp/dne.html
I hope this saves you time, and stress, in the future.
I have seen this resolve problems in similar circumstances with WatchGaurd as well as Cisco ASA’s (5505 or 5510) VPNs aswell, only they actually don’t seem to connect at all, I haven’t seen the error message but if I find it I’ll put it here. Thanks to “The other Martin” for the tip.
Welcome to WeAreNothing.com, the new home of this blog. I don’t know why I just said new home, because it’s not.. it never existed before so I can hardly call it the new home, so maybe, the first home of my WeAreNothing blog.
Firstly, thanks for visiting, I intend to update this blog regularly (how many times have you heard that before?) so that I can share my personal view on the convergence industry, and by that I mean pretty much anything IT related.
For those of you that have never met me, I am a voice and data engineer from Northern England, I install and maintain Mitel and Avaya phone systems and the systems required for their operation. This means I am frequently required to work with other tech, such as Cisco remote access and site to site VPNs, and VMware. Whilst not my primary focus, it does still interest me, so from time to time you may see me post about these things. I will probably also post about common problems I have seen, these may sometimes seem a little off topic, but this is industry we are in, nobody will have the same problems all the time, and sometimes you will be asked to investigate a problems slightly outside your comfort zone. I hope you may find the answer to some problem you may have on this site at some point.