Exchange Instant Messenger

[telexpress]

I am running exchange 2000 on server 2000 with instant messaging service thorugh exchange. I am having trouble connecting to the instant messaging server through instant messenger. I deleted the old protocol and installed another one and set everyone up through AD. What is going on?

 

[PHead2]

Can you detail the problem a little more specifically?

Can users not logon with the client or can messages not be sent/received?

 

[telexpress]

No client can logon to the IM server

 

[PHead2]

Make sure you are using the correct user name. Open AD users and computers, select properties for an IM enabled account and pick the excahnge features tab. Pick IM and select properties. Make sure the Instant Messaging User Address is what the user uses when attempting to logon.

What exactly happens when a user tries to logon? Is there an error saying that the server can't be reached or is there an error saying that there is password/account problem?

 

[lbicher]

What version of the IM client are you using? I had also had a problem setting this up recently. We were going to use the version of MSN Messenger that ships with Windows XP and found that it doesn't support IM through Exchange. Microsoft has a versoin available for download that does support it.

Also, another problem I had was the Proxy server settings in IE. In my case, while I had IE set to use my proxy and I did check "Bypass Proxy for local addresses", I did not realize that setting did not use the same Local Address Table that the Firewall Client for ISA Server does. So I was still going through my Proxy server since the Exchange server is on a different subnet then me. Integrated Authentication doesnot pass through the proxy so the users couldn't log in. The solution was to add additional IP addresses the IE would bypass the proxy server for.

 

[telexpress]

Could it be a security pronlem? I am using IM 4.7 for exchange and it doesn't matter what OS I am using, it does not connect. I installed, Microsoft Software Update Services recently and i believe it changed some of my security settings. What can i do to check what it changed and if it affected my IM service?

When I click "Click here to sign in"; the window "Sign in to Exchange Instant Messaging" comes up and says
"Exchange Instant Messaging Sign-in Failure

The person logged on to this computer does not have permission to use the specified e-mail address. Please type your e-mail address and password."

Now, I tried everything, I went to AD and check what my email address was set up to be for every user and tried that, no luck. IM would always sign-in automatically because when you sign into our domain, the login credentials would carry over to IM.

 

[PHead2]

Just so I'm clear, you're saying it used to work but now it's stopped?

Check the following:

Launch Exchange System Manager, open Global Settings, right-click Instant Messaging Settings and click on the Firewall Topology tab. The box asking if the network is behind a firewall should be unchecked.

Also, are you using the FQDN for the instant messaging server?

Also check the

http://www logs

for error codes generated when attempting to log on to the IM server and post them here.

 

[telexpress]

It used to work until I installed Microsoft Software Update Services which I believe changed some security settings and I don't know exactly which ones. The firewall is not checked in global settings. I am not sure what FQDN is or if i am even using it.

Error log:
Microsoft-WebDAV-MiniRedir/5.1.2600
2003-03-03 12:32:26 192.168.0.156 - 192.168.0.205 80 GET /<Rejected-By-UrlScan> ~/instmsg/aliases/jake 404 msmsgs/4.7.0.106

Microsoft-WebDAV-MiniRedir/5.1.2600
2003-03-03 12:51:00 192.168.0.250 - 192.168.0.205 80 GET /<Rejected-By-UrlScan> ~/instmsg/aliases/jimmy 404 msmsgs/4.7.0.106

 

[MBlank]

There is a great link here with alot of possible hints for you

http://support.microsoft.com/default.aspx?scid=kb;en-us;319758

 

[PHead2]

A 404 error code usually means that the email address you entered on the client does not match a valid IM user address, but you said you checked this.

Where exactly did these errors turn up?

The log I'm interested in is the W3SVC log on the IM server.

 

[telexpress]

That log that I just put up was from the W3SVC1, which is our default web site in IIS. I tried what MBlank gave me but it does the same thing.

 

[PHead2]

Can you post the contents of the urlscan.ini file.

 

[telexpress]

[options]
UseAllowVerbs=1 ; if 1, use [AllowVerbs] section, else use [DenyVerbs] section
UseAllowExtensions=0 ; if 1, use [AllowExtensions] section, else use [DenyExtensions] section
NormalizeUrlBeforeScan=1 ; if 1, canonicalize URL before processing
VerifyNormalization=1 ; if 1, canonicalize URL twice and reject request if a change occurs
AllowHighBitCharacters=0 ; if 1, allow high bit (ie. UTF8 or MBCS) characters in URL
AllowDotInPath=0 ; if 1, allow dots that are not file extensions
RemoveServerHeader=0 ; if 1, remove &quot;Server&quot; header from response
EnableLogging=1 ; if 1, log UrlScan activity
PerProcessLogging=0 ; if 1, the UrlScan.log filename will contain a PID (ie. UrlScan.123.log)
AllowLateScanning=0 ; if 1, then UrlScan will load as a low priority filter.
PerDayLogging=1 ; if 1, UrlScan will produce a new log each day with activity in the form UrlScan.010101.log
RejectResponseUrl= ; UrlScan will send rejected requests to the URL specified here. Default is /<Rejected-by-UrlScan>
UseFastPathReject=0 ; If 1, then UrlScan will not use the RejectResponseUrl or allow IIS to log the request

