RE: Re: [ActiveDir] icmp's

[Mark Parris]

This is from the Microsoft article – Enterprise logon scripts   By default, logon scripts written as either .bat or .cmd files (so-called "legacy" logon scripts) run in a visible command window; when executed, a command window open up on the screen. To prevent a user from closing the command window (and thus terminating the script), you can the Run legacy logon scripts hidden enable policy. This ensures that all legacy logon scripts run in a hidden window.   Mark   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Tom Kern Sent: 01 January 2006 14:18 To: ActiveDir@mail.activedir.org Subject: [Norton AntiSpam] Re: [ActiveDir] icmp's   I thought i read somewhere in some MS doc it being refered to as "legacy" since now you can put multiple logon scripts in GPO's and that they recommend doing it that way.   everytime a new OS or feature comes out, MS tends to refer to the previous os/feature as legacy or down-level. maybe i just made a silly assumption that using a logon script as a user attritbute( i guess somewhat simillar to the way NT did it) instead of a GPO was "legacy". thanks   On 1/1/06, Al Mulnick <[EMAIL PROTECTED]> wrote: I personally haven't heard it referred to as "legacy".  I think that may be because it wasn't a legacy method when I last heard it ;)   I haven't tested this, so your mileage may vary but: the "legacy" method would have been created and designed for a time before ICMP was the norm. As such, I wouldn't expect that to break if ICMP was disabled.  Several things will break, but I don't believe that's one of them.   Test it.  You'll know for sure then right?  Besides, I don't imagine a lot of networks out there are configured with ICMP disabled like that.    Al    On 12/31/05, Tom Kern <[EMAIL PROTECTED]> wrote: Thats it.   Isn't that the way its refered to in MS-speak?   I hope i didn't just make that up...   On 12/30/05, Brian Desmond <[EMAIL PROTECTED] > wrote: presumably setting the scriptPath attribute on accounts... Thanks, Brian Desmond [EMAIL PROTECTED] c - 312.731.3132 ________________________________ From: [EMAIL PROTECTED] on behalf of Al Mulnick Sent: Fri 12/30/2005 8:13 PM To: ActiveDir@mail.activedir.org Subject: Re: [ActiveDir] icmp's When you say legacy way, what does that mean exactly? On 12/30/05, Tom Kern < [EMAIL PROTECTED]> wrote:        would this also affect clients from getting logon scripts?        and when i say logon scripts, i mean the legacy way of distributing them, NOT thru GPO's.        Thanks again        On 12/30/05, Brian Desmond <[EMAIL PROTECTED] > wrote:                You need to enable ICMP echo source clients dest dc's, and icmp echo-reply source dc's dest clients.                The rules look something like this:                access-list DC_VLAN_OUT line 1 permit icmp any object-group domain_controllers echo                access-list DC_VLAN_IN line 1 permit icmp object-group domain_controllers any echo-reply                Have your network people considered rate-limiting ICMP packets rather than shutting them down all together. IMHO that's the correct way to handle this. Ping (echo, echo-reply) and traceroute (traceroute, time-exceeded) are necessary pieces of a network.                Thanks,                Brian Desmond                [EMAIL PROTECTED]                c - 312.731.3132                ________________________________                From: [EMAIL PROTECTED] on behalf of Tom Kern                Sent: Fri 12/30/2005 9:25 AM                To: activedirectory                Subject: [ActiveDir] icmp's                What affect would blocking icmp packets on all vlans have on win2k/xp client logons in a win2k forest?                any?                I know clients ping dc's to see which responds first and later ping dc's to determine round trip time for GPO processing, but would blocking icmp's have any adverse affects on clients?                I only ask because my corp blocks icmp's on all our vlans and i get a lot of event id 1000 from Usernev with error code of 59 which when i looked up, refers to network connectivity issues. i think this event id is related to the fact we block icmp packets and i was wondering if thats something i should worry about in a win2k network.                Thanks