Heads up...

[vortex.livejournal.com]

Just so you know, for those of you who use Remote Desktop...one or more of the 4 most recent Windows XP Security updates will prevent Remote Desktop from working.

I was remoted in to my home computers, did the updates, then couldn't connect back to them.

Drove home, tried to connect pc to pc using Remote Desktop and couldn't.
Un-installed those updates, and tested again...success!
Drove back to where I am and am now connected in again...

p.s.
I believe one of the updates was an IE Security update, the others were System Security updates...

Comments

[nem0.livejournal.com]

Is it just XP updates, or does it also affect Server 2003? Wondering, because I JUST installed this week's updates, and I'm headed out of town tomorrow, and might need to remote in to fix things while I'm in the road.

[vortex.livejournal.com]

I don't know, I am only working with XP at the moment.

Best bet is to try to remote in to your server before you leave and if you can't connect to it, then yes, that's the problem. I had to un-install the updates(4 of them) and re-boot to get it to work again.

Also might affect Terminal Server...

[nem0.livejournal.com]

Woo, appears 2003 is unaffected.

Good thing, too, because if anything else went wrong with this round of updates, I may have thrown the damn thing off the fire escape.

[vortex.livejournal.com]

HAHAHAHA!

I know how you feel!

A good friend of mine would chime in at this moment to say something like "Windows Sucks, BSD all-the-way!"...

[nem0.livejournal.com]

Don't I wish. All our software runs on Windows machines, and has run on Windows since the dawn of computers, so I'm reluctant to uproot everyone because it takes me an extra couple of hours to massage SBS into working like it should.

(Yeah, we could probably get away with a nice open-source OS on the server, but I think one or more of the license services for the CAD stuff would throw a hissy fit. Bleh.)

[rorted.livejournal.com]

At first glance, I appropriately misread this post as "Woo, appears 2003 is uninfected."

[vortex.livejournal.com]

Ha Ha!

It's late (at least it is where I am)...I can understand!...

[rorted.livejournal.com]

It's 4pm here, I can't really pull that as an excuse.

Might have something to do with me just finish cleaining up a virus outbreak. Now everywhere I look I see INFECTION!

[vortex.livejournal.com]

HaHa!

That could be it!

It's 2am here and I'm settling down with some Nacho chips with Jalapeno Cheddar dip and a Rum and coke (or two)...have a good evening!...

[barkman.livejournal.com]

On which machine did you update? becuase my home machine has them, and my work machine doesn't and i can still connect normally.

[vortex.livejournal.com]

I have three machines at home with XP SP2 and all of the latest updates (now excluding the 4 most recent IE and System Security updates)...

[vortex.livejournal.com]

p.s.
It might just be a specific problem with my machines since they have been around a while, with various software and such.

I haven't had a chance to figure out the specifics yet.

Just posting in case anyone else ran into it...

[major-error.livejournal.com]

That would seem to me to be more likely.

I ran the updates earlier this week, and haven't had any problems.

[bamatone.livejournal.com]

Same here. (Whew.)

[vortex.livejournal.com]

Absolutely Quite Possible :p...

[valiskeogh.livejournal.com]

thank god we dont install updates.

... well i do... but we have a WSUS that's supposed to be administered and maintained and is theoretically supposed to be delivering updates, but i've never seen it happen.

[vortex.livejournal.com]

Heh...so what yo u are saying is that your place of work in un-secured as it relates to all of the windows bugs?...

[valiskeogh.livejournal.com]

pretty much!

but hey, wtf do i know, i'm just a tech.

[vortex.livejournal.com]

ROFL!

...and that's just another reason why I love you!...