Windows Server

Srinivas · Guest

We have two offices remotely. We have VPN connection between both the offices
using PIX Firewall. One office is running Win2k and other NT4.0. If I want to
enable instant messaging between both the offices how should I go with the
setup.

Do I need to install two Live Comm servers at both the ends and one Access
proxy ?

Thanks in advance for you suggestion.

Srinivas · Guest

Bob

Thanks for the reply. Both the networks are not in same forest. One with
win2k AD and other with NT4.0 .

"Bob Christian" wrote:

Bob Christian · Guest

If the users for the offices are in the same forest, you can just configure
the ports between the servers and configure certificates on the servers to
enable TLS/MTLS between the two servers. The upside is that you don't need
an Access Proxy.

Live Communications Server 2005 Document: Configuring Certificates
http://office.microsoft.com/search/redir.aspx?AssetID=DC011586001033&CTT=5&Origin=HA011526621033

--
Bob Christian II
MVP - LCS
http://bobchristian.blogspot.com - Blog

"Srinivas" <Srinivas@discussions.microsoft.com> wrote in message
news:1AA7A78D-B40F-484C-A34F-FC8C317854D8@microsoft.com...

Bob Christian · Guest

Live Communications Server will not work with NT4, so you would have to
create an account, for the users, in the Windows 2000 AD domain. Yes, an
Access Proxy would definitely make things easier for the remote clients.

Regards,

Bob

--
Bob Christian II
MVP - LCS
http://bobchristian.blogspot.com - Blog

"Srinivas" <Srinivas@discussions.microsoft.com> wrote in message
news:D3964DD7-F6A1-40E5-A4C0-8AFD1A70B9ED@microsoft.com...

Jeremy Buch · Guest

If both domains have the VPN WAN, then you won't need an AP. Just install
LCS in the Win2K domain and then make sure accounts exist for the NT4 domain
users so that they can login directly over the VPN. If you want the NT4
users to use the Internet link instead of the VPN WAN, then you could set up
an AP for the Win2K domain to connect it to the Internet and have the NT4
domain users leverage the Internet link (via the AP) to login.

If the VPN WAN is already in use for local traffic, though, it seems like a
lot less hassle to just use it and login directly to the home server -
several protocol efficiencies will also help when your clients are directly
connected to their home server.

--
Jeremy Buch (Microsoft)

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup.

"Bob Christian" <BobChristian@removethis.gmail.com> wrote in message
news:%2311wxpc2FHA.636@TK2MSFTNGP10.phx.gbl...

Srinivas · Guest

Thanks Buch

I have installed the Live communication server as mentioned by you. The
remote office is in the different subnet for our local office. When I try
connecting from remote office to LCS using widows messanger I get the error
SIP/2.0 401 unauthorized.

I checked all the posts in the news group related to this error and done
exactly the same but still I have the same problem.

I have traced the log using the SIPlogger and sending you the same report.
Can you help me in
identifying the problem using this log

$$$$START-MESSAGE$$$$
TraceSeqNum: 1 Incoming Message { Unknown => Unknown } Time:
2005/10/28-17:05:46.0944
REGISTER sip:mslc.com SIP/2.0
Via: SIP/2.0/TCP 172.16.3.48:9682
Max-Forwards: 70
From:
<sip:user3@mslc.com>;tag=062fbd3023ea4c66a3fab4d4c1adb9a6;epid=3b7eac36d5
To: <sip:user3@mslc.com>
Call-ID: 4957d9592b344dffa6b79f81fa340b96
CSeq: 1 REGISTER
Contact: <sip:172.16.3.48:9682;transport=tcp>;methods="INVITE, MESSAGE,
INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER,
BENOTIFY";proxy=replace
User-Agent: RTC/1.3.5470 (Messenger 5.1.0701)
Supported: com.microsoft.msrtc.presence, adhoclist
ms-keep-alive: UAC;hop-hop=yes
Event: registration
Allow-Events: presence
Content-Length: 0
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

$$$$START-MESSAGE$$$$
TraceSeqNum: 2 Outgoing Message { Local => Unknown } Time:
2005/10/28-17:05:46.0954
SIP/2.0 401 Unauthorized
Date: Fri, 28 Oct 2005 11:35:46 GMT
WWW-Authenticate: NTLM realm="SIP Communications Service",
targetname="virtu-test-w2k3.mslc.com"
Via: SIP/2.0/TCP 172.16.3.48:9682;ms-received-port=1110;ms-received-cid=800
From:
<sip:user3@mslc.com>;tag=062fbd3023ea4c66a3fab4d4c1adb9a6;epid=3b7eac36d5
To: <sip:user3@mslc.com>;tag=19A2133BC36D7F6BC75DED4CF28BEAA2
Call-ID: 4957d9592b344dffa6b79f81fa340b96
CSeq: 1 REGISTER
Content-Length: 0
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

