The OSU Computer Helpdesk and other IT support groups at Oregon State have received numerous reports of a FRAUDULENT e-mail message with the following subject delivered to OSU e-mail addresses: ”Attention: Account user.”
This fraudulent message is a targeted phishing attempt designed to deceive you into providing your username, password and e-mail information to deceitful individuals. Information Services is working to block the source of this message.
Actions you can take:
- Delete the message from your mailbox.
- Do NOT respond to the message. This informs the spammer that your email address is real.
- If you have already responded to the e-mail, please CHANGE your ONID password immediately.
- Call the OSU Computer Helpdesk for assistance at 541-737-3474, Monday through Friday.
Phishing emails can have many subject lines. Please remember that any e-mail that asks you to provide your username and password is ALWAYS fraudulent.
Additionally, any e-mail that uses fear tactics (suspension, disabling your account, account infected) and requires you to provide username, password, etc. are ALWAYS fraudulent.
For more information about these kinds of phishing attempts, and for methods to report phishing, please visit http://oregonstate.edu/helpdocs/safety-and-security/computer-viruses-fraud/e-mail-fraud/phishing
I rebooted one of the Lync Front End servers due to spurious latency issues. This shouldn’t have caused any client issue but my off campus Lync client reported and network disconnect outage and required a restart of the client.
Blackboard is back up.
– Lindy Foster Enterprise Computing Oregon State University 541-737-3805
OSU suffered another border router failure between 10:36 am and 10:38 am this morning. We are in the process of shutting down the faulty device and have failed all traffic over to the standby device. This should resolve the issue until the faulty hardware has been repaired.
The IS Server Support team will performing emergency maintenance on one of the Exchange servers tonight at 6pm to address remote management services issues on one of the three servers. We do not expect this maintenance to cause an outage, however users mailboxes who are associated to that server will see a two messages while their mailbox switches to the redundant server(s) and back.
Who will this affect: Mostly Transparent to customers. When will this happen: Thursday – 05-16-2013 @ 06:00PM – 6:30PM What are we doing: Rebooting the server to reset the WinRM, IIS and associated services on Why are we doing this: Troubleshooting the WinRM, and other issues related to this specific server.
If you have any questions or concerns please feel free to contact us.
Jason Appah Network Engineering/Server Support B211 Kerr Admin Bldg Oregon State University Corvallis, OR 97331 541-737-8801 Jason.email@example.com
At approx. 1:20 a.m. this morning, one of our routers rebooted. The backup router took over shortly afterward. However, there was a disruption to internet connectivity.
This morning’s incident affected all communication between OSU and the Internet for up to 15 minutes between 1:20 am and 1:35 am as well as affecting ResNet (both wired and wireless networks) from 1:20 am to 6:45 am. We do not anticipate further issues as a result of this morning’s hardware failure.
Notice of Unplanned Outage
Today starting around 10:40 am lasting until approximately 11 am our authentication servers for the OSU_Secure wireless network and Enterprise VPN lost connection with its Active Directory server. This resulted in new connections to the OSU_Secure wireless network and Enterprise VPN for staff users being denied. The outage only affected users logging in with Active Directory accounts during that that timeframe. ONID authorization and the OSU_Access wireless network were unaffected.
If you have questions or concerns about this outage, please contact Network Engineering at net (at) oregonstate.edu or call 737-HELP.
Primary Contact: Mike Akey, firstname.lastname@example.org
I will be moving some internal systems off of a network switch that needs replacement. This will result in a very brief blip in availability for the database that Maintain uses.
Cutover at: 5pm Friday 17th.
Notice of Service Interruption
We experienced a MySQL service interruption from 12:28-12:38 this afternoon.
At 12:30 MySQL failed over to the secondary server and service availability was restored. The service took approximately 8 more minutes to become fully responsive due to heavy inbound traffic.
During the failover applications connecting to the MySQL service failed resulting in a blue page (if it was a drupal site) or possibly a blank page or error page for a custom application. Once the failover was complete for the next 8 minutes applications were extremely slow in loading and customers would have noticed long page load times (5-6 seconds) on all web infrastructure that relies on the MySQL service.
This failure was caused by pushing logging configuration changes directly to the production server as opposed to the staging environment where they should have been pushed first. This is a procedural issue that will be addressed.
We apologize for the service interruption and any inconvenience it caused. If you have any questions or concerns please contact us at 7-7SIG.
——————————- Shayne Huddleston Shared Infrastructure Information Services 541.543.8996
Primary Contact: Josh Zojonc, Josh.Zojonc@oregonstate.edu
We will be bundling up three extremely minor well understood changes into a single maintenance action.
The first change will be to deny non-secure SSL renegotiation, to address the vulnerability described in RFC 5746. This will not have an impact on legitimate users, nor will they notice any changes.
The second change will be to replace the self-signed certificate used for logging into the management interface and changing the address (url) used for management. This change will only impact those that log into the netscaler to manage it. An email will be sent to those that will be affected.
The last change will to implement a fix for an asymmetric routing issue we’ve been dealing with. This will not have a noticeable impact on existing services or users. We have to make this change to allow further onboarding of services to the Netscaler.
In the event of any problems changes will be rolled back.
Communication will be done via http://blogs.oregonstate.edu/sig