Windows Messenger 5.0 on a LAN enviroment

[Mark Stanley]

I am having a problem with Windows Messenger 5.0 on a LAN
enviroment,

Currently using a Windows XP Professional machine with
Windows
Messenger 5 installed and connecting to an Exchange 2000
IM
environment, I can send messages to other contacts but
unable to
receive them. The user sending the message gets the
standard message
of unable to deilver.

I have tried logging in on another machine and my
accounts works fine,
I have no IP port filtering enabled nor no Personal
Firewalls
installed.

Regards

Mark

 

[Jonathan Kay [MVP]]

Greetings Mark,

I know you said that no personal firewalls were installed, but what about the built-in
Internet Connection Firewall in Windows XP? What you're describing is a known problem with
the ICF on and Exchange Server 2000 IM connections. To check, click Start, then click the
Control Panel. If you're in category view
click Network and Internet connections then click Network Connections. Right click your
network/internet connection, then click Properties. Click the Advanced Tab, and verify that
the Internet Connection Firewall is unchecked.
____________________________________________
Jonathan Kay
Microsoft MVP - Windows Messenger/MSN Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com

 

[Mark Stanley]

Jonathan

Thanks for the quick responce, the XP ICF is disabled on
the machine.

Is there any way to debug the traffic ?

Regards

Mark

-----Original Message-----
Greetings Mark,

I know you said that no personal firewalls were

installed, but what about the built-in

Internet Connection Firewall in Windows XP? What you're

describing is a known problem with

the ICF on and Exchange Server 2000 IM connections. To

check, click Start, then click the

Control Panel. If you're in category view
click Network and Internet connections then click

Network Connections. Right click your

network/internet connection, then click Properties.

Click the Advanced Tab, and verify that

 

[Guest]

In the advanced proxy settings try adding *.domain.local (where domain.local is ur domain name) in the exception list.

might work

Jp