Block Windows Live Messenger in Businesses and Education
The ports used by Windows Live Messenger 
How to block Windows Live Messenger
Easily add extra things to the blocked lists - adapt it to your needs.
TerminatorX v2 can block Windows Live Messenger.
It can also block MSN Messenger, block AIM Messenger, block Web Messengers, block LimeWire, block proxy sites and anonymous surfing, block emule, block Facebook and MySpace, Block YouTube, block chat, block gambling sites - over 450 choices now available.
Take back control of your network!
TerminatorX runs invisibly - users do not notice it operating. It sits in the background until one of the applications or web sites you selected during setup (see screenshot) is detected. Then TerminatorX removes it from the screen.
TerminatorX Monitor - free with TerminatorX - runs on a System Administrator's remote workstation and shows in real time who is beio ng blocked and from which application or web site:
Download Monitor now - free add-on to TerminatorX
TerminatorX v2 is selective - you can choose to allow, for example, MSN Messenger to be used by some users (managers or teachers) but not others (employees or students).
| Find out about school district licenses and Reduced prices available for 2 or more Site Licenses. |
Blocking Windows Live Messenger port numbers
|
Note - if you block Windows Live Messenger ports, users can switch to web messengers - block them with TerminatorX |
Many of the port listings provided on the Internet are a description of the ports that need to be opened for Windows Live Messenger to operate correctly. These, of course, can be closed to block Windows Live Messenger and MSN Messenger.
Windows Live Messenger is an updated version of MSN Messenger and uses similar ports. According to Microsoft's web site and other web sites (e.g. www.cyberphaze.net - not currently online) it seems that Windows Live Messenger uses:
Messenger server: port 1493, 1542, 1863, 1963, 80 TCP and 443 TCP
File Transfer/Sharing Folders: local: 1544 and 6891 - in fact 6720-65535 TCP from one source
Messenger Update: remote: 80 local: 1457
Remote Assistance If available): 3389 TCP & TCP/UDP 49152 – 65535
Audio: local: 1863, 443, TCP 80, 1556, 11771, 13803 and generally 5004-65535 UDP plus TCP/UDP 30000 - 65535
Remote Desktop and whiteboard: local/remote: 389, 522, 1503, 1720, and 1731
Launching Games: 80
Application sharing: TCP 1503
Video Conference: TCP 9000-9999, 5004-65535 UDP + 80
Sign-In: remote: 443 local: TCP 80, 443, 1863, 1484, 2400
Games: TCP 80, 443, 1863 and TCP/UDP 1025 - 65535
Network detection: UDP 9 and TCP/UDP 7001Note - blocking TCP port 80 will stop users accessing web sites using Internet Explorer and other browsers.
It also uses a lager variety of URLs to connect to.
Other sources
A contributor on a microsoft forum wrote that 6720 - 35000 TCP and 31000 to 31500 UDP are implicated in file sharing activities. Another correspondent gives TCP 6720 to 65535 TCP and 31000 to 31500 UDP for file transferring.
On their support site Microsoft say that you should "configure the firewall to allow for incoming traffic on UDP ports 5004 through 65535" to make sure that video calling works correctly with Windows Live Messenger and MSN Messenger. To block Windows Live Messenger video calling, of course, you should consider blocking these.
|
Blocking MSN Web Messenger's port (80) will stop Internet Explorer showing any web sites - good or bad - for all users. Relax... let TerminatorX solve your problems for you. |
