Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
MOC2007 unable to log in to OCS2007 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi folks,

    I have installed OCS2007 into a test domain, and am unable to get MOC2007 to log into it.

     

    The relevant systems in my test (virtual server 2005) domain are:

     

    1)       Domain controller (ADS01)

    2)       OCS2007 SE server (LCS01)

    3)       2 desktops (XPPRO01, and XPPRO02)

     

    I have done the complete install, and have been successful all the way through the validation with only warnings regarding federation (this OCS deployment is not enabled for federation). I have installed MOC2007 on both desktops, and enabled them for automatic configuration (they are using the SRV record: _sipinternaltls._tcp.servername.net for this configuration). I have also tested this with manual configuration, and have the same result.

     

    I launch MOC2007, and it returns “Your account is not configured to use the communications service.”. I have checked the “Enable Live Communications for this user” in the user properties in DSA.msc, and the users I am testing with show up in the management console on LCS01 as enabled. Also, when I run the validation from LCS01 (in the setup tool) it shows IM communication is successful using those two users.

     

    I am getting a “SIP/2.0 401 Unauthorized” (in the logfiles from communicator) despite all of the validation passing. This even happens with the MOC2007 installed on the server itself. I’m stumped.

     

    I’ve run the Best Practices Analyzer from the XPPRO01 workstation, and it found no issues whatsoever. I ran the checkspn.vbs script from the resource kit, and it was successful. I created the extra DNS records for _sip._tcp.servername.net and _sipinternal._tcp.servername.net (I did this based on errors that showed up in the MOC2007 log files, it looked for these SRV records, so I pointed them at the LCS01 server). The errors associated to those SRV lookups went away, but no change in the behavior.

     

    Here is a sample of the log output from MOC2007:

    09/25/2007|17:33:40.891 898Big Smile18 INFO  :: End of Sending Packet - 192.168.100.5:5061 (From Local Address: 192.168.100.20:1932) 705 bytes

    09/25/2007|17:33:40.891 898Big Smile18 TRACE :: - encrypted buffer length: 726 bytes.  First 8 bytes:

    09/25/2007|17:33:40.891 898Big Smile18 TRACE ::        17 03 01 02 D1 23 FD F7  :....Ñ#ý÷

    09/25/2007|17:33:40.891 898Big Smile18 TRACE :: ASYNC_SOCKET:Tongue TiedendOrQueueIfSendIsBlocking sending SendBuffer 01BBE738, this 01A51D28

    09/25/2007|17:33:40.891 898Big Smile18 TRACE :: ASYNC_SOCKET:Tongue TiedendHelperFn sendBuffer 01BBE738 sent, this 01A51D28

    09/25/2007|17:33:40.891 898Big Smile18 TRACE :: SECURE_SOCKET: decrypting buffer size: 487 (first 8):

    09/25/2007|17:33:40.891 898Big Smile18 TRACE ::        17 03 01 01 E2 A0 58 D3  :....â XÓ

    09/25/2007|17:33:40.891 898Big Smile18 INFO  :: Data Received - 192.168.100.5:5061 (To Local Address: 192.168.100.20:1932) 466 bytes:

    09/25/2007|17:33:40.891 898Big Smile18 INFO  :: SIP/2.0 401 Unauthorized

     

    Date: Tue, 25 Sep 2007 23:33:40 GMT

    WWW-Authenticate: Kerberos realm="SIP Communications Service", targetname="sip/LCS01.servername.net", version=3

    From: <sip:username@servername.net>;tag=7b31f9a76a;epid=b2028e0065

    To: <sip:username@servername.net>;tag=0C7A6B1C06C2D7594AE9101D8F20142C

    Call-ID: 5d4046440b184e419d7cc73371d96a97

    CSeq: 1 REGISTER

    Via: SIP/2.0/TLS 192.168.100.20:1932;ms-received-port=1932;ms-received-cid=F00

    Content-Length: 0

     

    Tuesday, September 25, 2007 11:45 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi folks, I have resolved this issue.

     

    After a couple of days of banging my head on the wall, I remembered that this test environment had been prepped for LCS2005. I took a look in Add/Remove programs on ADS01, and the LCS2005 admin tools were still installed. I uninstalled them, then installed the OCS2007 admin tools. After this was complete, I disabled Office Communications for the two users I was testing with, applied it, then re-enabled them. I then switched to XPPRO01, and attempted logging in...Voila! Success!

     

    Hope this helps someone else,

     

    John

     

    Thursday, September 27, 2007 8:21 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi folks, I have resolved this issue.

     

    After a couple of days of banging my head on the wall, I remembered that this test environment had been prepped for LCS2005. I took a look in Add/Remove programs on ADS01, and the LCS2005 admin tools were still installed. I uninstalled them, then installed the OCS2007 admin tools. After this was complete, I disabled Office Communications for the two users I was testing with, applied it, then re-enabled them. I then switched to XPPRO01, and attempted logging in...Voila! Success!

     

    Hope this helps someone else,

     

    John

     

    Thursday, September 27, 2007 8:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks heaps John.

    Same issue, same solution!

    Cheers.

    Friday, October 19, 2007 6:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    your solution is not exeactly useful. Yes it solves the problem but the user looses his/her contact list and any configuration made to his profile. The exact solution is that you have to check the enhanced enablement checkbox which is at the bottom of the advanced settings page of user Communications properties.

     

    Regards

     

    Ozan

    Friday, February 1, 2008 5:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Ozan,

     

    Thanks for the feedback. This was a test environment, and due to the installation of the LCS2005 admin console, you couldn't make any changes take effect on a user account (no configuration was possible due to conflicting admin tools). It was only intended for someone that may have been testing with LCS or had the LCS tools installed previously. Like I said in my scenario description, this was a test domain not a previous installation or live domain, so making these changes didn't affect active users. I apologize if you used this on a live server with active users.

     

    In my case I had not installed the OCS admin tools on the domain controller (ADS01) and I did have LCS2005 Admin tools installed there. The "Enable Enhanced Presence" was checked on the users in the admin console on the OCS2007SE server (it was defaulted to this). Despite that, until I did the procedure I posted, the test accounts were unusable for OCS.

     

    that aside...

     

    Did your experience also include the uninstallation of LCS tools and install or reinstall of OCS tools? Was your experience on an upgrade of LCS2005?

     

    Post some more details on your scenario so other users can base their solutions off the feedback of both of us. =)

     

    Thanks again,

     

    John

     

     

    Friday, February 1, 2008 11:13 PM