Note: In VIPM 2012 We made some changes to the underlying code that fixes a long standing connection issue reported by many users. If you are having network connection issues, It's highly recommended that you upgrade to VIPM 2012. Get it here.
Certain packages can only be accessible from the internet such as those on the NI LabVIEW Tools Network, or the VI Package Network. If VIPM cannot access these networked repositories to download the package, you may be presented with a dialog, such as:
There are several things you can try to resolve these network connection issues:
- Firewall: You may have a situation where your firewall settings are blocking VIPM's access to the internet. This could be on your local PC, or this can be a company firewall managed by your network administrator. Please change your settings to allow VIPM.
- Local PC: If you have a program like Symantec, Kaspersky, TrendMicro, Mcafee, AVG or something similar. Make sure to add an exception for VIPM. If this still doesn't work then turn off the firewall completely in Windows to see if this solves the problem. Look in: Control Panel>Windows Firewall.
- Corporate firewall. Ask your IT department. VIPM requires access to the following URLs. If your IT department is blocking access to these base URLs, then this may be the problem:
- *.dl.sourceforge.net (This is the origin of the OpenG packages)
- Proxy Server: Your corporate network may be configured where you are required to go through a proxy server. VIPM 2012 uses your Windows system settings by default, so configuration should not be necessary. However, you may have a special configuration that requires extra setup. If this is the case then, you need to configure VIPM to use that proxy server correctly. More information can be found here:
- Run VIPM As Administrator: Sometimes the Windows user account does not have the necessary privileges. You can try any of the following to run VIPM as an Administrator:
- Run VIPM as Administrator: Right click on VIPM and choose "Run As Administrator" option
- Change the user account your using to be an Administrator (you might need an admin or your IT department to do this) and then try running VIPM
- Log into Windows with an Administrator level account and then try running VIPM
There is also a long discussion thread here, which outlines some special network configurations which might help.
If you still cannot resolve your issue, please submit a support ticket by clicking here and attach detailed troubleshooting information. To attach this information, follow the procedure here.