04-24-2009 01:18 PM
Solved! Go to Solution.
09-30-2009 03:24 PM
10-01-2009 04:59 PM - edited 10-01-2009 05:00 PM
Win7 RTM was released back in August for Microsoft Volume Licensing/Software Assurance customers
I'm not impressed with Juniper that NetScreen Client works with Vista but _doesn't_ work in Windows 7.
I'm testing XP Mode to see if I can run Netscreen Client inside the virtual PC - so far can install it inside XP mode but it isn't appearing back in Windows 7.. There goes the connection to our shared drive for any laptop users...
One remaining option is ditch the NetScreen Client completely and use Direct Connect on 2008 R2 servers - a bit drastic, but if Juniper aren't going to help people I'm not left with many options at this stage..
10-02-2009 12:43 PM - edited 10-02-2009 03:18 PM
Any updates on this thread? We are looking to upgrade to Windows 7 but need our VPN functionality...
This thread should NOT be considered solved until there is a rough timeline around when NS remote will be Windows 7 capable.
10-04-2009 02:58 PM
I agree - this post should NOT be closed until a solution is available.
I've found out a bit more about running NetScreen Client 9 in XP Mode - will take much a large amount of work to test this:
someone has done this with another client - hoping this can be adapted for NetScreen Client in a similar manner - more details available from http://jmpstart.wordpress.com/2009/09/16/safenet_s
11-10-2009 07:35 AM
I think Juniper made it pretty clear in this KB article:
There are no plans to support NS-Remote on the following platforms; please consult NS-Remote Software Release Dates and Milestones for EOL information.
02-15-2010 08:02 PM - edited 02-15-2010 08:05 PM
Just wanted to drop a note here that someone has found a fix/workaround from the Microsoft Technet forums:
1. Stop the Volume Shadow Copy service (VSS) (which prompt an error message when I tried to install the client)
2. Install Juniper Client and ignore the error messages about the virtual adapter
3. Restart your PC
4. If Microsoft IKE and IPSec services are running, stop them
5. Import you Security Policy
6. Startup the Service SafeNet IKE Service
7. Connect to your network
This has worked for me but the only downside is that this doesn't resolve the issue with the safenet adapter not installing, so that means DNS will not function once connected to your VPN. You must access network resources using ip addresses. Also, you will need to start the Safenet IKE service after each reboot. I suggest that you should create a .bat file with the following cmd:
net start IreIKE
This is best for my needs since I only need my VPN access for remote desktop connections and not anything that relies on DNS. If you need DNS with your VPN activities I suggest installing a Win XP virtual machine to access your VPN.