Windows NT Can't login after reboot - Windows 2003 server

  • Thread starter Thread starter Eduardo
  • Start date Start date
E

Eduardo

Hi guys.

I had a problem with our Windows 2003 Server.

We were working using Remote Desktop to reboot the server.
After reboot, some of servers couldn't login to Terminal Service.

I trayed to telnet selecting port number, but couldin't connect it.(NG using
netstat -n)
There were any message about terminal service on event viewer.

So, we decided to reboot again, using HP-iLO.
After that, server tuned on and terminal service worked again.

What is going on this server?
What is the problem?
Only way to fix it is reboot?
I looked around google, but I coundn't find any problem like mine
 
TS does not shut down the port on reboot. If it happens again, you can check
if the firewall is blocking the 3389 traffic.

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Eduardo" <Eduardo@discussions.microsoft.com> wrote in message
news:62535222-85C9-4F98-939C-ABE256E6562E@microsoft.com...
> Hi guys.
>
> I had a problem with our Windows 2003 Server.
>
> We were working using Remote Desktop to reboot the server.
> After reboot, some of servers couldn't login to Terminal Service.
>
> I trayed to telnet selecting port number, but couldin't connect it.(NG
> using
> netstat -n)
> There were any message about terminal service on event viewer.
>
> So, we decided to reboot again, using HP-iLO.
> After that, server tuned on and terminal service worked again.
>
> What is going on this server?
> What is the problem?
> Only way to fix it is reboot?
> I looked around google, but I coundn't find any problem like mine
 
Ok,
Next time I'll check it, and will report.

Thanks
--
Always Shutdown works on Windows!


"Jiazhi Ou [MSFT]" wrote:

> TS does not shut down the port on reboot. If it happens again, you can check
> if the firewall is blocking the 3389 traffic.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Eduardo" <Eduardo@discussions.microsoft.com> wrote in message
> news:62535222-85C9-4F98-939C-ABE256E6562E@microsoft.com...
> > Hi guys.
> >
> > I had a problem with our Windows 2003 Server.
> >
> > We were working using Remote Desktop to reboot the server.
> > After reboot, some of servers couldn't login to Terminal Service.
> >
> > I trayed to telnet selecting port number, but couldin't connect it.(NG
> > using
> > netstat -n)
> > There were any message about terminal service on event viewer.
> >
> > So, we decided to reboot again, using HP-iLO.
> > After that, server tuned on and terminal service worked again.
> >
> > What is going on this server?
> > What is the problem?
> > Only way to fix it is reboot?
> > I looked around google, but I coundn't find any problem like mine
>
>
 
Back
Top