$$$$START-MESSAGE$$$$
TraceSeqNum: 3 Incoming Message { Unknown => Unknown } Time:
2005/10/28-17:05:47.0335
REGISTER sip:mslc.com SIP/2.0
Via: SIP/2.0/TCP 172.16.3.48:9682
Max-Forwards: 70
From:
<sip:user3@mslc.com>;tag=062fbd3023ea4c66a3fab4d4c1adb9a6;epid=3b7eac36d5
To: <sip:user3@mslc.com>
Call-ID: 4957d9592b344dffa6b79f81fa340b96
CSeq: 2 REGISTER
Contact: <sip:172.16.3.48:9682;transport=tcp>;methods="INVITE, MESSAGE,
INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER,
BENOTIFY";proxy=replace
User-Agent: RTC/1.3.5470 (Messenger 5.1.0701)
Authorization: NTLM qop="auth", realm="SIP Communications Service",
targetname="virtu-test-w2k3.mslc.com", gssapi-data=""
Supported: com.microsoft.msrtc.presence, adhoclist
ms-keep-alive: UAC;hop-hop=yes
Event: registration
Allow-Events: presence
Content-Length: 0
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

$$$$START-MESSAGE$$$$
TraceSeqNum: 4 Outgoing Message { Local => Unknown } Time:
2005/10/28-17:05:47.0335
SIP/2.0 401 Unauthorized
Date: Fri, 28 Oct 2005 11:35:47 GMT
WWW-Authenticate: NTLM opaque="6D5509D7",
gssapi-data="TlRMTVNTUAACAAAAAAAAADgAAADzgpji5yQ1VNHar0MAAAAAAAAAAI4AjgA4AAAABQLODgAAAA8CAAgATQBTAEwAQwABAB4AVgBJAFIAVABVAC0AVABFAFMAVAAtAFcAMgBLADMABAAQAG0AcwBsAGMALgBjAG8AbQADADAAdgBpAHIAdAB1AC0AdABlAHMAdAAtAHcAMgBrADMALgBtAHMAbABjAC4AYwBvAG0ABQAQAG0AcwBsAGMALgBjAG8AbQAAAAAA",
targetname="virtu-test-w2k3.mslc.com", realm="SIP Communications Service"
Via: SIP/2.0/TCP 172.16.3.48:9682;ms-received-port=1110;ms-received-cid=800
From:
<sip:user3@mslc.com>;tag=062fbd3023ea4c66a3fab4d4c1adb9a6;epid=3b7eac36d5
To: <sip:user3@mslc.com>;tag=19A2133BC36D7F6BC75DED4CF28BEAA2
Call-ID: 4957d9592b344dffa6b79f81fa340b96
CSeq: 2 REGISTER
Content-Length: 0
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

$$$$START-MESSAGE$$$$
TraceSeqNum: 5 Incoming Message { Unknown => Unknown } Time:
2005/10/28-17:05:47.0735
REGISTER sip:mslc.com SIP/2.0
Via: SIP/2.0/TCP 172.16.3.48:9682
Max-Forwards: 70
From:
<sip:user3@mslc.com>;tag=062fbd3023ea4c66a3fab4d4c1adb9a6;epid=3b7eac36d5
To: <sip:user3@mslc.com>
Call-ID: 4957d9592b344dffa6b79f81fa340b96
CSeq: 3 REGISTER
Contact: <sip:172.16.3.48:9682;transport=tcp>;methods="INVITE, MESSAGE,
INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER,
BENOTIFY";proxy=replace
User-Agent: RTC/1.3.5470 (Messenger 5.1.0701)
Authorization: NTLM qop="auth", opaque="6D5509D7", realm="SIP Communications
Service", targetname="virtu-test-w2k3.mslc.com",
gssapi-data="TlRMTVNTUAADAAAAGAAYAJYAAAAYABgArgAAABoAGgBIAAAAGgAaAGIAAAAaABoAfAAAABAAEADGAAAAVYKQQgUAkwgAAAAPRABUAC0ATgBTAC0ATQBTAEcALQBTAFIAVgBBAGQAbQBpAG4AaQBzAHQAcgBhAHQAbwByAEQAVAAtAE4AUwAtAE0AUwBHAC0AUwBSAFYAYb7LOBsAIKx6wUidVRUyQ2X/RSnHP+ck2+wR1CDVWfzTlf56nD0v9a+YuLSMnSpVShH7mhzLD6Ph+buwuUUE+A=="
Supported: com.microsoft.msrtc.presence, adhoclist
ms-keep-alive: UAC;hop-hop=yes
Event: registration
Allow-Events: presence
Content-Length: 0
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

$$$$START-MESSAGE$$$$
TraceSeqNum: 6 Outgoing Message { Local => Unknown } Time:
2005/10/28-17:05:47.0815
SIP/2.0 401 Unauthorized
Date: Fri, 28 Oct 2005 11:35:47 GMT
WWW-Authenticate: NTLM realm="SIP Communications Service",
targetname="virtu-test-w2k3.mslc.com"
Via: SIP/2.0/TCP 172.16.3.48:9682;ms-received-port=1110;ms-received-cid=800
From:
<sip:user3@mslc.com>;tag=062fbd3023ea4c66a3fab4d4c1adb9a6;epid=3b7eac36d5
To: <sip:user3@mslc.com>;tag=19A2133BC36D7F6BC75DED4CF28BEAA2
Call-ID: 4957d9592b344dffa6b79f81fa340b96
CSeq: 3 REGISTER
Content-Length: 0
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

