_rvp._tcp... SRV record with Exchange2000 & WinM3 msn client

[JayShaw]

Ok....I have a couple of questions for you on this...

Does the RVP record contain the FQDN of the server in the "host offering
this service"? for ex server.domain.com?
or should it just contain the netbios name of the server "server", or should
it contain just the domain name "domain.com" ????

Im trying to get to the point where I can use my smtp Exchange 2k email
addresses as my login address for Instant messaging.

Secondly.....

Now when setting up the IM virtual server within system manager, should I
used the DNS (netbios) name of the server ? ("server") or the domain name
"domain.com" .

"news.pajo.com" <mat...@yahoo.com> wrote in message
news:OYWtpmSRAHA.164@cppssbbsa05...
> Exchange server running instant messenger service set up and functioning.
>
> DNS SRV record created to forward RVP port 80 requests to server within
> domain handling RVP service
> (ex. wh...@hotmail.com {im-user-address} requests logon from HOTMAIL.COM.
> SRV record forwards RVP service requests to IM.HOTMAIL.COM.) Kind of like
> an MX record in functionality...
> {hotmail only used to make description more understandable}
>
> This allows the end user to use there normal email address to logon to
> Instant Messaging Server instead of modifying the address to reflect the
> physical instant messaging server. (ex. wh...@im.hotmail.com)
>
> Win2000 clients seem to function just fine. But home user running WinME
is
> not. User can logon only if specifying the exact server name (ex.
> wh...@im.hotmail.com).
>
> Does anyone know of a possible reason for WinME or WinME MSN client v2 ->
3
> not properly requesting or accepting DNS SRV methods?
>
> I would assume that hotmail is using something similar to this but I can't
> seem to prove it :-)
>
> Does anyone actually have this working? ...Is this thing on?
>
> Thanks.
>
> Matt W.
>
>
>
>

[Mark Dudding]

First question:

Use the FQDN of the server where your IM router is running. If you only
have a home server installation, it acts as a router as well. Example -
im.somplace.com

Second question:

I would use the FQDN name when creating IM home servers or routers for that
matter. The suggestion to use the short name is because IM inherits it's
proxy settings from IE, and in most environments local servers (shortnames)
are not proxied. Therefore, if you have a proxied IE environment you might
want to consider not proxing FQDNs that are internal. Using a long name
will help facilitate IM connections for users in child domains or outside
your organization.

Example - *.somplace.com as a exception. Remember that Windows Integrated
Authentication does NOT work through a proxied connection.

NOTE: the following is a rough representation of the logon process for the
MSN messaging client for Exchange 2000 IM. It is not intended to be
complete. For a more detailed explanation the following URL points to a
document that outlines the operation for the RVP service:

http://msdn.microsoft.com/library/techart/rvp.htm

Example:

Username Firstname...@someplace.com
IM Router: im.someplace.com
IM Home Server: imhome1.someplace.com

When you start the MSN Messenger, the client will parse the domain name
(e.g. someplace.com) from the user address
(Firstname...@someplace.com) and attempt to contact the IM router
responsible for servicing this IM domain/ namespace. This one to one
mapping exists between each IM domain and the user's SMTP namespace by
creating an appropriate SRV entry for the TCP_RVP service in the
someplace.com namespace in DNS. In this case, the SMTP namespace
someplace.com would be mapped to the IM domain im.someplace.com hosted on
the IM router with the same name (im.someplace.com).

The messenger client will attempt a login subscription request with the IM
router.

The IM router will in turn attempt to determine the user's home server by
lookin up the attribute for the user's IM home server (MsExchIMPhysicalURL)
stored in the Active Directory. If this is successful, the IM router will
redirect the messenger client to that URL via a status code 302 message.
NOTE: MsExchIMPhysicalURL is tagged as part of the Global Catalog.
Therefore, GC replication has to occur before the IM router can successfully
look this value up (HTTP 404 messages in your log, when this step fails).

The messenger client will subsequently contact their appropriate IM home
server and complete the login subscription request by authenticating with
the IM home server. As part of the login subscription request, the client
notifies the IM home server of the user's status and client location (based
on the client IP address and port the MSN Messenger client is running on).
Additionally, the IM home server will notify any parties who have subscribed
to the user's presence information.

Cheers,

Mark

"JayShaw" <JS...@bigfootinteractive.com> wrote in message
news:OVJMGca...@cppssbbsa02.microsoft.com...

[Jonathan Steffan]

Go ahead and use your FQDN, it's better. RVP record should match what you
set up your webserver and IM virtual server under. I.E.: Your webserver is
running your default we and your IM web, the IM web having im.domain.com as
the header. You need to set your rvp record so it looks like the following:
im.domain.com. [0][0][80]

The website header, rvp record and Im virtual server's FQDM need to be the
same. Hope this helps.

-Jonathan Steffan
jonatha...@yahoo.com