From: Lynchburg, VA
We too are experiencing this issue. I have an email dialogue open with MSN, but thus far have been told to update my version of MSN Messenger to the latest build, check my IE security settings, etc. Will keep everyone informed if I hear anything back that might be of value to the list. I have stressed repeatedly to MSN that this issue seems to be affecting ISA and firewall users only. I can connect with no problem outside my network, via dialup, without a firewall.
I haven't been affected by the issue because we don't allow IM'er to the Internet on any of your networks for security reasons.
However, this is a problem that a lot of people have been reporting. I don't know what's causing it, but it may be an authentication issue.
Configure the clients as Firewall clients. Since Messenger only runs on Windows OS's that support the Firewall client, this should not be a problem. Then configure the HTTP Redirector to forward requests directly to the server on the Internet. Make sure the Messengers are not configured to use the Web Proxy service. Some versions of Messenger ignore this setting and use spyware methods to detect and use the Web Proxy settings on the browser. I've mentioned this before and I think its very poor form for the Messenger to grab the browser settings even when you've explicitly configured it to not use a Web Proxy.
In an absolutelly weird manner our MSN Messengers started to work fine again. I only told users to close it from the tray icon and start session again. Everyone is connecting fine right now and no more 'could not deliver' messagees at all. Will MS pay to all of us our psycho's bill? Cheers, Alvin
I've still haven't figured out what is causing this problem; but surelly it started when some clientes insttalled the new rellease 5.0. Everything was working fine before so. I guess the problem is co-existence of some 4.x and 5.0 behind the same ISA server as it seems to treat them in a different manner; 5.0 tries to use http proxy as pointed before but 4.x doesn't unless connections settings state so; it doesn't sound reasonably at all.. but i've just experienced that. I'm afraid i have no time enough for 'lab testings' at work, but it should be interesting to put same version in all clients with same firewall client version (someone can have installed wspclnt from MSPxy2.0) and check that everything will work fine that way. Cheers, Alvaro.
Another observation: sometimes i'm chatting fine with a colleague in US, and when trying to talk to someone in Europe i lose some packets with the one in Europe; it makes me wonder if the problem is in MSN server's pool communications. Web page .NET status doesn't show any problem with the service... Cheers, Alvin
quote:Originally posted by AdminISA: Oh my GOD, and i'm banging my head since morning into my isa server . This is silly, i even removed all my definitions/protocol rules, thinking that i may have done something silly into it .
Can anybody have the reason for this. On Saturday we did got connected, but the connections were very erratic. But today, we just couldn't and everybody in my office was cursing me .
What is the way out.
Is anybody using Yahoo messenger, I'm unable to connect Yahoo messenger also behind ISA server. I have tried all settings in yahoo, with/without proxy/direct connection/ etc. HTTP redirector with behind firewall option as well as direct to web also. but nothing worked, even opened its favourite 5050 port in protocols, MSP client is installed on my machine and no default gateway is defined in network properties. What could be the reason.
[Hi Ajmal - We've had mixed success with Yahoo messenger behind the firewall. Yahoo customer services says: In order to use Yahoo Chat's webcam feature, your firewall must permit outgoing TCP connections to webcam.yahoo.com on port 5100. If you use a proxy server to conect to the Internet, you will not be able to use the webcam feature.
So... currently we have text messaging enabled and working. Webcam and voice do NOT work. I would appreciate any advice I can get on how to enable these as they say. Thanks and good luck!
From: Athens Texas USA
I have the offical response from microsoft on this issue. MSN Messenger 5.0 upon installation highjacks all messenger traffic. When you have an allow rule for domains msn could not do a reverse lookup, so they have created the reverse look up zones that allow this now. They did tell me that msn messenger was not supported by them. windows messenger 4.7 is what everyone should be running.
hi i have never got this problem i have been using Isa Server for 6 months . well i donno why u guys r using securenat for msn messenger . why don't u use socks 4 for it. i have been using this i i have'nt heard an error about this on my network!