Terminal Server and Windows 2003 Server RC2

[Guest dmcmahon25575]

We have several servers at a COLO that all have Windows 2003 RC2 as the OS.

All of the servers but one are accessable using Remote Desktop. The server

that is not working has the same configuration, Remote access is enabled but

I still get the error

 

This computer can't connect to the remote computer

 

This happens through the VPN as well as from any other server connected

directly to the network domain.

 

Any thoughts?????

 

Thanks,

--

David

[Guest Jeff Pitsch]

Re: Terminal Server and Windows 2003 Server RC2

 

Any errors in the event logs? Can you telnet to port 3389? Is the

remote desktop users group setup properly? Have you tried rebooting or

disabling/enabling it again?

 

Jeff Pitsch

Microsoft MVP - Terminal Server

Citrix Technology Professional

Provision Networks VIP

 

Forums not enough?

Get support from the experts at your business

http://jeffpitschconsulting.com

 

dmcmahon25575 wrote:

> We have several servers at a COLO that all have Windows 2003 RC2 as the OS.

> All of the servers but one are accessable using Remote Desktop. The server

> that is not working has the same configuration, Remote access is enabled but

> I still get the error

>

> This computer can't connect to the remote computer

>

> This happens through the VPN as well as from any other server connected

> directly to the network domain.

>

> Any thoughts?????

>

> Thanks,

[Guest Vera Noest [MVP]]

Re: Terminal Server and Windows 2003 Server RC2

 

Any warnings or errors in EventViewer on the server?

Is the server listening on port 3389? Check with "netstat -an"

(without the quotes) at a command prompt on the console of the

server.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?ZG1jbWFob24yNTU3NQ==?=

<dmcmahon25575@discussions.microsoft.com> wrote on 13 sep 2007 in

microsoft.public.windows.terminal_services:

> We have several servers at a COLO that all have Windows 2003 RC2

> as the OS. All of the servers but one are accessable using

> Remote Desktop. The server that is not working has the same

> configuration, Remote access is enabled but I still get the

> error

>

> This computer can't connect to the remote computer

>

> This happens through the VPN as well as from any other server

> connected directly to the network domain.

>

> Any thoughts?????

>

> Thanks,

[Guest dmcmahon25575]

Re: Terminal Server and Windows 2003 Server RC2

 

No event log errors

 

No, I cannot telnet to port 3389 although the server is listening on that port

 

Yes I have disabled, rebooted, enabled, Rebooted several times

--

David

 

 

"Jeff Pitsch" wrote:

> Any errors in the event logs? Can you telnet to port 3389? Is the

> remote desktop users group setup properly? Have you tried rebooting or

> disabling/enabling it again?

>

> Jeff Pitsch

> Microsoft MVP - Terminal Server

> Citrix Technology Professional

> Provision Networks VIP

>

> Forums not enough?

> Get support from the experts at your business

> http://jeffpitschconsulting.com

>

> dmcmahon25575 wrote:

> > We have several servers at a COLO that all have Windows 2003 RC2 as the OS.

> > All of the servers but one are accessable using Remote Desktop. The server

> > that is not working has the same configuration, Remote access is enabled but

> > I still get the error

> >

> > This computer can't connect to the remote computer

> >

> > This happens through the VPN as well as from any other server connected

> > directly to the network domain.

> >

> > Any thoughts?????

> >

> > Thanks,

>

[Guest dmcmahon25575]

Re: Terminal Server and Windows 2003 Server RC2

 

No warnings or errors in Event Log

 

Yes the server is listening on port 3389

--

David

 

 

"Vera Noest [MVP]" wrote:

> Any warnings or errors in EventViewer on the server?

> Is the server listening on port 3389? Check with "netstat -an"

> (without the quotes) at a command prompt on the console of the

> server.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> =?Utf-8?B?ZG1jbWFob24yNTU3NQ==?=

> <dmcmahon25575@discussions.microsoft.com> wrote on 13 sep 2007 in

> microsoft.public.windows.terminal_services:

>

> > We have several servers at a COLO that all have Windows 2003 RC2

> > as the OS. All of the servers but one are accessable using

> > Remote Desktop. The server that is not working has the same

