Windows Server 2003 Service Pack2

[Guest gsmith@gbmc]

Hi,

 

I installed Windows 2003 SP2 on my server. After I installed the SP2, I

could not use terminal services to get to this server. I performed numerous

steps and still could could not terminatl service to this server, however I

can get out to another box on the server. I deleted the sp2 and terminal

servies worked again. Any suggestions?

[Guest William Mann]

RE: Windows Server 2003 Service Pack2

 

Can you be more verbose on the numerous steps? Did you go to services and

check that the terminal serivces were started? did you portscan the server to

see if the port (3186, off the top of my head) was open? Did you check the

box for remote desktop? Did you go into terminal services manager, what did

that say?

 

Regards,

 

William Mann

 

"gsmith@gbmc" wrote:

> Hi,

>

> I installed Windows 2003 SP2 on my server. After I installed the SP2, I

> could not use terminal services to get to this server. I performed numerous

> steps and still could could not terminatl service to this server, however I

> can get out to another box on the server. I deleted the sp2 and terminal

> servies worked again. Any suggestions?

[Guest gsmith@gbmc]

RE: Windows Server 2003 Service Pack2

 

Yes,

I checked the services and they were started, I deleted and re-created the

rdp-tcp connection in terminal services configuration manager. I also

stopped and started the rdp connection in terminal services configuration.

