Signing in to Instant Messaging fails

[Bernardo Fernandez]

I am no expert on Exchange Server, so bear on me. I have a
Small Business Server 2000 which works fine. I had my
Instant Messaging working perfectly until I made some
arrangements in my ISA firewall to protect from the
Blaster worm. (I created a protocol rule for blocking
ports 135 tcp, 139, tcp, 445 tcp, 593 tcp, 3333 tcp, 4444
tcp, 69 udp, 135 udp, 137 udp, 138 udp and 666-765 tcp).

Coincidentally, I now receive the following text "Signing
in to Microsoft Exchange Instant Messaging failed because
the service is temporarily unavailable. Please try again
later." when trying to login from a client computer into
IM. I did KB article 812210 procedure but not found any
object at LostAndFoundConfig container.

Just in case, I reversed the settings at the ISA server
protocol rules and still cannot sign into instant
messaging. I ignore if there is any relation between the
ISA settings and IM not working.

I would really appreciate any help.

[Leon Wong [MSFT]]

Hard to tell what's going on. One thing that may help diagnose the issue is
using a web browser to connect to IIS on the IM server machine. Exchange IM
uses the HTTP protocol, so using a web browser can help check for basic
connectivity issues and may give more intelligible error messages.

--------------------
Content-Class: urn:content-classes:message
From: "Bernardo Fernandez" <bf...@complet.com.mx>
Sender: "Bernardo Fernandez" <bf...@complet.com.mx>
Subject: Signing in to Instant Messaging fails
Date: Fri, 29 Aug 2003 10:39:30 -0700
Lines: 22
Message-ID: <34bf01c36e54$800b7a90$7d02...@phx.gbl>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Thread-Index: AcNuVIALJ1wCppqYR0yDiKU6SU+t4w==
Newsgroups: microsoft.public.exchange2000.realtime.collaboration
Path: cpmsftngxa06.phx.gbl
Xref: cpmsftngxa06.phx.gbl
microsoft.public.exchange2000.realtime.collaboration:4413
NNTP-Posting-Host: TK2MSFTNGXS01 10.40.2.125
X-Tomcat-NG: microsoft.public.exchange2000.realtime.collaboration

--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

[Bernardo Fernandez]

Thank you very much Leon. Please let me know the procedure
for using a web browser to connect to IIS.

By checking the event viewer at the server, I am getting
the following in the application log:

"POP3SVC Warning
Connection from 192.168.16.12 refused because the
corresponding virtual server instance could not be found
or is not running. The error code was 0x43."

Being that address, the client's DNS which tried to sign
in.

Maybe this can give us a clue.