$$$$START-MESSAGE$$$$
TraceSeqNum: 7 Incoming Message { Unknown => Unknown } Time:
2005/10/28-17:05:48.0196
REGISTER sip:mslc.com SIP/2.0
Via: SIP/2.0/TCP 172.16.3.48:9682
Max-Forwards: 70
From:
<sip:user3@mslc.com>;tag=062fbd3023ea4c66a3fab4d4c1adb9a6;epid=3b7eac36d5
To: <sip:user3@mslc.com>
Call-ID: 4957d9592b344dffa6b79f81fa340b96
CSeq: 4 REGISTER
Contact: <sip:172.16.3.48:9682;transport=tcp>;methods="INVITE, MESSAGE,
INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER,
BENOTIFY";proxy=replace
User-Agent: RTC/1.3.5470 (Messenger 5.1.0701)
Authorization: NTLM qop="auth", realm="SIP Communications Service",
targetname="virtu-test-w2k3.mslc.com", gssapi-data=""
Supported: com.microsoft.msrtc.presence, adhoclist
ms-keep-alive: UAC;hop-hop=yes
Event: registration
Allow-Events: presence
Content-Length: 0
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

$$$$START-MESSAGE$$$$
TraceSeqNum: 8 Outgoing Message { Local => Unknown } Time:
2005/10/28-17:05:48.0196
SIP/2.0 401 Unauthorized
Date: Fri, 28 Oct 2005 11:35:48 GMT
WWW-Authenticate: NTLM opaque="DCBD965B",
gssapi-data="TlRMTVNTUAACAAAAAAAAADgAAADzgpji8SfFZd1M4scAAAAAAAAAAI4AjgA4AAAABQLODgAAAA8CAAgATQBTAEwAQwABAB4AVgBJAFIAVABVAC0AVABFAFMAVAAtAFcAMgBLADMABAAQAG0AcwBsAGMALgBjAG8AbQADADAAdgBpAHIAdAB1AC0AdABlAHMAdAAtAHcAMgBrADMALgBtAHMAbABjAC4AYwBvAG0ABQAQAG0AcwBsAGMALgBjAG8AbQAAAAAA",
targetname="virtu-test-w2k3.mslc.com", realm="SIP Communications Service"
Via: SIP/2.0/TCP 172.16.3.48:9682;ms-received-port=1110;ms-received-cid=800
From:
<sip:user3@mslc.com>;tag=062fbd3023ea4c66a3fab4d4c1adb9a6;epid=3b7eac36d5
To: <sip:user3@mslc.com>;tag=19A2133BC36D7F6BC75DED4CF28BEAA2
Call-ID: 4957d9592b344dffa6b79f81fa340b96
CSeq: 4 REGISTER
Content-Length: 0
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

$$$$START-MESSAGE$$$$
TraceSeqNum: 9 Incoming Message { Unknown => Unknown } Time:
2005/10/28-17:05:48.0616
REGISTER sip:mslc.com SIP/2.0
Via: SIP/2.0/TCP 172.16.3.48:9682
Max-Forwards: 70
From:
<sip:user3@mslc.com>;tag=062fbd3023ea4c66a3fab4d4c1adb9a6;epid=3b7eac36d5
To: <sip:user3@mslc.com>
Call-ID: 4957d9592b344dffa6b79f81fa340b96
CSeq: 5 REGISTER
Contact: <sip:172.16.3.48:9682;transport=tcp>;methods="INVITE, MESSAGE,
INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER,
BENOTIFY";proxy=replace
User-Agent: RTC/1.3.5470 (Messenger 5.1.0701)
Authorization: NTLM qop="auth", opaque="DCBD965B", realm="SIP Communications
Service", targetname="virtu-test-w2k3.mslc.com",
gssapi-data="TlRMTVNTUAADAAAAGAAYAJYAAAAYABgArgAAABoAGgBIAAAAGgAaAGIAAAAaABoAfAAAABAAEADGAAAAVYKQQgUAkwgAAAAPRABUAC0ATgBTAC0ATQBTAEcALQBTAFIAVgBBAGQAbQBpAG4AaQBzAHQAcgBhAHQAbwByAEQAVAAtAE4AUwAtAE0AUwBHAC0AUwBSAFYAFPpBNcF9AZI2jvKzzMToImhzcuzJJjK0KMli3fD+O7ZMRrkCDgFmLyjXMM4shlKgJijOPXb/UQfqXwmndwwA+w=="
Supported: com.microsoft.msrtc.presence, adhoclist
ms-keep-alive: UAC;hop-hop=yes
Event: registration
Allow-Events: presence
Content-Length: 0
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

