04-16-2009 06:26 AM
I'm currently running Windows 7 on my Dell Latitude E6500 and using IE 8. IVE works like a champ on it... everything I've tried works fine. The only thing I have yet to try is Network Connect. Everything else works, web, SAM, file, telnet, terminal.... As a matter of fact, I have less problems on Windows 7 than I do with Vista (go figure.)
Whether its technically supported... I'm sure the answer is no (since the RC isn't even out yet.)
Production: Clustered A/P SA 6000 - 6.5R2
Development: SA 2000 - 6.5R2
05-12-2009 09:55 AM
MAG 4610 (7.4) Lab
12-17-2009 09:19 AM
Any update on this thread would be a big help.
I use to have Windows XP Pro. Needed more then 3.2GB RAM, purchased new system. Windows 7 x64. I can access our corp Juniper 6.0.0 based system for our lab, but the corporate VPN access requires hostcheck for the Antivirus and uses a 6.3.0 client. I am also using Avast 4.8 Home edition (works fine on my stil working XP Pro system with exact same AV and install processs)
I have a fellow employee who has Windows 7 32bit working and said he had issues where the Juniper created adapter was disabled, but that is not the case in my situation.
If it is a firewall, I tried by disabling it to test and it still failed.
I also launch the juniper client via direct client (C:\Program Files (x86)\Juniper Networks\Network Connect 6.3.0\dsNetworkConnect.exe)
Same Error: You are not allowed to sign in. Please contact your administrator
Our "administrator" will not support x64 or Windows 7 (only WIndows XP Pro 32bit... which means nothing with more then 3GB RAM .... )
How do I get better logging to see if / where the failure lies?
12-17-2009 01:57 PM
Windows 7 Enterprise is supported in Juniper SA 6.5R2 release. All other versions of Windows 7 are compatible platforms.
All browsers are 32-bit browsers unless otherwise specified.
Please see the following KB for more details:
The error message you are getting "You are not allowed to sign in. Please contact your administrator." seems like related to role mapping failure, which could happen due to Hostcheck policies failing.
Your administrator will be able to see in the user access logs which HostCheck Policy is failing. If he has enabled client side logging, debuglog.log file on your PC should give you details on which policies fail and if it is indeed related to HC failure.
12-22-2009 10:48 AM
Thanks for the reply.
Just a few small questions related to the new Winodws 7 x64 6.5R2 client:
1) Our Lab system uses an older version of the Juniper Appliance which distributes the 6.0.0 client while our office corporate systems use th 184.108.40.206 client. Will this one new client work with both (or neither) version?
2) As I can not use either of the 6.3 or 6.0 clients with any current Windows OS, will this have any license implications for us in allowing customer's to use the VPN service? I am sure we will very soon be having issues where our customers will have workstations using 64bit Windows 7 (most systems come with more then with 4GB RAM and Windows Vista or 7). Can we download and when we have a compatablity issue, send them the newer client so they can use our VPN system?
12-28-2009 05:43 AM
I "resolved" this in that the host checker utility was failing due to AntiVirus. Once I reinstalled Avast and did a "standard" installation (vs my very basic AV ONLY), it past host-check and launched.
I will update if I learn which "Avast Provider" the host check utility requires to pass.