I'm putting this in UMR because it's about IT and our school... not so much for computer help.

WTF is up with IT and being unable to keep the computers usable on campus? For the last week at least, anytime I try to use any of my network drive stuff on campus computers (ready, pretty much everything, including the desktop) there is a good chance that the whole machine just grinds to a halt. Linux, windows, whatever. Unusable. It happens when I'm in the labs after 9 or so, which is about the only time I'm in the labs.

I've been sitting here for 30 minutes waiting for this particular freezeup to unfreeze so I can save and commit my changes into a repository and gtfo... but it doesn't look like that will be happening anytime soon. Even if I could save off to my flash drive I'd be fine. (I'm typing this on my laptop that I had to get out so I could get anything done while in a computer lab... the irony).

I love going to the premier technological university of Missouri, and having unusable lab machines... Does anyone else have these issues? Where stuff just hangs for a few minutes then magically comes back to life? I've had a ticket open with IT for the last week or so and they've been blaming it on some server team that only does work "off business hours", but that it should be done.

Basically I'm sick of this - I've lost about an hour of productivity at least tonight.



Logging out, logging in, logging in remotely, logging into windows... none of these get around the issue.

If anyone else is having issues with this... at all... like log in and try it even... please open a ticket with IT about it... maybe something will actually happen if there are enough tickets about it, or they'll choose to do their work at a time that students tend not to work? Or maybe I'm just an odd ball out here doing my hw after 10:00 on a wednesday

You're not alone. I can't even log into the Unix boxes in the EE building. If it's not 3 AM next time I think about it, I'll put in a ticket.

Try using symbolic links.


For Reference: http://en.wikipedia.org/wiki/Ln_(Unix)

I told IT about this. They basically said, yes, it's broken, probably not going to fix it.

None of them seemed to know that HALF (and I'm not exaggerating) of the computers in the HSS lab were not functioning at some point. I took it upon myself to report them and still some aren't perfect... dull keyboards, the login window doesn't let you type more than 5 letters in the username box... pleh. In that one it just sucks because you have to move from computer to computer while stepping over everyone else.

Yeah it pisses me off having to wait at least 5 minutes after logging into a computer in order to click a link which prompts me to to make sure I REALLY want to open that .lnk file and wait another minute for firefox to open.

They constantly lockup for ~30sec-1min at a time for me and it's a royal pain in the ass to get anything done. It's not just at night either.

My login scripts are broken now on the campus (unix) machines. Festive!

I think we should blame that stupid Microsoft DFS thing. NFS worked fine, why did you have to move to crappy MS shit?

can't access the s drives at all. This is rediculous

emergency email notification sent out at 12:03:

Also, TJ started with only five working computers in the CLC this year. I think we may be up to 10 now... Replacing or fixing them shouldn't be hard.

Also, my Linux login script was messed up as well, I sat with IT for about an hour before they could figure out the cause, and a bad way of fixing it.

I love how IT plays the blame game - no one in IT is responsible for this crash!

In all honestly, there probably isn't one person directly responsible. An update got pushed that probably caused this to happen. It may have just been that a DFS update came from M$ and one of the scripts that worked before the update cause problems.

And anyways. I think by publicly acknowledging the fault they're accepting blame. It's pretty common practice to talk to the vendor of the software when the problem is severe enough to cause unscheduled outages. It's quicker and easier usually then trying to go in blind and fix it yourself.

That would all be fine and acceptable if campus machines hadn't been acting like this for the last two weeks...

...still no s drive access so much for the one hour

+1