cannot connect with RDP...

[Guest Billingsley]

My Remote Desktop client just blinks like it tries to connect but gets

denied right away. The server is Windows 2003 Storage Server R2 and is

obviously in Remote Administration Mode. When I look at TCPView port 3389

isn't listening but when I look at netstat -an port 3389 is. I also get

strange behavoir while copying files to the server such as:

 

" Not enough server storage is available to process this command."

 

Which I know is completely wrong because I have over 900G free. I sense

there are some RPC issues but I'm not sure how to go about troubleshooting

them. Can someone give me a pointer or two?

 

TIA.

-Steven-

[Guest Vera Noest [MVP]]

Re: cannot connect with RDP...

 

The messages refers to memory rather than disk space.

 

Which EventID, Source and Description do you get in the EventLog on

the TS?

Assuming that you get EventID 2021 and 2022, check this:

 

317249 - How to troubleshoot Event ID 2021 and Event ID 2022

http://support.microsoft.com/?kbid=317249

 

177078 - Antivirus software may cause Event ID 2011

http://support.microsoft.com/?kbid=177078

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"Billingsley" <billingsley@newsgroup.nospam> wrote on 10 sep 2007

in microsoft.public.windows.terminal_services:

> My Remote Desktop client just blinks like it tries to connect

> but gets denied right away. The server is Windows 2003 Storage

> Server R2 and is obviously in Remote Administration Mode. When

> I look at TCPView port 3389 isn't listening but when I look at

> netstat -an port 3389 is. I also get strange behavoir while

> copying files to the server such as:

>

> " Not enough server storage is available to process this

> command."

>

> Which I know is completely wrong because I have over 900G free.

> I sense there are some RPC issues but I'm not sure how to go

> about troubleshooting them. Can someone give me a pointer or

> two?

>

> TIA.

> -Steven-

[Guest Billingsley]

Re: cannot connect with RDP...

 

Thank you very much for the reply. The issue is my Trend AV product. I

disabled the firewall and all problems were solved. I don't know why it

randomly decides to start blocking RDP requests but it does :S.

 

Thanks,

-Steven-

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns99A7E38365ADAveranoesthemutforsse@207.46.248.16...

> The messages refers to memory rather than disk space.

>

> Which EventID, Source and Description do you get in the EventLog on

> the TS?

> Assuming that you get EventID 2021 and 2022, check this:

>

> 317249 - How to troubleshoot Event ID 2021 and Event ID 2022

> http://support.microsoft.com/?kbid=317249

>

> 177078 - Antivirus software may cause Event ID 2011

> http://support.microsoft.com/?kbid=177078

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> "Billingsley" <billingsley@newsgroup.nospam> wrote on 10 sep 2007

> in microsoft.public.windows.terminal_services:

>

>> My Remote Desktop client just blinks like it tries to connect

>> but gets denied right away. The server is Windows 2003 Storage

>> Server R2 and is obviously in Remote Administration Mode. When

>> I look at TCPView port 3389 isn't listening but when I look at

>> netstat -an port 3389 is. I also get strange behavoir while

>> copying files to the server such as:

>>

>> " Not enough server storage is available to process this

>> command."

>>

>> Which I know is completely wrong because I have over 900G free.

>> I sense there are some RPC issues but I'm not sure how to go

>> about troubleshooting them. Can someone give me a pointer or

>> two?

>>

>> TIA.

>> -Steven-

[Guest Vera Noest [MVP]]

Re: cannot connect with RDP...

 

OK, I'm glad that your problem is solved, and thanks for reporting

the solution here, Steven!

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"Billingsley" <billingsley@newsgroup.nospam> wrote on 12 sep 2007

in microsoft.public.windows.terminal_services:

> Thank you very much for the reply. The issue is my Trend AV

> product. I disabled the firewall and all problems were solved.

> I don't know why it randomly decides to start blocking RDP

> requests but it does :S.

>

> Thanks,

> -Steven-

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

> in message

> news:Xns99A7E38365ADAveranoesthemutforsse@207.46.248.16...

>> The messages refers to memory rather than disk space.

>>

>> Which EventID, Source and Description do you get in the

>> EventLog on the TS?

>> Assuming that you get EventID 2021 and 2022, check this:

>>

>> 317249 - How to troubleshoot Event ID 2021 and Event ID 2022

>> http://support.microsoft.com/?kbid=317249

>>

>> 177078 - Antivirus software may cause Event ID 2011

>> http://support.microsoft.com/?kbid=177078

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> "Billingsley" <billingsley@newsgroup.nospam> wrote on 10 sep

>> 2007 in microsoft.public.windows.terminal_services:

>>

>>> My Remote Desktop client just blinks like it tries to connect

>>> but gets denied right away. The server is Windows 2003

>>> Storage Server R2 and is obviously in Remote Administration

>>> Mode. When I look at TCPView port 3389 isn't listening but

>>> when I look at netstat -an port 3389 is. I also get strange

>>> behavoir while copying files to the server such as:

>>>

>>> " Not enough server storage is available to process this

>>> command."

>>>

>>> Which I know is completely wrong because I have over 900G

>>> free. I sense there are some RPC issues but I'm not sure how

>>> to go about troubleshooting them. Can someone give me a

>>> pointer or two?

>>>

>>> TIA.

>>> -Steven-