Wednesday, February 11, 2009 9:47 AM
I'm having a strange problem with some of my OCS users while they trying to connect from remote.
I have OCS 2007 Standard server, and an EDGE server in the DMZ.
I've configured the EDGE to be working with the domain (domain list), and configured the users to have remote access enable on the OCS server.
Couple of users complained that they cannot access from remote, and when they are typing their password they are getting the following error:
Microsoft Office Communicator 2007
Cannot sign in to Communicator. You may have entered your sign-in address, user name, or password incorrectly, or the authentication service may be incompatible with this version of the program. If your sign-in information is correct and the problem persists, please contact your system administrator.
from internal network, everything is working fine without any problem.
I've checked and did the following:
1) The authentication type is both for NTLM and Kerberos.
2) I do have some users that can still access from remote without any problem, and also if I'm creating a new user and configure it to remote access I can access.
3) I've tried to disable remote access and then enable it back but it didn't helped.
4) I don't see any error message in the event viewer on the OCS Server, EDGE or Client machines although event logging on communicator is working.
5) I've checked to see if there any FW issues, but apparently not, because from the same computer I can access with one user, but cannot access with another.
6) I have the latest's hotfixes and patches both to the Communicator client and the OCS server.
7) I do have a problem to trying and debug it, because I cannot enter to the Office Communicator to open a new log sessions through the OCS server, and Network monitor cannot help as well because it's an SSL tunnel.
Any ideas how to solve/debug it?
Any help will be appreciated.
Thursday, February 12, 2009 5:05 AMMake sure your users are entering their login name as (domain\user) and the sign-in name is their email address (SIP address).
Thursday, February 12, 2009 10:25 AMI've make sure of it.
for the same user, while connecting the laptop to the local network is working. while working from wireless it doesnt.
Friday, November 13, 2009 2:46 PM
I also have the same problem.
But my scanario is:
I have Common windows login account for few users,but ther mail id and sips are seperate.
Now when i am trying to login with the any of the account i am facing the above error.
Thursday, November 19, 2009 10:58 AM
Did you do anyting with Client Version Filtering because I've seen this error as well when we applied client filtering.
Remove/Change the client filter to see if I'm right.
Microsoft minded UC specialist - http://www.reijling.nl