Communicator on Windows 7 not working outside the main site

Toutes les réponses

• jeudi 4 mars 2010 14:47

  Modérateur

   

   
  

  0
  Can you enable loggign on the OC clients and report back with whatever errors are appearing in the workstation's event log?
  
  http://communicationsserverteam.com/archive/2009/04/01/394.aspx

  ---

  Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
  • Réponse
  • Citation

   
• jeudi 4 mars 2010 23:24

   

   
  

  0

  Jeff,

  I had a look in the event log and there several errors related to account in the security logs. Please see below.

  Log Name:      Security
  Source:        Microsoft-Windows-Security-Auditing
  Date:          05/03/2010 9:16:45 AM
  Event ID:      4648
  Task Category: Logon
  Level:         Information
  Keywords:      Audit Success
  User:          N/A
  Computer:      win7.domain.local
  Description:
  A logon was attempted using explicit credentials.

  Subject:
   Security ID:  domain\user01
   Account Name:  user01
   Account Domain:  domain
   Logon ID:  0x3c2e3b
   Logon GUID:  {9f135fb6-7bc5-3a58-b0c5-9ea5719981d5}

  Account Whose Credentials Were Used:
   Account Name:  user01
   Account Domain:  domain.local
   Logon GUID:  {0350fb77-21a5-761a-6a11-f02498881a98}

  Target Server:
   Target Server Name: ocsfe01.domain.local
   Additional Information: sip/ocsfe01.domain.local

  Process Information:
   Process ID:  0x1110
   Process Name:  C:\Program Files (x86)\Microsoft Office Communicator\communicator.exe

  Network Information:
   Network Address: -
   Port:   -

  This event is generated when a process attempts to log on an account by explicitly specifying that account’s credentials.  This most commonly occurs in batch-type configurations such as scheduled tasks, or when using the RUNAS command.
  Event Xml:
  <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
      <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
      <EventID>4648</EventID>
      <Version>0</Version>
      <Level>0</Level>
      <Task>12544</Task>
      <Opcode>0</Opcode>
      <Keywords>0x8020000000000000</Keywords>
      <TimeCreated SystemTime="2010-03-04T23:16:45.235257700Z" />
      <EventRecordID>339541</EventRecordID>
      <Correlation />
      <Execution ProcessID="548" ThreadID="3264" />
      <Channel>Security</Channel>
      <Computer>win7.domain.local</Computer>
      <Security />
    </System>
    <EventData>
      <Data Name="SubjectUserSid">S-1-5-21-854245398-1500820517-839522115-26735</Data>
      <Data Name="SubjectUserName">user01</Data>
      <Data Name="SubjectDomainName">domain</Data>
      <Data Name="SubjectLogonId">0x3c2e3b</Data>
      <Data Name="LogonGuid">{9F135FB6-7BC5-3A58-B0C5-9EA5719981D5}</Data>
      <Data Name="TargetUserName">user01</Data>
      <Data Name="TargetDomainName">domain.local</Data>
      <Data Name="TargetLogonGuid">{0350FB77-21A5-761A-6A11-F02498881A98}</Data>
      <Data Name="TargetServerName">ocsfe01.domain.local</Data>
      <Data Name="TargetInfo">sip/ocsfe01.domain.local</Data>
      <Data Name="ProcessId">0x1110</Data>
      <Data Name="ProcessName">C:\Program Files (x86)\Microsoft Office Communicator\communicator.exe</Data>
      <Data Name="IpAddress">-</Data>
      <Data Name="IpPort">-</Data>
    </EventData>
  </Event>

   

  • Réponse
  • Citation

   
• vendredi 5 mars 2010 14:36

   

   
  

  0
  Have you edit the sensitive info on that log?
  
  If not...
  
  Does the site you're in has LAN access to main site?
  
  Because your MOC is trying to connect to:
  
   Target Server Name: ocsfe01.domain.local
  
  Is this server available on the remote site? If it's available is there any firewall between sites? Is the firewall configured to let OCS ports go through?
  
  Hope it helps
  
  Regards,
  
  Hugo Picão
  • Réponse
  • Citation

   
• lundi 8 mars 2010 09:32

  Modérateur

   

   
  

  0
  HI Michael,
  Any update for your issue?
  
  Regards!
  gavin
  • Réponse
  • Citation

   
• mardi 9 mars 2010 16:38

   

   
  

  0

  HI Michael,
  Any update for your issue?
  
  Regards!
  gavin

  
  Hi Gavin,
  
  I found a work around for the issue. It's a Windows 2008 issue more than Windows 7. This also applies to SharePoint related issue also. The kbs fix the problem.
  
  http://support.microsoft.com/kb/926642
  
  Ignore the fact that it's applies to Windows 2003 but it does work with Windows 2008. Doesn't need to reboot or restart IIS at all. Just need to give it about 10 mins or so.
  
  Thanks all for helping out.
  
  

  • Marqué comme réponse Gavin-ZhangModerator vendredi 12 mars 2010 09:24
  •  
  • Réponse
  • Citation

   
• vendredi 12 mars 2010 09:23

  Modérateur

   

   
  

  0
  Hi Michael,
  Thanks very much for your share.
  
  Best regards!
  gavin
  • Réponse
  • Citation