Windows Live Messenger connectivity issue

The idea of putting strict limitations to internet access (applications as
well as browser surf) took me to the step of limiting web access for
Microsoft applications alongside with other software that utilize update
features or use web-based elements as a part of interface/functionality.

So I'd like to ask if there's any available information on Microsoft
'offical IP address range', in other words and to be more precise - what is
the range of IP addresses Windows Live Messenger may connect to in order to
pass authorization and make use of all the features (including file transfer
and voice/video communication)? Being familiar with the protocol used by
Windows Live Messenger when connecting to its services, I'd also like to
restrict its access to the specific address range. I've already tried the
following known so far (as suggested in several threads found), but these are
not sufficient:

207.46.0.0 - 207.46.255.255
212.73.0.0 - 212.73.255.255
213.19.0.0 - 213.19.255.255


If anyone knows the IP addresses ranges sufficient for Windows Live
Messenger to utilize all its features, please reply.
Thanks in advance

Pyz wrote:
> So I'd like to ask if there's any available information on Microsoft
> 'offical IP address range', in other words and to be more precise - what is
> the range of IP addresses Windows Live Messenger may connect to in order to
> pass authorization and make use of all the features (including file transfer
> and voice/video communication)?

I have proof that WLM passes video/audio through my corporation's
intranet, so it is using IP addresses on our private network, which
pretty much dooms your effort to restrict what it can connect to.

Put another way, some of the traffic passes directly between the two
systems communicating, so you'd have to white-list the IP address of
every person you intended to communicate with.

--
Steve Swift
http://www.swiftys.org.uk/swifty.html
http://www.ringers.org.uk

Corporate communication based on WLM is not what I was aiming at. Initial
intention was to get the addresses ranges WLM utilizes to communicate via and
update its components from.

Anyway, thanks for the reply
I'll try to modify my question in another section