Using AOL or yahoo services works through the IM proxy. Switching to MSN causes the failure. Tried using no proxy, environment and http proxy settings with the same results. Client fails to connect.
Don't quite understand, which IM proxy? Or are you just talking about the HTTP proxy?
MSN won't work correctly through transparent proxy. You need to open ports for it to connect. (And mark it as an exception in the transparent proxy settings).
MSN does work through standard HTTP proxy as long as it's specified somehow to the client.
There is no dedicated IM proxy in Astaro. (Willing to be proved wrong). There is only a IM detection mechanism, for blocking/warning/allowing specific IM protocols through via pattern scanning, it doesn't proxy or allow per-se.
Sorry, my use of the terms was off. This would be through the standard http proxy, not the transparent proxy. I am able to use Yahoo and now AOL without making any additional packet filter rules. I have the default Packet Filter Rule called "Instant Messaging" which was added by the installation wizard. When I look at the services specified in that rule, all services except MSN Messenger are listed.
So was MSN messenger previously listed and now it is gone? I dont know. I do know I didn't create any of those services nor did I add them to the rule. Also, under the IM/P2P Security settings, MSN Messenger is listed as "Alert".
While I can create the MSN Service definition and add it to the IM packet filter rule, I did not have to do this in the previous version 7 release versions. Am I doing something wrong or is this indeed a bug?
Sorry, my use of the terms was off. This would be through the standard http proxy, not the transparent proxy. I am able to use Yahoo and now AOL without making any additional packet filter rules. I have the default Packet Filter Rule called "Instant Messaging" which was added by the installation wizard. When I look at the services specified in that rule, all services except MSN Messenger are listed.
So was MSN messenger previously listed and now it is gone? I dont know. I do know I didn't create any of those services nor did I add them to the rule. Also, under the IM/P2P Security settings, MSN Messenger is listed as "Alert".
While I can create the MSN Service definition and add it to the IM packet filter rule, I did not have to do this in the previous version 7 release versions. Am I doing something wrong or is this indeed a bug?
are you talking about connecting to msn or doing file transfers? I can connect to msn and send im's fine with the transparent proxy..file transfers require packet filter mods..
I've also creates a Messenger IM service definition allowing 1:65535 -> 1863 and added that to the Instant Messenging service group definition. And that is allowed in the packet filter - it was added by the install wizard. No Dice. Packet filter log shows the IM client machince trying to make a connection to MSN @ 65.54.179.216:443. And 443 is being proxied through the standard proxy (astaro device:8080).
Are you saying the Internet settings on the client PC are set to use Astaro as the http/https proxy?
Barry
Yes, the PC's Internet Explorer / FireFox is set to use the proxy. I've tried using MSN Messenger default, http and proxy settings. And yes, if I open all outgoing ports then MSN Messenger works. So the problem is not with MSN Messenger itself.
Are you saying the Internet settings on the client PC are set to use Astaro as the http/https proxy?
Barry
Yes, the PC's Internet Explorer / FireFox is set to use the proxy. I've tried using MSN Messenger default, http and proxy settings. And yes, if I open all outgoing ports then MSN Messenger works. So the problem is not with MSN Messenger itself.
