- Pulse Secure Community
- :
- About kwabbernoot_
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
since
10-29-2017
10-29-2017
kwabbernoot_
Occasional Contributor
5
Posts
0
Kudos
1
Solution
05-22-2014
08:23:AM
Hi, Some additional info on the issue: At our site we have 2 SSL-VPN devices, both running IVE 7.4R9.2. On our SA6500 device we have VPN connectivity issues with JunOS Pulse v5.0.4.46105 for IOS. Pulse verison 5.0.3 does not have issues. On our MAG6610 using an SM-160 module we do not have any VPN connectivity issues using the JunOS Pulse v5.0.4.46105 IOS client, also Pulse v5.0.3 works without issues. When I compare both realms and role configs they are identical. Both devices have connection pools that use "SSL" as transport. When I modify the pool configuration on the SA6500 device to "ESP" VPN connectivity is working again. Seems strange to me that the SSL transport works on a MAG device when it fails on a SA device. With kind regards, Van Dorpe Sven
... View more
04-26-2013
09:37:AM
Hi, I have the same issue on 2 Intel Atom based windows 8 Devices. The WSAM dEbug Log makes the following Log: 00189,09 2013/04/26 17:29:59.013 1 User1 dsSamProxy.exe Proxy p1152 t16F4 samproxy.cpp:368 - 'dsSamProxy:Run' CreateFile failed, could not get a handle to device: \\.\NEOFLTR_730_23977, error: 2 It seems that the system fails to laod the TDI driver and therfor can not connect /receive the configuration form the server. With kind regards, Kwabbernoot-be
... View more
11-27-2008
04:34:AM
ck, Activate Juniper DNS and check the WSAM Event Log for "host not found" entries whene using IScala. Try to modify the IScala config to full qualified domain names if the entries that are not found do not have a domain name. eg. Hostname = iscala01, FQDN Hostname= iscala01.domain.net You'll have to make certain that the domain name is resolved by the local DNS server of the local network. The fact that Lotus Notes and citrix no longer work with "Juniper DNS deactivated" is due to the fact the DNS server used by the juniper appliance is resolving those names. With kind regards, kwabbernoot Message Edited by kwabbernoot on 11-27-2008 04:59 AM
... View more
11-26-2008
06:27:AM
Hi ck, Try your application when WSAM is active. Run the application with the "Juniper DNS" option activated. Run the application with the "Juniper DNS" option de-activated. You active/de-activate the "Juniper DNS" option in the "Winsock" tab of the WSAM Application. You can do this within the same WSAM session. Review your DNS resolution if de-activating the option helps. WSAM depends completely on DNS resolution, if your application uses WINs try to use fully qualified DNS names. I already had similar issues with application using WINS basedhost names. Regards, Kwabbernoot Message Edited by kwabbernoot on 11-26-2008 06:28 AM
... View more
11-26-2008
06:20:AM
Hi, We have already seen similar messages inthe Event log of our active/passive SA4000 cluster. It is even worse, the passive does not take over VPN traffic unless we manually kick the primary node of the network. After creating a ticket with Juniper and some analyses of our own we discoverd that in most of the cases the issue was caused by the fact that: - the debug log was active (or) - a policy trace was still running This could also be caused by other troubelshooting processes, our SA4000 system has +-700 concurrent users on peak hours. Regards, Kwabbernoot
... View more
Latest Tags
No tags yet
© 2017 Pulse Secure, LLC. Use of this website assumes acceptance of our Legal Notices and Privacy Policy.
Pulse Secure has updated its Privacy Policy effective June 28, 2017.
