February 2014 - Core-students - mailman3.cels.anl.gov

INFO: Watch List for incident INC0012028 is now complete
by Argonne Service Desk 20 Feb '14

20 Feb '14

Date: 2014-02-20 08:21 CST Complete Time: 2014-02-20 11:49 CST Number: INC0012028 State: Complete Click here to view Incident: INC0012028 Short Description: Re: banned from the lab network Description: received from: devoid(a)anl.gov I haven't seen any blocks although I'm not sure if we're getting emails for the 140.221.64.0/22 network or not. That's the one that Ryan was running ~50 ssh session tests against. Forwarding to MCS core and CIS. On Wednesday, February 19, 2014, Ryan Aydelott <ryan.aydelott(a)gmail.com> wrote: > namby, vm's, jabber, anl.gov website - etc - I was running a few chunks > of SSH sessions spewing test results - I'm wondering if I didn't get > blocked by some IDS somewhere - who might I talk to to get removed from > this dark place as it's impossible to WFH now without network trickery (re: > tor) and I would rather not dump lab traffic through such a thing raising > our profile > > > -ryan > The incident you were added to the watch list is now complete. Thank you, CIS Service Desk 630-252-9999 option 2 2014-02-20 11:49 CST - Matthew KwiatkowskiCustomer Comments We pulled the IP this morning and are seeing what we can do with the detection algorithm with networking. Ref:MSG0048225

1 0

INFO: Watch List for incident INC0012028 is now complete
by Argonne Service Desk 20 Feb '14

20 Feb '14

Date: 2014-02-20 08:21 CST Complete Time: 2014-02-20 11:49 CST Number: INC0012028 State: Complete Click here to view Incident: INC0012028 Short Description: Re: banned from the lab network Description: received from: devoid(a)anl.gov I haven't seen any blocks although I'm not sure if we're getting emails for the 140.221.64.0/22 network or not. That's the one that Ryan was running ~50 ssh session tests against. Forwarding to MCS core and CIS. On Wednesday, February 19, 2014, Ryan Aydelott <ryan.aydelott(a)gmail.com> wrote: > namby, vm's, jabber, anl.gov website - etc - I was running a few chunks > of SSH sessions spewing test results - I'm wondering if I didn't get > blocked by some IDS somewhere - who might I talk to to get removed from > this dark place as it's impossible to WFH now without network trickery (re: > tor) and I would rather not dump lab traffic through such a thing raising > our profile > > > -ryan > The incident you were added to the watch list is now complete. Thank you, CIS Service Desk 630-252-9999 option 2 2014-02-20 11:49 CST - Matthew KwiatkowskiCustomer Comments We pulled the IP this morning and are seeing what we can do with the detection algorithm with networking. Ref:MSG0048224

1 0

INFO: Watch List for incident INC0012028 is now complete
by Argonne Service Desk 20 Feb '14

20 Feb '14

Date: 2014-02-20 08:21 CST Complete Time: 2014-02-20 11:49 CST Number: INC0012028 State: Complete Click here to view Incident: INC0012028 Short Description: Re: banned from the lab network Description: received from: devoid(a)anl.gov I haven't seen any blocks although I'm not sure if we're getting emails for the 140.221.64.0/22 network or not. That's the one that Ryan was running ~50 ssh session tests against. Forwarding to MCS core and CIS. On Wednesday, February 19, 2014, Ryan Aydelott <ryan.aydelott(a)gmail.com> wrote: > namby, vm's, jabber, anl.gov website - etc - I was running a few chunks > of SSH sessions spewing test results - I'm wondering if I didn't get > blocked by some IDS somewhere - who might I talk to to get removed from > this dark place as it's impossible to WFH now without network trickery (re: > tor) and I would rather not dump lab traffic through such a thing raising > our profile > > > -ryan > The incident you were added to the watch list is now complete. Thank you, CIS Service Desk 630-252-9999 option 2 2014-02-20 11:49 CST - Matthew KwiatkowskiCustomer Comments We pulled the IP this morning and are seeing what we can do with the detection algorithm with networking. Ref:MSG0048228

1 0

INFO: Watch List for incident INC0012028 is now complete
by Argonne Service Desk 20 Feb '14

20 Feb '14

Date: 2014-02-20 08:21 CST Complete Time: 2014-02-20 11:49 CST Number: INC0012028 State: Complete Click here to view Incident: INC0012028 Short Description: Re: banned from the lab network Description: received from: devoid(a)anl.gov I haven't seen any blocks although I'm not sure if we're getting emails for the 140.221.64.0/22 network or not. That's the one that Ryan was running ~50 ssh session tests against. Forwarding to MCS core and CIS. On Wednesday, February 19, 2014, Ryan Aydelott <ryan.aydelott(a)gmail.com> wrote: > namby, vm's, jabber, anl.gov website - etc - I was running a few chunks > of SSH sessions spewing test results - I'm wondering if I didn't get > blocked by some IDS somewhere - who might I talk to to get removed from > this dark place as it's impossible to WFH now without network trickery (re: > tor) and I would rather not dump lab traffic through such a thing raising > our profile > > > -ryan > The incident you were added to the watch list is now complete. Thank you, CIS Service Desk 630-252-9999 option 2 2014-02-20 11:49 CST - Matthew KwiatkowskiCustomer Comments We pulled the IP this morning and are seeing what we can do with the detection algorithm with networking. Ref:MSG0048226