; If RemoveServerHeader is 0, then AlternateServerName can be
; used to specify a replacement for IIS's built in 'Server' header
AlternateServerName=

[AllowVerbs]

;
; The verbs (aka HTTP methods) listed here are those commonly
; processed by a typical IIS server.
;
; Note that these entries are effective if &quot;UseAllowVerbs=1&quot;
; is set in the [Options] section above.
;

GET
HEAD
POST

[DenyVerbs]

;
; The verbs (aka HTTP methods) listed here are used for publishing
; content to an IIS server via WebDAV.
;
; Note that these entries are effective if &quot;UseAllowVerbs=0&quot;
; is set in the [Options] section above.
;

PROPFIND
PROPPATCH
MKCOL
DELETE
PUT
COPY
MOVE
LOCK
UNLOCK
OPTIONS
SEARCH

[DenyHeaders]

;
; The following request headers alter processing of a
; request by causing the server to process the request
; as if it were intended to be a WebDAV request, instead
; of a request to retrieve a resource.
;

Translate:
If:
Lock-Token:

[AllowExtensions]

;
; Extensions listed here are commonly used on a typical IIS server.
;
; Note that these entries are effective if &quot;UseAllowExtensions=1&quot;
; is set in the [Options] section above.
;

.asp
.cer
.cdx
.asa
.htm
.html
.txt
.jpg
.jpeg
.gif

;.idq
;.htw
;.ida
;.idc
;.shtm
;.shtml
;.stm
;.htr
;.printer
[DenyExtensions]

;
; Extensions listed here either run code directly on the server,
; are processed as scripts, or are static files that are
; generally not intended to be served out.
;
; Note that these entries are effective if &quot;UseAllowExtensions=0&quot;
; is set in the [Options] section above.
;

; Deny executables that could run on the server
.bat
.cmd
.com

; Deny infrequently used scripts
.htw ; Maps to webhits.dll, part of Index Server
.ida ; Maps to idq.dll, part of Index Server
.idq ; Maps to idq.dll, part of Index Server
.htr ; Maps to ism.dll, a legacy administrative tool
.idc ; Maps to httpodbc.dll, a legacy database access tool
.shtm ; Maps to ssinc.dll, for Server Side Includes
.shtml ; Maps to ssinc.dll, for Server Side Includes
.stm ; Maps to ssinc.dll, for Server Side Includes
.printer ; Maps to msw3prt.dll, for Internet Printing Services

; Deny various static files
.ini ; Configuration files
.log ; Log files
.pol ; Policy files
.dat ; Configuration files

;.asp
;.cer
;.cdx
;.asa
[DenyUrlSequences]
.. ; Don't allow directory traversals
./ ; Don't allow trailing dot on a directory name
\ ; Don't allow backslashes in URL
: ; Don't allow alternate stream access
% ; Don't allow escaping after normalization
& ; Don't allow multiple CGI processes to run on a single request

 

[PHead2]

Ok, from the DenyVerbs section remove:

PROPFIND
PROPPATCH

Add this to the allow verbs section. Also add:

SUBSCRIBE
UNSUBSCRIBE
ACL
NOTIFY
SUBSCRIPTIONS

Reboot to make sure these take effect.

Let me know if it works!

 

[PHead2]

Also, you should change AllowDotInPath=0 to AllowDotInPath=1

 

[homerunkevin]

Hi all

I got the following Error Message
&quot;Signing in to Microsoft Exchange Instant Messaging failed because of a problem connecting to the services&quot;

Love always,
Kevin Z
Techncial Support specailist
kevin@hsmc.com

 

[rpiver]

Hello All,
I just recently ran into the same problem that everyone is having above &quot;Signing in to Microsoft Exchange Instant Messaging failed because of a problem connecting to the services&quot; and was able to solve it by doing the following.

If your exchange and DNS server are the same computer and you do not have to have the _rvp record in DNS, it will not allow you to sign in. The bad thing about this is that you have to recreate everything including the IM virtual server. Also make sure to run the following commands on the DNS server ipconfig /flushdns followed by ipconfig /registerdns.

Also, if you are using host headers make sure to have the appropiate entry in DNS for the Host header.

Check in AD Users and Computers, Double CLick on a user that has Instant Messenging Enable, go to the Exchange Features tab, select Instant Messaging, and click properties.

Your Instant Messaging Url address and Instant Messaging Home Server address should be the same.

Also check what your Instant Messaging User address is. That is the &quot;email&quot; address that you will use to sign onto Instant Messenger.

In my particular case I use a host header name of IM2 and my Instant Messaging User address is username@IM2
I cannot use the FQDN.

My Instant Messaging Url address is

http://IM2/instmsg/aliases/username

My Instant Messaging Home Server address is the same.

I hope that this helps,
Rad Piver
GlobalStrata Solutions, Inc.
MCSE, MCP+I, CCNP, CNA, A+

 

[mawilson]

Does anyone know any way that I can use my domain name for the IMdomainname? I can get it to work by using the server name for the IMdomainname but I would like to use domain (or domain.com). rpiver said he couldn't use the FQDN, but I was just wondering if anyone else had any other experiences getting it to work.
I have the _rvp record in dns going to server.domain.local.