Terminal Server stops working after installing KB835732 (aka MS04-011)

Toggle sidebar Toggle sidebar
L

LiLxJohnny

Golden Member
Apr 4, 2000
1,877
0
76
After install MS04-011 as per the Microsoft Bulletin for the RPC vunerability, I noticed that upon restart, our Terminal Server does not work anymore!

I am not planning yet to reinstall the Terminal Server and I was hoping I can just restart the service but it seems that I am not allowed to do so.

Any thoughts or suggestions? This is the only patch that I installed also.

Please LMK
 
S

spyordie007

Diamond Member
May 28, 2001
6,229
0
0
AFAIK there isnt a way to easily restart the service. I dont have any suggestions off the top of my head but if it is the patch that casued the problem than call Microsoft PSS; they give free support if their patches cause issues (especially with services).

-Erik
 
L

LiLxJohnny

Golden Member
Apr 4, 2000
1,877
0
76
I did not know that, I thought I would need to pay per call/incident for support.

Know the number of chance? :)
 
S

spyordie007

Diamond Member
May 28, 2001
6,229
0
0
I *think* this page has the number(s) you would call but am not certain; if they are not the right group I would imagine they can at the least put you on the path to where you need to be:
http://support.microsoft.com/default.aspx?scid=fh;en-us;Prodoffer11a&sd=GN

I've never actually called PSS on a patch issue but I have the understanding that if you call on an issue that one of their patches cause they will waive the incident fee. If you want more details about how the free hotfix/patch issue support works I'd suggest PMing Sianath as he works @ PSS.

-Erik
 
S

Sianath

Senior member
Sep 1, 2001
437
0
0
Give us a call. There isn't any charge at all for issues related to updates... we'll get it fixed. :)
 
S

stash

Diamond Member
Jun 22, 2000
5,468
0
0
That's the number for PSS Security. You'll need to call into the main PSS phone line, and they will route you to the appropriate team. If the problem is related to TS licensing, it will go to directory services, otherwise it will go to the performance group.

The number you shoud call is (800) 936-4900
 
L

LiLxJohnny

Golden Member
Apr 4, 2000
1,877
0
76
Well to keep a long story short .. here's what I found out from my own investigation

Apparently install MS04-011 and then having Terminal Services stop working was just coincidental. As it turns out after looking at what processes were using what ports, I discovered that the store.exe (MS Exchange's Information Store) was holding on to the TCP port 3389!! That was the reason why it stopped working! ARGH!

I guess the Information Store's service takes whatever port it finds available and as such coincidentally thought 3389 was available b/c the Terminal Service did have the chance to load yet. O wells, go figure?! After shutting down the Information Store service and starting it up again, Terminal Service worked. Store.exe took up another port of its own, which I confirmed is definitely not being used by any of the other services I need.

Thanks for all your help guys!
 
S

Sianath

Senior member
Sep 1, 2001
437
0
0
You can configure the port to use in the registry for Exchange. I forget off the top of my head where it's at (been a while since I worked with Exchange) but it's there so you can get Exchange to play nicely with firewalls that are blocked on both sides.

Edit: Here it is for Exchange 5.5 (not sure if it's changed for 2000, I'll dig for a newer link later).

155831 XCCC: Setting TCP/IP Ports for Exchange and Outlook Client Connections
http://support.microsoft.com/?id=155831
 
L

LiLxJohnny

Golden Member
Apr 4, 2000
1,877
0
76
Originally posted by: Sianath
You can configure the port to use in the registry for Exchange. I forget off the top of my head where it's at (been a while since I worked with Exchange) but it's there so you can get Exchange to play nicely with firewalls that are blocked on both sides.

Edit: Here it is for Exchange 5.5 (not sure if it's changed for 2000, I'll dig for a newer link later).

155831 XCCC: Setting TCP/IP Ports for Exchange and Outlook Client Connections
http://support.microsoft.com/?id=155831
Click to expand...

Should also be true for Exchange 2k no? I'll have to check the registry and see .. thanks for the heads up. I also know of another workaround for this issue.

You can modify the registry and locate the Information Store Service and add in it that the dependency for this service being TermServices. Once you do that, the Information Store will not start up until TermServices starts up.

What do you guys think?
 
You must log in or register to reply here.

TRENDING THREADS

COMPANY
RESOURCES
FOLLOW
Top Bottom