$$$$START-MESSAGE$$$$
TraceSeqNum: 10 Outgoing Message { Local => Unknown } Time:
2005/10/28-17:05:48.0646
SIP/2.0 401 Unauthorized
Date: Fri, 28 Oct 2005 11:35:48 GMT
WWW-Authenticate: NTLM realm="SIP Communications Service",
targetname="virtu-test-w2k3.mslc.com"
Via: SIP/2.0/TCP 172.16.3.48:9682;ms-received-port=1110;ms-received-cid=800
From:
<sip:user3@mslc.com>;tag=062fbd3023ea4c66a3fab4d4c1adb9a6;epid=3b7eac36d5
To: <sip:user3@mslc.com>;tag=19A2133BC36D7F6BC75DED4CF28BEAA2
Call-ID: 4957d9592b344dffa6b79f81fa340b96
CSeq: 5 REGISTER
Content-Length: 0
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

$$$$START-MESSAGE$$$$
TraceSeqNum: 11 Incoming Message { Unknown => Unknown } Time:
2005/10/28-17:06:07.0143
REGISTER sip:mslc.com SIP/2.0
Via: SIP/2.0/TCP 172.16.3.48:9682
Max-Forwards: 70
From:
<sip:user3@mslc.com>;tag=0a8ac17014884d1190cb0bf3025a6a37;epid=3b7eac36d5
To: <sip:user3@mslc.com>
Call-ID: 777da38a0b6742cb817e0a227863ae35
CSeq: 1 REGISTER
Contact: <sip:172.16.3.48:9682;transport=tcp>;methods="INVITE, MESSAGE,
INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER,
BENOTIFY";proxy=replace
User-Agent: RTC/1.3.5470 (Messenger 5.1.0701)
Supported: com.microsoft.msrtc.presence, adhoclist
ms-keep-alive: UAC;hop-hop=yes
Event: registration
Allow-Events: presence
Content-Length: 0
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

$$$$START-MESSAGE$$$$
TraceSeqNum: 12 Outgoing Message { Local => Unknown } Time:
2005/10/28-17:06:07.0143
SIP/2.0 401 Unauthorized
Date: Fri, 28 Oct 2005 11:36:07 GMT
WWW-Authenticate: NTLM realm="SIP Communications Service",
targetname="virtu-test-w2k3.mslc.com"
Via: SIP/2.0/TCP 172.16.3.48:9682;ms-received-port=1111;ms-received-cid=900
From:
<sip:user3@mslc.com>;tag=0a8ac17014884d1190cb0bf3025a6a37;epid=3b7eac36d5
To: <sip:user3@mslc.com>;tag=19A2133BC36D7F6BC75DED4CF28BEAA2
Call-ID: 777da38a0b6742cb817e0a227863ae35
CSeq: 1 REGISTER
Content-Length: 0
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

$$$$START-MESSAGE$$$$
TraceSeqNum: 13 Incoming Message { Unknown => Unknown } Time:
2005/10/28-17:06:08.0034
REGISTER sip:mslc.com SIP/2.0
Via: SIP/2.0/TCP 172.16.3.48:9682
Max-Forwards: 70
From:
<sip:user3@mslc.com>;tag=0a8ac17014884d1190cb0bf3025a6a37;epid=3b7eac36d5
To: <sip:user3@mslc.com>
Call-ID: 777da38a0b6742cb817e0a227863ae35
CSeq: 2 REGISTER
Contact: <sip:172.16.3.48:9682;transport=tcp>;methods="INVITE, MESSAGE,
INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER,
BENOTIFY";proxy=replace
User-Agent: RTC/1.3.5470 (Messenger 5.1.0701)
Authorization: NTLM qop="auth", realm="SIP Communications Service",
targetname="virtu-test-w2k3.mslc.com", gssapi-data=""
Supported: com.microsoft.msrtc.presence, adhoclist
ms-keep-alive: UAC;hop-hop=yes
Event: registration
Allow-Events: presence
Content-Length: 0
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

$$$$START-MESSAGE$$$$
TraceSeqNum: 14 Outgoing Message { Local => Unknown } Time:
2005/10/28-17:06:08.0034
SIP/2.0 401 Unauthorized
Date: Fri, 28 Oct 2005 11:36:08 GMT
WWW-Authenticate: NTLM opaque="7A0CE4B9",
gssapi-data="TlRMTVNTUAACAAAAAAAAADgAAADzgpjiINsBIMX6CYgAAAAAAAAAAI4AjgA4AAAABQLODgAAAA8CAAgATQBTAEwAQwABAB4AVgBJAFIAVABVAC0AVABFAFMAVAAtAFcAMgBLADMABAAQAG0AcwBsAGMALgBjAG8AbQADADAAdgBpAHIAdAB1AC0AdABlAHMAdAAtAHcAMgBrADMALgBtAHMAbABjAC4AYwBvAG0ABQAQAG0AcwBsAGMALgBjAG8AbQAAAAAA",
targetname="virtu-test-w2k3.mslc.com", realm="SIP Communications Service"
Via: SIP/2.0/TCP 172.16.3.48:9682;ms-received-port=1111;ms-received-cid=900
From:
<sip:user3@mslc.com>;tag=0a8ac17014884d1190cb0bf3025a6a37;epid=3b7eac36d5
To: <sip:user3@mslc.com>;tag=19A2133BC36D7F6BC75DED4CF28BEAA2
Call-ID: 777da38a0b6742cb817e0a227863ae35
CSeq: 2 REGISTER
Content-Length: 0
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

