RDP issue after reboot 2003 server

[Fab]

Hi all,
i've a strange behavior in some servers with 2003 R2 Sp2. I know that other
guys have same issue but nobody received a right reply.
In few words after reboot, Terminal Server services start normally but 3389
port is not open. After a second reboot 3389 port is open and then i can
connect to server via RDP. After the third reboot 3389 is closed and after
another reboot is newly open and so on....
Browsing many web sites i see that this behavior start in March 2008 but it
doesn't seems originated by sp2 installation. I've many server with sp2 and
at the moment only two have the issue.

Any ideas?
Many thanks in advanced.

 

[Fab]

RE: RDP issue after reboot 2003 server

News about issue. After first reboot i wait for about 15 minutes and 3389
port is open. No action to server (no logon at console, restart of service
and so on).

It seems that service hung on starting or a large timeout ( 9000 seconds ?)


"Fab" wrote:

> Hi all,
> i've a strange behavior in some servers with 2003 R2 Sp2. I know that other
> guys have same issue but nobody received a right reply.
> In few words after reboot, Terminal Server services start normally but 3389
> port is not open. After a second reboot 3389 port is open and then i can
> connect to server via RDP. After the third reboot 3389 is closed and after
> another reboot is newly open and so on....
> Browsing many web sites i see that this behavior start in March 2008 but it
> doesn't seems originated by sp2 installation. I've many server with sp2 and
> at the moment only two have the issue.
>
> Any ideas?
> Many thanks in advanced.
>
>

 

[Chris Ferraro]

RE: RDP issue after reboot 2003 server

I have this problem and opened a phone case with Microsoft. The guy I got
was not very smart so it was useless.

"Fab" wrote:

> News about issue. After first reboot i wait for about 15 minutes and 3389
> port is open. No action to server (no logon at console, restart of service
> and so on).
>
> It seems that service hung on starting or a large timeout ( 9000 seconds ?)
>
>
> "Fab" wrote:
>
> > Hi all,
> > i've a strange behavior in some servers with 2003 R2 Sp2. I know that other
> > guys have same issue but nobody received a right reply.
> > In few words after reboot, Terminal Server services start normally but 3389
> > port is not open. After a second reboot 3389 port is open and then i can
> > connect to server via RDP. After the third reboot 3389 is closed and after
> > another reboot is newly open and so on....
> > Browsing many web sites i see that this behavior start in March 2008 but it
> > doesn't seems originated by sp2 installation. I've many server with sp2 and
> > at the moment only two have the issue.
> >
> > Any ideas?
> > Many thanks in advanced.
> >
> >

 

[Chris Ferraro]

RE: RDP issue after reboot 2003 server

Actully, my issue is not exactly the same but sounds somewhat similar.
Regardless, I started a new post about it.

"Fab" wrote:

> News about issue. After first reboot i wait for about 15 minutes and 3389
> port is open. No action to server (no logon at console, restart of service
> and so on).
>
> It seems that service hung on starting or a large timeout ( 9000 seconds ?)
>
>
> "Fab" wrote:
>
> > Hi all,
> > i've a strange behavior in some servers with 2003 R2 Sp2. I know that other
> > guys have same issue but nobody received a right reply.
> > In few words after reboot, Terminal Server services start normally but 3389
> > port is not open. After a second reboot 3389 port is open and then i can
> > connect to server via RDP. After the third reboot 3389 is closed and after
> > another reboot is newly open and so on....
> > Browsing many web sites i see that this behavior start in March 2008 but it
> > doesn't seems originated by sp2 installation. I've many server with sp2 and
> > at the moment only two have the issue.
> >
> > Any ideas?
> > Many thanks in advanced.
> >
> >

 

[Fab]

RE: RDP issue after reboot 2003 server

Other my servers have same behavior. I confirm no link to SP2 install. I
suppose issue is related to a MS patch released in june 08.

"Chris Ferraro" wrote:

> Actully, my issue is not exactly the same but sounds somewhat similar.
> Regardless, I started a new post about it.
>
> "Fab" wrote:
>
> > News about issue. After first reboot i wait for about 15 minutes and 3389
> > port is open. No action to server (no logon at console, restart of service
> > and so on).
> >
> > It seems that service hung on starting or a large timeout ( 9000 seconds ?)
> >
> >
> > "Fab" wrote:
> >
> > > Hi all,
> > > i've a strange behavior in some servers with 2003 R2 Sp2. I know that other
> > > guys have same issue but nobody received a right reply.
> > > In few words after reboot, Terminal Server services start normally but 3389
> > > port is not open. After a second reboot 3389 port is open and then i can
> > > connect to server via RDP. After the third reboot 3389 is closed and after
> > > another reboot is newly open and so on....
> > > Browsing many web sites i see that this behavior start in March 2008 but it
> > > doesn't seems originated by sp2 installation. I've many server with sp2 and
> > > at the moment only two have the issue.
> > >
> > > Any ideas?
> > > Many thanks in advanced.
> > >
> > >