1 0

Re: banned from the lab network
by Scott Devoid 20 Feb '14

20 Feb '14

I haven't seen any blocks although I'm not sure if we're getting emails for the 140.221.64.0/22 network or not. That's the one that Ryan was running ~50 ssh session tests against. Forwarding to MCS core and CIS. On Wednesday, February 19, 2014, Ryan Aydelott <ryan.aydelott(a)gmail.com> wrote: > namby, vm’s, jabber, anl.gov website - etc - I was running a few chunks > of SSH sessions spewing test results - I’m wondering if I didn’t get > blocked by some IDS somewhere - who might I talk to to get removed from > this dark place as it’s impossible to WFH now without network trickery (re: > tor) and I would rather not dump lab traffic through such a thing raising > our profile > > > -ryan >

4 7

Slow moving
by Tina Stanton-Piersanti 20 Feb '14

20 Feb '14

Just dropped off Vin and going to take my chances on 55. I know that is moving slow. Happy Thursday! Sent from my iPhone

1 0

INFO: Watch List for incident INC0012028
by Argonne Service Desk 20 Feb '14

20 Feb '14

When replying to this notification, this line and everything below it will be ignored. Place comments above this line. Date: 2014-02-20 08:21 CST Number: INC0012028 State: Open Click here to view Incident: INC0012028 Short Description: Re: banned from the lab network Description: received from: devoid(a)anl.gov I haven't seen any blocks although I'm not sure if we're getting emails for the 140.221.64.0/22 network or not. That's the one that Ryan was running ~50 ssh session tests against. Forwarding to MCS core and CIS. On Wednesday, February 19, 2014, Ryan Aydelott <ryan.aydelott(a)gmail.com> wrote: > namby, vm's, jabber, anl.gov website - etc - I was running a few chunks > of SSH sessions spewing test results - I'm wondering if I didn't get > blocked by some IDS somewhere - who might I talk to to get removed from > this dark place as it's impossible to WFH now without network trickery (re: > tor) and I would rather not dump lab traffic through such a thing raising > our profile > > > -ryan > You have been added to the watch list for this incident. The incident has been received and will be assigned to a member of our technical staff momentarily. If you have additional information that may help us in resolving this incident, please reply to this message, and your comments will be added to the ticket. If you would like to speak to someone please contact the CIS Service Desk and refer to incident INC0012028. Thank you, CIS Service Desk 630-252-9999 option 2 Ref:MSG0047919

1 0

FW: Default addresses
by Stacey, Craig J. 19 Feb '14

19 Feb '14

FYI -- Craig > -----Original Message----- > From: Zaluzec, Christiaan N. > Sent: Wednesday, February 19, 2014 5:36 PM > To: Stacey, Craig J. > Subject: Re: Default addresses > > I bet I know what happened here. I made a change to the default email > address policies which effect newly created MCS mailboxes, per our > discussion a few weeks ago to default them to ANL.gov addresses. > > This was not supposed to affect existing mailboxes, but it must have. > > The MCS addresses are still valid, but the default was probably changed. > > I'll work on a remedy tonight. I think I may be able to devise a fix. > > > > Thanks, > Christiaan Zaluzec > > > On Feb 19, 2014, at 4:08 PM, "Stacey, Craig J." <stace(a)anl.gov> wrote: > > > > I have a disturbingly high number of people who seem to have had their > default address changed to @anl.gov without their requesting it. Did > something happen? A recent example is hunter(a)anl.gov. > > > > -- > > Craig > >

1 0

Stacey, Craig J. sent you a file on Box
by Stacey, Craig J. 18 Feb '14

18 Feb '14

Stacey, Craig J. (stace(a)anl.gov) has sent you a file: Jared JohnsonApplication.pdf View File "I'm not saying I can for sure make this happen, but if I could, would we have projects that would be appropriate for this student if I can get one? I kinda feel like we would, but I want to make sure we have the time to devote to that." © 2013 About Box • Privacy Policy • Edit Notification Settings 4440 El Camino Real, Los Altos, CA 94022 Sent from the Argonne National Laboratory Box.Net Instance

1 0

Where's JohnR?
by Roberts, John E. 17 Feb '14

17 Feb '14

Sorry for the late notice. Need to take care of some odds and ends tomorrow. Please put me down for a vacation day. I'll be around-ish if needed. -John

1 0