$$$$START-MESSAGE$$$$
TraceSeqNum: 15 Incoming Message { Unknown => Unknown } Time:
2005/10/28-17:06:08.0886
REGISTER sip:mslc.com SIP/2.0
Via: SIP/2.0/TCP 172.16.3.48:9682
Max-Forwards: 70
From:
<sip:user3@mslc.com>;tag=0a8ac17014884d1190cb0bf3025a6a37;epid=3b7eac36d5
To: <sip:user3@mslc.com>
Call-ID: 777da38a0b6742cb817e0a227863ae35
CSeq: 3 REGISTER
Contact: <sip:172.16.3.48:9682;transport=tcp>;methods="INVITE, MESSAGE,
INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER,
BENOTIFY";proxy=replace
User-Agent: RTC/1.3.5470 (Messenger 5.1.0701)
Authorization: NTLM qop="auth", opaque="7A0CE4B9", realm="SIP Communications
Service", targetname="virtu-test-w2k3.mslc.com",
gssapi-data="TlRMTVNTUAADAAAAGAAYAHwAAAAYABgAlAAAABAAEABIAAAACgAKAFgAAAAaABoAYgAAABAAEACsAAAAVYKQQgUAkwgAAAAPbQBzAGwAYwAuAGMAbwBtAHUAcwBlAHIAMwBEAFQALQBOAFMALQBNAFMARwAtAFMAUgBWAMkUlJwXfYTWQtClPyBG8NH91izwMyJ335Hxl3jHow0GA5z7EDXyNSFqFFYFvDPAOCXtNVBNppbqoe/4oIMy/yo="
Supported: com.microsoft.msrtc.presence, adhoclist
ms-keep-alive: UAC;hop-hop=yes
Event: registration
Allow-Events: presence
Content-Length: 0
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

$$$$START-MESSAGE$$$$
TraceSeqNum: 16 Outgoing Message { Local => Unknown } Time:
2005/10/28-17:06:09.0456
SIP/2.0 200 OK
Authentication-Info: NTLM rspauth="0100000000000000DAA65CBFA4525B97",
srand="95248C5C", snum="1", opaque="7A0CE4B9", qop="auth",
targetname="virtu-test-w2k3.mslc.com", realm="SIP Communications Service"
ms-keep-alive: UAS; tcp=no; hop-hop=yes; end-end=no; timeout=300
Via: SIP/2.0/TCP 172.16.3.48:9682;ms-received-port=1111;ms-received-cid=900
From:
<sip:user3@mslc.com>;tag=0a8ac17014884d1190cb0bf3025a6a37;epid=3b7eac36d5
To: <sip:user3@mslc.com>;tag=19A2133BC36D7F6BC75DED4CF28BEAA2
Call-ID: 777da38a0b6742cb817e0a227863ae35
CSeq: 3 REGISTER
Contact:
<sip:172.16.3.48:1111;transport=tcp;ms-received-cid=900>;methods="INVITE,
MESSAGE, INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER,
BENOTIFY";expires=7200
Expires: 7200
presence-state: required="yes",resync="yes"
Allow-Events:
vnd-microsoft-provisioning,vnd-microsoft-roaming-contacts,vnd-microsoft-roaming-ACL,presence,presence.wpending
Supported: adhoclist
Server: RTC/2.1
Content-Length: 0
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

$$$$START-MESSAGE$$$$
TraceSeqNum: 17 Incoming Message { Unknown => Unknown } Time:
2005/10/28-17:06:10.0187
SUBSCRIBE sip:user3@mslc.com SIP/2.0
Via: SIP/2.0/TCP 172.16.3.48:9682
Max-Forwards: 70
From:
<sip:user3@mslc.com>;tag=aae67d9010d44d38873e6bdef6ec7008;epid=3b7eac36d5
To: <sip:user3@mslc.com>
Call-ID: c7ce277cefee42888a2c599ae0370ae9
CSeq: 1 SUBSCRIBE
Contact:
<sip:user3@mslc.com:9682;maddr=172.16.3.48;transport=tcp>;proxy=replace
User-Agent: RTC/1.3
Event: vnd-microsoft-roaming-contacts
Accept: application/vnd-microsoft-roaming-contacts+xml
Supported: com.microsoft.autoextend
Supported: ms-benotify
Proxy-Require: ms-benotify
Supported: ms-piggyback-first-notify
Proxy-Authorization: NTLM qop="auth", realm="SIP Communications Service",
opaque="7A0CE4B9", crand="c5daf4db", cnum="1",
targetname="virtu-test-w2k3.mslc.com",
response="010000003764393072621d56a4525b97"
Content-Length: 0
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