I did run a command, (but I can't remember what it was) to check port 3189.

I am not that familiar with this area, but we are not blocking rdp sessions.

Once I deleted the sp2, I could perform a terminal session service to this

box.

 

"William Mann" wrote:

> Can you be more verbose on the numerous steps? Did you go to services and

> check that the terminal serivces were started? did you portscan the server to

> see if the port (3186, off the top of my head) was open? Did you check the

> box for remote desktop? Did you go into terminal services manager, what did

> that say?

>

> Regards,

>

> William Mann

>

> "gsmith@gbmc" wrote:

>

> > Hi,

> >

> > I installed Windows 2003 SP2 on my server. After I installed the SP2, I

> > could not use terminal services to get to this server. I performed numerous

> > steps and still could could not terminatl service to this server, however I

> > can get out to another box on the server. I deleted the sp2 and terminal

> > servies worked again. Any suggestions?

[Guest William Mann]

RE: Windows Server 2003 Service Pack2

 

The best way to check that the port is open is with a port-scanner, I prefer

nmap, (http://insecure.org/) as it will also tell you what else is open for

attack on the server. SP2 shouldn't affect RDP, but its possible that the

firewall might be getting enabled on install, as I seem to remember can

happen (nmap will tell you). You could also try connecting the remote

desktop from the local machine, and see if its some kind of networking fault

(for a long time I couldn't run remote desktop between our sites, even though

I could mount a smb/cifs volume...). If all else fails, try connecting with

remote desktop, and on the client and server run Wireshark, and look at the

packet information, it might just contain your answer....

 

Hope this helps,

 

William Mann

 

"gsmith@gbmc" wrote:

> Yes,

> I checked the services and they were started, I deleted and re-created the

> rdp-tcp connection in terminal services configuration manager. I also

> stopped and started the rdp connection in terminal services configuration.

> I did run a command, (but I can't remember what it was) to check port 3189.

> I am not that familiar with this area, but we are not blocking rdp sessions.

> Once I deleted the sp2, I could perform a terminal session service to this

> box.

>

> "William Mann" wrote:

>

> > Can you be more verbose on the numerous steps? Did you go to services and

> > check that the terminal serivces were started? did you portscan the server to

> > see if the port (3186, off the top of my head) was open? Did you check the

> > box for remote desktop? Did you go into terminal services manager, what did

> > that say?

> >

> > Regards,

> >

> > William Mann

> >

> > "gsmith@gbmc" wrote:

> >

> > > Hi,

> > >

> > > I installed Windows 2003 SP2 on my server. After I installed the SP2, I

> > > could not use terminal services to get to this server. I performed numerous

> > > steps and still could could not terminatl service to this server, however I

> > > can get out to another box on the server. I deleted the sp2 and terminal

> > > servies worked again. Any suggestions?

[Guest Thee Chicago Wolf]

Re: Windows Server 2003 Service Pack2

 

>I installed Windows 2003 SP2 on my server. After I installed the SP2, I

>could not use terminal services to get to this server. I performed numerous

>steps and still could could not terminatl service to this server, however I

>can get out to another box on the server. I deleted the sp2 and terminal

>servies worked again. Any suggestions?

 

Hi,

 

Here's a KB article for those folks just updating to SP2:

http://support.microsoft.com/kb/944011

 

- Thee Chicago Wolf

[Guest gsmith@gbmc]

RE: Windows Server 2003 Service Pack2

 

Let me try. Thank you.

 

"William Mann" wrote:

> The best way to check that the port is open is with a port-scanner, I prefer

> nmap, (http://insecure.org/) as it will also tell you what else is open for

> attack on the server. SP2 shouldn't affect RDP, but its possible that the

> firewall might be getting enabled on install, as I seem to remember can

> happen (nmap will tell you). You could also try connecting the remote

> desktop from the local machine, and see if its some kind of networking fault

> (for a long time I couldn't run remote desktop between our sites, even though

> I could mount a smb/cifs volume...). If all else fails, try connecting with

> remote desktop, and on the client and server run Wireshark, and look at the

> packet information, it might just contain your answer....

>

> Hope this helps,

>

> William Mann

>

> "gsmith@gbmc" wrote:

>

> > Yes,

> > I checked the services and they were started, I deleted and re-created the

> > rdp-tcp connection in terminal services configuration manager. I also

> > stopped and started the rdp connection in terminal services configuration.

> > I did run a command, (but I can't remember what it was) to check port 3189.

> > I am not that familiar with this area, but we are not blocking rdp sessions.

> > Once I deleted the sp2, I could perform a terminal session service to this

> > box.

> >

> > "William Mann" wrote:

> >

> > > Can you be more verbose on the numerous steps? Did you go to services and

> > > check that the terminal serivces were started? did you portscan the server to

> > > see if the port (3186, off the top of my head) was open? Did you check the

> > > box for remote desktop? Did you go into terminal services manager, what did

> > > that say?

> > >

> > > Regards,

> > >

> > > William Mann

> > >

> > > "gsmith@gbmc" wrote:

> > >

> > > > Hi,

> > > >

> > > > I installed Windows 2003 SP2 on my server. After I installed the SP2, I

> > > > could not use terminal services to get to this server. I performed numerous

> > > > steps and still could could not terminatl service to this server, however I

> > > > can get out to another box on the server. I deleted the sp2 and terminal

> > > > servies worked again. Any suggestions?

[Guest gsmith@gbmc]

Re: Windows Server 2003 Service Pack2

 

The knowledge base article your requested is currently not available is what

comes up when I go to that link.

 

Thanks.

 

"Thee Chicago Wolf" wrote:

> >I installed Windows 2003 SP2 on my server. After I installed the SP2, I

> >could not use terminal services to get to this server. I performed numerous

> >steps and still could could not terminatl service to this server, however I

> >can get out to another box on the server. I deleted the sp2 and terminal

> >servies worked again. Any suggestions?

>

> Hi,

>

> Here's a KB article for those folks just updating to SP2:

> http://support.microsoft.com/kb/944011

>

> - Thee Chicago Wolf

>

[Guest Thee Chicago Wolf]

Re: Windows Server 2003 Service Pack2

 

>The knowledge base article your requested is currently not available is what

>comes up when I go to that link.

 

Now that's bizarre. It was there when I posted my response. I wonder

why they yanked it.

 

- Thee Chicago Wolf

[Guest Thee Chicago Wolf]

Re: Windows Server 2003 Service Pack2

 

>The knowledge base article your requested is currently not available is what

>comes up when I go to that link.

 

Ok, here's a quick synopses of the article:

 

Title: Some problems occur after installing Windows Server 2003 SP2

 

Result: After applying Service Pack 2 on your Windows Server 2003

computer, you may experience one of more of the following symptoms:

 

1. If it is an Exchange Server, Exchange queues become clogged in the

MAPI delivery queue. Messages get stuck in this queue and cannot be

delivered.

 

2. ActiveSync may not work on the Exchange Server 2003

 

3. For the IIS server, browsing the public and/or default website in

IIS results in error "Page cannot be displayed"

 

4. Non-Pages Pool (Kernel) memory becomes exhausted

 

5. For a print server, the printing job may be partially missing

 

Cause: The problem may be the result of combining the NIC driver and

the TCP Chimney feature that comes with the Scalable Networking Pack,

which is included in Windows 2003 PS2.

 

With TCP Chimney feature, some NIC driver cause high NonPaged pool

usage.

 

Once there is less than 30MB of available paged pool memory, http.sys

starts rejecting connections.

 

Resolution: Contact the NIC manufacturer and upgrade to the NIC driver

to the latest version. If the driver does not resolve the issue, use

the workaround below.

 

Disable the TCP Chimney feature on the server using the netsh.exe

tool. Click Start, click Run, type cmd, click OK. At the prompt type

netsh.exe int ip set chimney DISABLED and press the Enter key.

 

- Thee Chicago Wolf