I'm using it here for over half a year without any issues. Weird... <Siegfried />
> -----Original Message----- > From: Kevin Miller [mailto:[EMAIL PROTECTED]] > Sent: Monday, March 25, 2002 5:51 PM > To: MS-Exchange Admin Issues > Subject: RE: Instant Messenger Service > > The internal client accesses the standard MSNIM server why not just use > there's? I am so discouraging this morning. But this is not a fun thing > to do. Made it work once, but was so unstable, ended up giving up. > > --Kevinm M, WLKMMAS, UCC+WCA, And Beyond > http://www.daughtry.ca/ For Graphics and WebDesgin, GO here! > > > -----Original Message----- > From: John Weber [mailto:[EMAIL PROTECTED]] > Sent: Monday, March 25, 2002 8:47 AM > To: MS-Exchange Admin Issues > Subject: RE: Instant Messenger Service > > > This is in experimental stage only. > Yes, firewall in place. > VPN is not a good option, as most of the clients we work with won't let > that type of traffic out for only one person. > > So...what I'm trying to do is get the IM to work both directions on 80 > and 80 only, as all of the clients I know of allow 80 back and forth. > > John Weber > Consultant > Centerlogic > 503-262-0490 x203 > > > -----Original Message----- > From: Kevin Miller [mailto:[EMAIL PROTECTED]] > Sent: Monday, March 25, 2002 08:32 > To: MS-Exchange Admin Issues > Subject: RE: Instant Messenger Service > > > Do you not have a firewall? You planning on leavening things Wide open? > The best way to do this would be with a VPN. > > --Kevinm M, WLKMMAS, UCC+WCA, And Beyond http://www.daughtry.ca/ For > Graphics and WebDesgin, GO here! > > > -----Original Message----- > From: John Weber [mailto:[EMAIL PROTECTED]] > Sent: Monday, March 25, 2002 8:28 AM > To: MS-Exchange Admin Issues > Subject: RE: Instant Messenger Service > > > I have a need for the exchange hosted IM to be accessible from other, > outside the domain, users. > > In the case of my testing, I am using my domain at home to test for > connections. [EMAIL PROTECTED] is the office [EMAIL PROTECTED] is the > home. > > Both are fully registered FQDN dns entries, although there is no > IM.domainA.com registered. > > What I am trying to do is get the [EMAIL PROTECTED] to come in and use > the account for [EMAIL PROTECTED] and that is failing. I wonder if it > could be that the user name for domainA and domainB are the same, > although they are different domains. > > We have some other folks who work at client sites and are logged into > the client site domains, and as such, will be coming from an FQDN > environment when they authenticate into my Exchange IM. > > I know that I have a) something wrong, or b) this isn't going to work. > > At present, I am not so far along that I can't nuke and start over if > need be. > > I used the _rvp in local DNS. Are you saying that I may need to have a > IM.domainA.com registered with my exeternal DNS? > > John Weber > Consultant > Centerlogic > 503-262-0490 x203 > > > -----Original Message----- > From: Siegfried Weber [mailto:[EMAIL PROTECTED]] > Sent: Friday, March 22, 2002 16:46 > To: MS-Exchange Admin Issues > Subject: RE: Instant Messenger Service > > > Must be something else than. Using those steps I was able to get it > running here. I didn't use an RVP record but instead a FQDN when > creating the IM Virtual Server. Also I made sure the FQDN is registered > on the external DNS. > > What I don't understand is why you have [EMAIL PROTECTED] and > [EMAIL PROTECTED] What is the purpose of that? > > What did the user enter the logon dialog at home? > > On my system it is: > > IM address: [EMAIL PROTECTED] > Windows 2000 user name: MyUserName > Windows 2000 password: MyPassword > Windows 2000 domain name: MyWindows2000DomainName (netbios AFAIK) > > > -----Original Message----- > > From: John Weber [mailto:[EMAIL PROTECTED]] > > Sent: Saturday, March 23, 2002 12:34 AM > > To: MS-Exchange Admin Issues > > Subject: RE: Instant Messenger Service > > > > Great last name... > > > > OK...I reset the password. No workie. > > > > [EMAIL PROTECTED] works inside the firewall. > > > > [EMAIL PROTECTED] logs into his machine at home, and then tries to > > authenticate in, and constantly gets asked for the password, and it > > doesn't take. Home account is using a 2Kserver box with a registered > > domain as the login. Messenger says that the home account login > > doesn't have the permission > to > > use the email account, and asks for the proper password. > > > > Should work...doesn't. > > > > John Weber > > Consultant > > Centerlogic > > 503-262-0490 x203 > > > > > > -----Original Message----- > > From: Siegfried Weber [mailto:[EMAIL PROTECTED]] > > Sent: Friday, March 22, 2002 15:19 > > To: MS-Exchange Admin Issues > > Subject: RE: Instant Messenger Service > > > > > > The fix is to enable "Store passwords in reversible encryption" [1] > and > > reset each user password. Exchange 2000 IM doesn't use NTLM auth. > > > > [1] You have to make the decision if you want to allow that yourself. > > It's just the action need to be done to use Exchange IM from outside a > > > firewall. > > > > <Siegfried /> > > > > > -----Original Message----- > > > From: John Weber [mailto:[EMAIL PROTECTED]] > > > Sent: Friday, March 22, 2002 8:31 PM > > > To: MS-Exchange Admin Issues > > > Subject: RE: Instant Messenger Service > > > > > > We fixed the issue with the XP side by installing the setup from the > > e2k > > > cd. That adds the Exchange functionality to the Messenger. > > > > > > I have it working inside the firewall. > > > When I try to login from outside the firewall I get a message saying > > that > > > the user logged into the machine doesn't have rights to the email > > account. > > > It then asks for the credentials. > > > When I give it the proper user name, email address, etc, it simply > > dumps > > > back to asking for the password. > > > > > > If the fix is to open the firewall to allow NTLM authentication, I > am > > not > > > sure I want to do that? > > > > > > Any thoughts would be appreciated. > > > > > > John Weber > > > Consultant > > > Centerlogic > > > 503-262-0490 x203 > > > > > > > > > -----Original Message----- > > > From: William Lefkovics [mailto:[EMAIL PROTECTED]] > > > Sent: Friday, March 22, 2002 10:18 > > > To: MS-Exchange Admin Issues > > > Subject: RE: Instant Messenger Service > > > > > > > > > The IP scope doesn't matter. IM is a specialized web application > and > > MSN > > > Messenger is an application specific browser. > > > > > > I am aware of issues with the MSN Messenger that ships with XP. I > > replace > > > it with the MSN Messenger 4.6 from the Exchange download. > > > > > > > > > -----Original Message----- > > > From: John Weber [mailto:[EMAIL PROTECTED]] > > > Sent: Thursday, March 21, 2002 4:25 PM > > > To: MS-Exchange Admin Issues > > > Subject: Instant Messenger Service > > > > > > > > > Hi all, > > > > > > IM on e2k sp2 setup and functioning internal to our firewall. Went > in > > > pretty easy, and config wasn't too bad, except why didn't it do it > for > > me > > > when I installed? (side question, don't answer that). > > > > > > All the docs intimate that this puppy should accept connections from > > > > outside the firewall so our roving personnel can go to a client > > > site, boot > > their > > > laptop, and connect back into the office with Messenger for > > chat/advice > > > etc. > > > > > > Anybody have this working? I've read about the polling and fixed > port > > > delivery, and am working my way through the XP and Messenger and > > Firewall > > > stuff, but it appears that I need some help. > > > Specifically - does this/will this work or am I spinning my wheels? > > > What is the client side config to point it to an exchange based IM > > server > > > that is not inside the current IP scope? > > > > > > My boss awaits with bated breath. I'd like to know also :) > > > > > > TIA > > > > > > John Weber > > > Consultant > > > Centerlogic > > > 503-262-0490 x203 > > > > > > > > > List Charter and FAQ at: > > > http://www.sunbelt-software.com/exchange_list_charter.htm > > > > > > List Charter and FAQ at: > > > http://www.sunbelt-software.com/exchange_list_charter.htm > > > > > > > > > List Charter and FAQ at: > > > http://www.sunbelt-software.com/exchange_list_charter.htm > > > > > > List Charter and FAQ at: > > http://www.sunbelt-software.com/exchange_list_charter.htm > > > > > > List Charter and FAQ at: > > http://www.sunbelt-software.com/exchange_list_charter.htm > > > List Charter and FAQ at: > http://www.sunbelt-software.com/exchange_list_charter.htm > > > List Charter and FAQ at: > http://www.sunbelt-software.com/exchange_list_charter.htm > > > > List Charter and FAQ at: > http://www.sunbelt-software.com/exchange_list_charter.htm > > > List Charter and FAQ at: > http://www.sunbelt-software.com/exchange_list_charter.htm > > > > List Charter and FAQ at: > http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