$$$$START-MESSAGE$$$$
TraceSeqNum: 18 Outgoing Message { Local => Unknown } Time:
2005/10/28-17:06:10.0288
SIP/2.0 200 OK
Authentication-Info: NTLM rspauth="0100000028F71300D7930D60A4525B97",
srand="7E6C6B83", snum="2", opaque="7A0CE4B9", qop="auth",
targetname="virtu-test-w2k3.mslc.com", realm="SIP Communications Service"
Contact: <sip:virtu-test-w2k3.mslc.com;transport=tcp>
Content-Length: 175
Via: SIP/2.0/TCP 172.16.3.48:9682;ms-received-port=1111;ms-received-cid=900
From:
<sip:user3@mslc.com>;tag=aae67d9010d44d38873e6bdef6ec7008;epid=3b7eac36d5
To: <sip:user3@mslc.com>;tag=A8EA0DCA
Call-ID: c7ce277cefee42888a2c599ae0370ae9
CSeq: 1 SUBSCRIBE
Expires: 45791
Content-Type: application/vnd-microsoft-roaming-contacts+xml
Event: vnd-microsoft-roaming-contacts
subscription-state: active;expires=45791
ms-piggyback-cseq: 4
Supported: com.microsoft.autoextend, ms-piggyback-first-notify, ms-benotify
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

$$$$START-MESSAGE$$$$
TraceSeqNum: 19 Incoming Message { Unknown => Unknown } Time:
2005/10/28-17:06:14.0033
SUBSCRIBE sip:user3@mslc.com SIP/2.0
Via: SIP/2.0/TCP 172.16.3.48:9682
Max-Forwards: 70
From:
<sip:user3@mslc.com>;tag=0ca75fec65e24d39ae14968e92644be6;epid=3b7eac36d5
To: <sip:user3@mslc.com>
Call-ID: adf8d5d88e2342caa0df14d96dae2999
CSeq: 1 SUBSCRIBE
Contact:
<sip:user3@mslc.com:9682;maddr=172.16.3.48;transport=tcp>;proxy=replace
User-Agent: RTC/1.3
Event: vnd-microsoft-roaming-ACL
Accept: application/vnd-microsoft-roaming-acls+xml
Supported: com.microsoft.autoextend
Supported: ms-benotify
Proxy-Require: ms-benotify
Supported: ms-piggyback-first-notify
Proxy-Authorization: NTLM qop="auth", realm="SIP Communications Service",
opaque="7A0CE4B9", crand="746dbcd8", cnum="2",
targetname="virtu-test-w2k3.mslc.com",
response="010000003566656368a1839ea4525b97"
Content-Length: 0
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

$$$$START-MESSAGE$$$$
TraceSeqNum: 20 Outgoing Message { Local => Unknown } Time:
2005/10/28-17:06:14.0093
SIP/2.0 200 OK
Authentication-Info: NTLM rspauth="0100000028F713002AE76000A4525B97",
srand="833E9FC3", snum="3", opaque="7A0CE4B9", qop="auth",
targetname="virtu-test-w2k3.mslc.com", realm="SIP Communications Service"
Contact: <sip:virtu-test-w2k3.mslc.com;transport=tcp>
Content-Length: 180
Via: SIP/2.0/TCP 172.16.3.48:9682;ms-received-port=1111;ms-received-cid=900
From:
<sip:user3@mslc.com>;tag=0ca75fec65e24d39ae14968e92644be6;epid=3b7eac36d5
To: <sip:user3@mslc.com>;tag=F6A273D6
Call-ID: adf8d5d88e2342caa0df14d96dae2999
CSeq: 1 SUBSCRIBE
Expires: 46223
Content-Type: application/vnd-microsoft-roaming-acls+xml
Event: vnd-microsoft-roaming-ACL
subscription-state: active;expires=46223
ms-piggyback-cseq: 4
Supported: com.microsoft.autoextend, ms-piggyback-first-notify, ms-benotify
----****MESSAGE BODY DELETED****----

$$$$END-MESSAGE$$$$

Jeremy Buch · Guest

I don't see any failure - the 401 responses come in as authentication is
negotiated, but the 200 OK response to the REGISTER eventually comes after
proper credentials are entered on the client and negotiation finishes.

If the client is failing to login, use the registry on the client to enable
logging and look there. From this initial log, though, it looks like a
successful client login (from the server side, at least).

--
Jeremy Buch (Microsoft)

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup.

"Srinivas" <Srinivas@discussions.microsoft.com> wrote in message
news:3327CB59-F117-416F-9E20-8933CD35D361@microsoft.com...

Srinivas · Guest

HI