> > configuration, Remote access is enabled but I still get the

> > error

> >

> > This computer can't connect to the remote computer

> >

> > This happens through the VPN as well as from any other server

> > connected directly to the network domain.

> >

> > Any thoughts?????

> >

> > Thanks,

>

[Guest dmcmahon25575]

Re: Terminal Server and Windows 2003 Server RC2

 

even though the server is listening on 3389 I cannot telnet into the machine

--

David

 

 

"Vera Noest [MVP]" wrote:

> Any warnings or errors in EventViewer on the server?

> Is the server listening on port 3389? Check with "netstat -an"

> (without the quotes) at a command prompt on the console of the

> server.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> =?Utf-8?B?ZG1jbWFob24yNTU3NQ==?=

> <dmcmahon25575@discussions.microsoft.com> wrote on 13 sep 2007 in

> microsoft.public.windows.terminal_services:

>

> > We have several servers at a COLO that all have Windows 2003 RC2

> > as the OS. All of the servers but one are accessable using

> > Remote Desktop. The server that is not working has the same

> > configuration, Remote access is enabled but I still get the

> > error

> >

> > This computer can't connect to the remote computer

> >

> > This happens through the VPN as well as from any other server

> > connected directly to the network domain.

> >

> > Any thoughts?????

> >

> > Thanks,

>

[Guest dmcmahon25575]

Re: Terminal Server and Windows 2003 Server RC2

 

I found the answer, the windows firewall was turned on. We do not need the

windows firewall as we are using a SonicWall so I turned it off and the

problem went away.

 

Thanks

--

David

 

 

"Jeff Pitsch" wrote:

> Any errors in the event logs? Can you telnet to port 3389? Is the

> remote desktop users group setup properly? Have you tried rebooting or

> disabling/enabling it again?

>

> Jeff Pitsch

> Microsoft MVP - Terminal Server

> Citrix Technology Professional

> Provision Networks VIP

>

> Forums not enough?

> Get support from the experts at your business

> http://jeffpitschconsulting.com

>

> dmcmahon25575 wrote:

> > We have several servers at a COLO that all have Windows 2003 RC2 as the OS.

> > All of the servers but one are accessable using Remote Desktop. The server

> > that is not working has the same configuration, Remote access is enabled but

> > I still get the error

> >

> > This computer can't connect to the remote computer

> >

> > This happens through the VPN as well as from any other server connected

> > directly to the network domain.

> >

> > Any thoughts?????

> >

> > Thanks,

>

[Guest dmcmahon25575]

Re: Terminal Server and Windows 2003 Server RC2

 

I found the answer, the windows firewall was turned on. We do not need the

windows firewall as we are using a SonicWall so I turned it off and the

problem went away.

 

Thanks

--

David

 

 

"Vera Noest [MVP]" wrote:

> Any warnings or errors in EventViewer on the server?

> Is the server listening on port 3389? Check with "netstat -an"

> (without the quotes) at a command prompt on the console of the

> server.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> =?Utf-8?B?ZG1jbWFob24yNTU3NQ==?=

> <dmcmahon25575@discussions.microsoft.com> wrote on 13 sep 2007 in

> microsoft.public.windows.terminal_services:

>

> > We have several servers at a COLO that all have Windows 2003 RC2

> > as the OS. All of the servers but one are accessable using

> > Remote Desktop. The server that is not working has the same

> > configuration, Remote access is enabled but I still get the

> > error

> >

> > This computer can't connect to the remote computer

> >

> > This happens through the VPN as well as from any other server

> > connected directly to the network domain.

> >

> > Any thoughts?????

> >

> > Thanks,

>

[Guest Vera Noest [MVP]]

Re: Terminal Server and Windows 2003 Server RC2

 

OK, I'm glad that you solved the problem, and thanks for reporting

the solution here!

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?ZG1jbWFob24yNTU3NQ==?=

<dmcmahon25575@discussions.microsoft.com> wrote on 13 sep 2007 in

microsoft.public.windows.terminal_services:

> I found the answer, the windows firewall was turned on. We do

> not need the windows firewall as we are using a SonicWall so I

> turned it off and the problem went away.

>

> Thanks