Remote Desktop - Is it a reboot fix?

[AA]

We’ve RDP issues with Win2K3 Boxes. Some times it works and some times it’s
simply not. When I try to connect RDP after few seconds it just comes right
back with no warnings no errors

I have spent some good time but not able to find some route cause, which can
help in finding the issues.

I checked and remote access is enabled and my user is allowed.
No firewall
No issues found in event log entries
Terminal Server Manager.5.2


I don't have any error messages; all it happens is RDP freezes. And I know
this will work when we are ending up in rebooting the servers, which is just
impossible.

Please help me!

Regards.
Azeem

 

[Jeff Pitsch]

Re: Remote Desktop - Is it a reboot fix?

When it doesn't work is, is it still listening on port 3389? When you say
it comes back does the connection screen just go away? does it connect to
anything? does it pull up a blue screen at least? What service pack is on
the Win2k3 boxes? What else is on there? perhaps another remote control
software?

Jeff Pitsch
Microsoft MVP - Terminal Services


"AA" <AA@discussions.microsoft.com> wrote in message
news:E1A8FD8F-1BE0-49DD-9175-33C3954BD224@microsoft.com...
> We've RDP issues with Win2K3 Boxes. Some times it works and some times it's
> simply not. When I try to connect RDP after few seconds it just comes
> right
> back with no warnings no errors
>
> I have spent some good time but not able to find some route cause, which
> can
> help in finding the issues.
>
> I checked and remote access is enabled and my user is allowed.
> No firewall
> No issues found in event log entries
> Terminal Server Manager.5.2
>
>
> I don't have any error messages; all it happens is RDP freezes. And I know
> this will work when we are ending up in rebooting the servers, which is
> just
> impossible.
>
> Please help me!
>
> Regards.
> Azeem
>

 

[AA]

Re: Remote Desktop - Is it a reboot fix?

Thanks for your quick response

When it doesn't work is, is it still listening on port 3389?
No, its not even listening
When you say it comes back does the connection screen just go away?
-Whenever I try to connect, it just try displays connecting, no blue
screeing..... and then throws up...The client could not connect to the
remote. Remote connecting might not be enbled.....
What service pack is on the Win2k3 boxes?
SP2
What else is on there? perhaps another remote control software?
Thru console it just works fine (Damware). no issues....


Please let me know if you need any other info...
"Jeff Pitsch" wrote:

> When it doesn't work is, is it still listening on port 3389? When you say
> it comes back does the connection screen just go away? does it connect to
> anything? does it pull up a blue screen at least? What service pack is on
> the Win2k3 boxes? What else is on there? perhaps another remote control
> software?
>
> Jeff Pitsch
> Microsoft MVP - Terminal Services
>
>
> "AA" <AA@discussions.microsoft.com> wrote in message
> news:E1A8FD8F-1BE0-49DD-9175-33C3954BD224@microsoft.com...
> > We've RDP issues with Win2K3 Boxes. Some times it works and some times it's
> > simply not. When I try to connect RDP after few seconds it just comes
> > right
> > back with no warnings no errors
> >
> > I have spent some good time but not able to find some route cause, which
> > can
> > help in finding the issues.
> >
> > I checked and remote access is enabled and my user is allowed.
> > No firewall
> > No issues found in event log entries
> > Terminal Server Manager.5.2
> >
> >
> > I don't have any error messages; all it happens is RDP freezes. And I know
> > this will work when we are ending up in rebooting the servers, which is
> > just
> > impossible.
> >
> > Please help me!
> >
> > Regards.
> > Azeem
> >
>
>
>

 

[Jeff Pitsch]

Re: Remote Desktop - Is it a reboot fix?

Weird, if it's dropping the port altogether I don't know. I guess I would
start with the classic virus scans, that type of thing. I would also
possibly try replacing the NIC, testing the wire, port, that type of thing
as well.

Jeff Pitsch
Microsoft MVP - Terminal Services


"AA" <AA@discussions.microsoft.com> wrote in message
news:20BC28CF-5160-47A1-8EBA-C715A1D3EDCD@microsoft.com...
> Thanks for your quick response
>
> When it doesn't work is, is it still listening on port 3389?
> No, its not even listening
> When you say it comes back does the connection screen just go away?
> -Whenever I try to connect, it just try displays connecting, no blue
> screeing..... and then throws up...The client could not connect to the
> remote. Remote connecting might not be enbled.....
> What service pack is on the Win2k3 boxes?
> SP2
> What else is on there? perhaps another remote control software?
> Thru console it just works fine (Damware). no issues....
>
>
> Please let me know if you need any other info...
> "Jeff Pitsch" wrote:
>
>> When it doesn't work is, is it still listening on port 3389? When you
>> say
>> it comes back does the connection screen just go away? does it connect
>> to
>> anything? does it pull up a blue screen at least? What service pack is
>> on
>> the Win2k3 boxes? What else is on there? perhaps another remote control
>> software?
>>
>> Jeff Pitsch
>> Microsoft MVP - Terminal Services
>>
>>
>> "AA" <AA@discussions.microsoft.com> wrote in message
>> news:E1A8FD8F-1BE0-49DD-9175-33C3954BD224@microsoft.com...
>> > We've RDP issues with Win2K3 Boxes. Some times it works and some times
>> > it's
>> > simply not. When I try to connect RDP after few seconds it just comes
>> > right
>> > back with no warnings no errors
>> >
>> > I have spent some good time but not able to find some route cause,
>> > which
>> > can
>> > help in finding the issues.
>> >
>> > I checked and remote access is enabled and my user is allowed.
>> > No firewall
>> > No issues found in event log entries
>> > Terminal Server Manager.5.2
>> >
>> >
>> > I don't have any error messages; all it happens is RDP freezes. And I
>> > know
>> > this will work when we are ending up in rebooting the servers, which is
>> > just
>> > impossible.
>> >
>> > Please help me!
>> >
>> > Regards.
>> > Azeem
>> >
>>
>>
>>