This the log at client side. I am unable to trace what exactly is the
problem. Please provide me some solution
07:05:34.568 1A8:59C INFO :: End of Sending Packet - 192.168.0.205:5060
(From Local Address: 172.16.3.48:1924)
07:05:34.908 1A8:59C INFO :: Data Received - 192.168.0.205:5060 (To Local
Address: 172.16.3.48:1924):
07:05:34.908 1A8:59C INFO :: SIP/2.0 401 Unauthorized

Date: Mon, 31 Oct 2005 07:06:08 GMT

WWW-Authenticate: NTLM realm="SIP Communications Service",
targetname="virtu-test-w2k3.mslc.com"

Via: SIP/2.0/TCP 172.16.3.48:15344;ms-received-port=1924;ms-received-cid=400

From:
<sip:user3@mslc.com>;tag=0c52ee18e41f40afab9d5aec879d51e7;epid=c18d4a1908

To: <sip:user3@mslc.com>;tag=875A929ECFFF5F3B85B66F1AF006DBC0

Call-ID: 65027bbcbf5a42f4af0565222fa923af

CSeq: 5 REGISTER

Content-Length: 0

07:05:34.908 1A8:59C INFO :: End of Data Received - 192.168.0.205:5060 (To
Local Address: 172.16.3.48:1924)
07:05:34.908 1A8:59C INFO :: SIP_MSG_PROCESSOR::GetChallengeListForPlatform
ProtocolsFromPlatform=0xe
07:05:34.908 1A8:59C TRACE :: SIP_STACK::FindProviderSAContext SA_CONTEXT
found:virtu-test-w2k3.mslc.com- 015F6D70, this 015F4838
07:05:34.908 1A8:59C TRACE :: SIP_STACK::FindProviderSAContext SA_CONTEXT
found:virtu-test-w2k3.mslc.com- 015F6D70, this 015F4838
07:05:34.908 1A8:59C TRACE :: SIP_STACK::FindProviderSAContext SA_CONTEXT
found:virtu-test-w2k3.mslc.com- 015F6D70, this 015F4838
07:05:34.908 1A8:59C ERROR :: OUTGOING_TRANSACTION::ProcessAuthRequired-Too
many 407s seen. Failing the session
07:05:34.908 1A8:59C ERROR ::
OUTGOING_TRANSACTION::ProcessAuthRequiredResponse - ProcessAuthRequired
failed 80ef0191
07:05:34.908 1A8:59C INFO :: CRTCProfile::SetState - [015F8268]
enState:1->5, statusCode=80ef0191, text=(null)
07:05:34.908 1A8:59C INFO :: RegistrationStateChangeEvent-
profile=015F8268, state=5, statusCode=80ef0191, text=(null)
07:05:34.908 1A8:59C INFO :: CRTCProfile::SetState - register error, clear
postponed watchers
07:05:34.918 1A8:59C INFO :: CRTCClient::InternalEnableProfileEx -
pProfile=015F8268, regFlag=0x0, roamingFlag=0x0, realm=<SIP Communications
Service>
07:05:34.918 1A8:59C INFO :: RoamingSession::SetDeltaNum[015F831C],0->0
07:05:34.918 1A8:59C INFO :: RoamingSession::SetDeltaNum[015F8360],0->0
07:05:34.918 1A8:59C INFO :: RoamingSession::SetDeltaNum[015F83BC],0->0
07:05:34.918 1A8:59C INFO :: RoamingSession::SetDeltaNum[015F83D4],0->0
07:05:34.918 1A8:59C INFO :: RoamingSession::SetDeltaNum[015F83A4],0->0
07:05:34.918 1A8:59C INFO :: SetRoamingStatus - roamingFlag:old(0)|=flag(0)
--> new(0), statusCode=0
07:05:34.918 1A8:59C INFO :: RoamingSession::SetDeltaNum[015F83D4],0->0
07:06:08.186 1A8:59C TRACE :: put_ClientName<Messenger>
07:06:08.186 1A8:59C TRACE :: put_ClientCurVer<5.1.0701>
07:06:08.186 1A8:59C INFO :: RoamingSession::SetDeltaNum[015F831C],0->0
07:06:08.186 1A8:59C INFO :: RoamingSession::SetDeltaNum[015F8360],0->0
07:06:08.186 1A8:59C INFO :: RoamingSession::SetDeltaNum[015F83D4],0->0
07:06:08.186 1A8:59C INFO :: RoamingSession::SetDeltaNum[015F83BC],0->0
07:06:08.186 1A8:59C INFO :: RoamingSession::SetDeltaNum[015F83A4],0->0
07:06:08.206 1A8:59C TRACE :: put_AllowedAuth:1000e->1000e
07:06:08.206 1A8:59C INFO :: RoamingSession::SetDeltaNum[015F831C],0->0
07:06:08.206 1A8:59C INFO :: RoamingSession::SetDeltaNum[015F8360],0->0
07:06:08.206 1A8:59C INFO :: RoamingSession::SetDeltaNum[015F83D4],0->0
07:06:08.206 1A8:59C INFO :: RoamingSession::SetDeltaNum[015F83BC],0->0
07:06:08.206 1A8:59C INFO :: RoamingSession::SetDeltaNum[015F83A4],0->0
07:06:08.206 1A8:59C INFO :: CRTCClient::RealAddBuddy -
uri=sip:user2@mslc.com,name=,data=
07:06:08.206 1A8:59C INFO :: persistent=1, subscribType=0,
profile=015F826C, flag=0, roam=0
07:06:08.206 1A8:59C INFO ::
Buddy::init(015F8CD8),sip:user2@mslc.com,pers=1,sub=0,profile=015F826C,flag=0
07:06:08.206 1A8:59C INFO :: buddy name=,data=
07:06:08.206 1A8:59C INFO :: BuddyEvent-- buddy=015F8CD8, enType=0,
statusCode=0, text=(null)
07:06:08.206 1A8:59C INFO :: BuddyGroupEvent--enType=3, statusCode=0,
buddyGroup=015F8838, buddy=015F8CD8
07:06:08.206 1A8:59C INFO :: CRTCClient::RealAddBuddy -
uri=sip:user3@mslc.com,name=,data=
07:06:08.206 1A8:59C INFO :: persistent=1, subscribType=0,
profile=015F826C, flag=0, roam=0
07:06:08.206 1A8:59C INFO ::
Buddy::init(015F8C20),sip:user3@mslc.com,pers=1,sub=0,profile=015F826C,flag=0
07:06:08.206 1A8:59C INFO :: buddy name=,data=
07:06:08.206 1A8:59C INFO :: BuddyEvent-- buddy=015F8C20, enType=0,
statusCode=0, text=(null)
07:06:08.206 1A8:59C INFO :: BuddyGroupEvent--enType=3, statusCode=0,
buddyGroup=015F8838, buddy=015F8C20
07:06:08.206 1A8:59C INFO :: RoamingSession::SetDeltaNum[015F83D4],0->0
07:06:08.216 1A8:59C INFO :: CRTCClient::InternalEnableProfileEx -
pProfile=015F8268, regFlag=0xf, roamingFlag=0xf, realm=<SIP Communications
Service>
07:06:08.226 1A8:59C INFO :: CRTCProfile::SetState - [015F8268]
enState:5->1, statusCode=0, text=(null)
07:06:08.226 1A8:59C INFO :: RegistrationStateChangeEvent-
profile=015F8268, state=1, statusCode=0, text=(null)
07:06:09.508 1A8:59C INFO :: Sending Packet - 192.168.0.205:5060 (From
Local Address: 172.16.3.48:1925):
07:06:09.508 1A8:59C INFO :: REGISTER sip:mslc.com SIP/2.0

