We are using an SA4500 with release 7r1, and we are having inotes webaccess trouble.
We are unable to send email, attach files, use sametime, same a meeting via IVE.
When we connect to our inotes server directly everything works.
I have opened several tickets, but for the moment only for the attach file error support gave me the following soulution:
'This is not an IVE issue to an onotes issue, please conact IBM support" and they reffer to kb17687
I also tested inotes with release 6.5 but problems are the same.
I tried all the already posted inotes solutions, without any succes.
For me there is a general inotes client issue with the IVE, but support is only handeling my issues one by one.
We currently have a working e-gap whale solution, and we do not have any issues with it.
Does anyone have the same issues, or maybe a solution?
Make sure that for the Network Connect access control that you are allowing all the relevant IP addresses and Ports. Also, If you are using Split-tunneling that you add those addresses or networks to the split-tunnel network profile.
Just a bit of advice, never run the first release of any software, you don't want to be the one finding bugs.
Same problems for me with sa4000 7.0R2 and inotes 8.5.2.
With inotes 8.5.1 we can send a message without attachement but now even the send button don't work.
The only configuration working is ultra light mode of inotes with firefox 3.6 but in this case you cannot do an attachement.
I don't understand why Juniper ignore their customers who use inotes thru the ive and the only response is to say "This is not an IVE issue".
For iNotes 8.5.2, can you try adding a Custom Header policy to allow custom headers?
It looks like iNotes has introduced a HTTP header called X-IBM-NOTES-NONCE to combat some XSS vulnerabilities but this is not a standard HTTP header so the SA will block it by default.
Name: iNotes custom header policy
Resources: enter your iNotes URL e.g. https://inotes.company.acme:443/*
Roles: Select Roles that have iNotes access
Action: Allow Custom Headers
4. Click 'Save Changes'
Can you test and see if that resolves the issues in your case?
I have downgraded my IVE to 6.5r6
Now using inotes in lite mode with IE8 everything seems to work "normally".
Using Firefox 3.6.10 in lite mode send a meeting request does not work.
In full mode with the "instant messaging" option disabled IE8 also works "normally".
With Firefox 3.6.10 I am unable to send mail and meeting request also does not work.
We use iNotes 8.5.1 FP4 and i tried implementing the custom header with no succes.
A test to upgrade to 8.5.2 revealed the same error's plus also and our e-gap whale solutions has trouble with iNotes 8.5.2. We had to downgrade to notes 8.5.1 FP4 again.
I am having a feeling that this is a IBM iNotes issue, they seem to change inotes behavior with evry patch or upgrade.
We have opened a ticket with IBM support and they seem tobe working on a patch....
My Juniper tickets did not result into any working solution.
For how long have you been using IVE to access inotes? Did it work in the past?
custom headers don't work anyway.
I use ive for accessing inotes since 3 years now; with dwa7 it was working fine with ie, less with firefox.
If you keep your mailbox model dwa7 instead of mail85, it works fine even on 8.5.2 server.
Problems started with 8.5.0
I hope you'll get some result with IBM.
Let me know about that.
Thank you for the information within this thread. I am experiencing the same situation on my test email accounts since migrating them to the v8.5.2 mail template. Have you had any luck with IBM providing support for this issue? Thank you, again.
The only feeback I recieved is that both IBM and Juniper are "working" on a solution (since serveral months).
Both IBM and Juniper blame each other, but what I discovered from testing is that the problems started with Domino 8.5.1.
Domino 8.5 works like a charm....
So for the the problem is an IBM issue.
I need somebody from Juniper to provide assistance to work with Lotus iNotes DEV to resolve this issue for our mutual customers.
Please contact me at [email protected]