>>thought it might be something like that, thanks... any real purpose for
>>those specific ports? (looking it up it's supposed to be DNS auxiliary
[quoted text clipped - 5 lines]
>
> You might have to block ports all the way up to 1030, or 1032.
Rick,
The kids use Instant Messaging which is not the same as the Windows
Messenger Service and uses a different set of ports (Yahoo 5050, AIM 5190
MSN 1863).

Signature
Mike Maltby
mike.maltby@gmail.com
>>> thought it might be something like that, thanks... any real purpose
>>> for those specific ports? (looking it up it's supposed to be DNS
[quoted text clipped - 13 lines]
>
> Rick
>>>thought it might be something like that, thanks... any real purpose for
>>>those specific ports? (looking it up it's supposed to be DNS auxiliary
[quoted text clipped - 12 lines]
>
> Rick
There are three "Messengers", thanks to MSFT choosing to use a confusing
nomenclature.
Windows Messenger Service:
Only available with Windows 2K, Windows XP, and, maybe, Windows NT (very
old OS). Used by Windows network administrators for distributing notices to
system users. Uses port 135, and the lowest of the ephemeral ports
(beginning with port 1025). UDP packets. Also used by spammers, and RPC
worms, to try to reach users with unprotected systems on Internet
connection. Completely unrelated to any of the instant message services;
certainly can't access, or be accessed by, IM servers.
Windows Messenger 4.7(?):
Only available with Windows XP. Necessary for remote desktop sharing, or
whatever that application is. Can access, and be accessed by the MSN
Messenger servers.
MSN Messenger 7.0 (latest version):
Standalone IM product that runs under all versions of Windows except
Windows 95.
Restricting the functionality of the Windows Messenger Service will not
affect the use of the MSN Messenger service.
I expect some MVP will now clarify any errors I have made...

Signature
Norman
~Win dain a lotica, En vai tu ri, Si lo ta
~Fin dein a loluca, En dragu a sei lain
~Vi fa-ru les shutai am, En riga-lint
Rick T - 15 Jul 2005 17:36 GMT
ahh, I knew that (though not in that detail)...
blocked 1026&1027 since that's all I see; will this also block the first
couple Internet requests from when I boot up ?
Rick
>>>>thought it might be something like that, thanks... any real purpose for
>>>>those specific ports? (looking it up it's supposed to be DNS auxiliary
[quoted text clipped - 41 lines]
>
> I expect some MVP will now clarify any errors I have made...