Via: SIP/2.0/TCP 172.16.3.48:15344

Max-Forwards: 70

From:
<sip:user3@mslc.com>;tag=9dc9404930224848b4505c20da2b5dcb;epid=c18d4a1908

To: <sip:user3@mslc.com>

Call-ID: 6eefb6d5fe9c4ed5bba278fec993798b

CSeq: 1 REGISTER

Contact: <sip:172.16.3.48:15344;transport=tcp>;methods="INVITE, MESSAGE,
INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER,
BENOTIFY";proxy=replace

User-Agent: RTC/1.3.5470 (Messenger 5.1.0701)

Supported: com.microsoft.msrtc.presence, adhoclist

ms-keep-alive: UAC;hop-hop=yes

Event: registration

Allow-Events: presence

Content-Length: 0

Jeremy Buch · Guest

What are you seeing from the client? Do you fail to login altogether, or
are you prompted for credentials and after you enter them you login
properly? I want to make sure I understand what you are troubleshooting.
Is this failure happening after some time and you are logged out, or what?

The log I saw before eventually succeeded to login, so I want to understand
if you are logging in fine eventually or not. The client will try to login
using desktop credentials before prompting for credentials in the UI, so I
just want to make sure you aren't trying to debug the fact that it may fail
to login when trying to use desktop credentials with the SIP URI you have
specified.

--
Jeremy Buch (Microsoft)

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup.

"Srinivas" <Srinivas@discussions.microsoft.com> wrote in message
news:3073EEF7-EC4A-424C-B426-4E95811C95C4@microsoft.com...

Srinivas · Guest

Jeremy

As I mentioned , I am trying connection between two branch offices which are
not of same domain and both connected using VPN. When I try connecting from
the remote office client to local server I get the login prompt to enter
login credentials and after that it fails with messange

Signing in to SIP Communications Service failed because the sign-in name,
username, or password is incorrect, or the authentication service is not
compatible with this version of the program. If you have signed in correctly
and the problem persists, contact your network administrator.

Or

SIP Communications Service failed because the service is temporarily
unavailable

Please suggest me If I can achieve this without using proxy or do you
recemmond using proxy. If I have to use proxy what is to be done at my end
because I donot have any access rights on the remote side.

"Jeremy Buch" wrote:

	Windows Server Forum Index -> Live Communications Server	All times are GMT
Page 1 of 1