Strange WSAM happenings

[kenlars_]

I'm using WSAM in destination mode to grant access to a specific server. I think the configuration is correct - at least it works on my PC. I have a user who is trying to use this and I see the following symptoms -

• WSAM starts very slowly - maybe 30 seconds.
• User gets no access when attempting to access the server via browser.
• User gets no access when attempting to telnet to the server on port 443.
• WSAM times out when you attempt to ping the DNS name of the server.
• No debuglog.log file is found anywhere on the machine. There is no "Juniper Networks" directory under Documents and Settings\All Users.

Anyone got any ideas? BTW, I'm running 6.5r5.

Ken

[muttbarker_ · Accepted solution]

Probably a "duh" comment on my part, but it smells like the WSAM code is corrupt or did not completely download. Did you try yanking it out and having them start again to get the ActiveX download anew? Or maybe flip to JSAM for fun?

[ThomasE66_]

" I think the configuration is correct - at least it works on my PC."

Do you mean it works normally from your PC? Is this the only user affected?

EDIT: I would try Kevin's suggestion first.

[kenlars_]

Kevin -

Thanks - I thought I had had them delete and reload WSAM, but apparently I had not done so. It worked after I did that with them this morning.

Ken