11-18-2008 02:19 AM
I've got an issue when users are connected to our SSL VPN SA4000. They login and WSAM starts automaticaly. I configured the WSAM for the connection to our mailservers so they can replicate there mailfiles. Now they have another application running on there LAN, called iScala. When not connected to the SSL VPN (and WSAM) performance is good. Once they connect and WSAM is started, performance is bad. I already excluded additional processes (SwfIII.exe and ScaPgm.exe) but still performance is bad. Does anyone knows what I can check more?
Solved! Go to Solution.
11-26-2008 06:27 AM - edited 11-26-2008 06:28 AM
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.
11-27-2008 02:14 AM
after de-activation the Juniper DNS, performance did improve on the iScala client that is running on the local LAN. But...
the remote application isn't connecting anymore (in our case we use the WSAM for a Lotus Notes connection and Citrix)
When de-activated, I tried with host entries on the Juniper and on the windows client, but this isn't helping. Maybe I should have a look at the firewall...
11-27-2008 04:34 AM - edited 11-27-2008 04:59 AM
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,
11-27-2008 07:41 AM
I asked my colleague in Dubai, because they have the problem, if he could change the client config. I'm waiting on his feedback.
At the time, he's using the 'Juniper DNS' de-activated and I also added an extra connection document in his notes client directly with the IP-address. This works great... but each time he starts his WSAM he has to de-activate Juniper DNS
So I hope he can configure his iScala client with the FQDN and that speeds up the performance. As it is already weekend in Dubai, I will not have any update until Monday. I'll keep you posted.
Already thanks for your help
12-05-2008 02:44 AM