Remote Destop (for administration)

[Guest apaquette]

I am supporting a company with 6 Windows 2003 servers in the domain. I can

remote into 5 of OK. The 6th server is the issue. "Remote Desktop" is enabled

on the System Properties/Remote screen. On Network

Connections/Properties/Advanced/Firewall Settings/Advanced, under both

Services and Exceptions Remote Desktop in enabled for TCP 3389. Portqry shows

TCP 3389 (ms-wbt-service) LISTENING, UDP 3389 (unknown service) NOT

LISTENING. However, when I attempt to remote connect, even from it's own

client, it cannot connect.

 

Any suggestions on how to make this work?

Thanks

[Guest Soo Kuan Teo [MSFT]]

Re: Remote Destop (for administration)

 

what is the exact error you received?

what is the output when you run the following cmd locally?

qwinsta.exe

 

 

--

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

 

"apaquette" <apaquette@discussions.microsoft.com> wrote in message

news:93A827B5-83BE-45A6-AAE1-719C65E27B9E@microsoft.com...

>I am supporting a company with 6 Windows 2003 servers in the domain. I can

> remote into 5 of OK. The 6th server is the issue. "Remote Desktop" is

> enabled

> on the System Properties/Remote screen. On Network

> Connections/Properties/Advanced/Firewall Settings/Advanced, under both

> Services and Exceptions Remote Desktop in enabled for TCP 3389. Portqry

> shows

> TCP 3389 (ms-wbt-service) LISTENING, UDP 3389 (unknown service) NOT

> LISTENING. However, when I attempt to remote connect, even from it's own

> client, it cannot connect.

>

> Any suggestions on how to make this work?

> Thanks

>

[Guest apaquette]

Re: Remote Destop (for administration)

 

Wen I attempt to connect from the servers' Remote Desttop Connection client,

the error is:

"This computer can't connect to the remote computer.

Try connecting again. If the problem continues, contact the owner of the

remote computer or your network administrator."

 

The output from qwinsta.exe is:

Sessionname Username ID State Type Device

console 0 conn wdcon

rdp-tcp 65536 listen rdpwd

 

"Soo Kuan Teo [MSFT]" wrote:

> what is the exact error you received?

> what is the output when you run the following cmd locally?

> qwinsta.exe

>

>

> --

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

>

> "apaquette" <apaquette@discussions.microsoft.com> wrote in message

> news:93A827B5-83BE-45A6-AAE1-719C65E27B9E@microsoft.com...

> >I am supporting a company with 6 Windows 2003 servers in the domain. I can

> > remote into 5 of OK. The 6th server is the issue. "Remote Desktop" is

> > enabled

> > on the System Properties/Remote screen. On Network

> > Connections/Properties/Advanced/Firewall Settings/Advanced, under both

> > Services and Exceptions Remote Desktop in enabled for TCP 3389. Portqry

> > shows

> > TCP 3389 (ms-wbt-service) LISTENING, UDP 3389 (unknown service) NOT

> > LISTENING. However, when I attempt to remote connect, even from it's own

> > client, it cannot connect.

> >

> > Any suggestions on how to make this work?

> > Thanks

> >

>

>

[Guest Jeff Pitsch]

Re: Remote Destop (for administration)

 

Have you tried disabling remote desktop, hit OK/apply, reenable remote

desktop? I've come across situations like this where that works.

 

Jeff Pitsch

Microsoft MVP - Terminal Services

 

 

"apaquette" <apaquette@discussions.microsoft.com> wrote in message

news:B945F510-31CB-48D9-A8A3-BF8A8C50033E@microsoft.com...

> Wen I attempt to connect from the servers' Remote Desttop Connection

> client,

> the error is:

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

> Try connecting again. If the problem continues, contact the owner of the

> remote computer or your network administrator."

>

> The output from qwinsta.exe is:

> Sessionname Username ID State Type Device

> console 0 conn wdcon

> rdp-tcp 65536 listen rdpwd

>

> "Soo Kuan Teo [MSFT]" wrote:

>

>> what is the exact error you received?

>> what is the output when you run the following cmd locally?

>> qwinsta.exe

>>

>>

>> --

>> This posting is provided "AS IS" with no warranties, and confers no

>> rights.

>>

>> "apaquette" <apaquette@discussions.microsoft.com> wrote in message

>> news:93A827B5-83BE-45A6-AAE1-719C65E27B9E@microsoft.com...

>> >I am supporting a company with 6 Windows 2003 servers in the domain. I

>> >can

>> > remote into 5 of OK. The 6th server is the issue. "Remote Desktop" is

>> > enabled

>> > on the System Properties/Remote screen. On Network

>> > Connections/Properties/Advanced/Firewall Settings/Advanced, under both

>> > Services and Exceptions Remote Desktop in enabled for TCP 3389. Portqry

>> > shows

>> > TCP 3389 (ms-wbt-service) LISTENING, UDP 3389 (unknown service) NOT

>> > LISTENING. However, when I attempt to remote connect, even from it's

>> > own

>> > client, it cannot connect.

>> >

>> > Any suggestions on how to make this work?

>> > Thanks

>> >

>>

>>

[Guest Soo Kuan Teo [MSFT]]

Re: Remote Destop (for administration)

 

Can you please try if the following help?

http://forums.technet.microsoft.com/en/winserverTS/thread/da00a036-207f-43fb-838b-536db79468fe/

 

 

--

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

 

"apaquette" <apaquette@discussions.microsoft.com> wrote in message

news:93A827B5-83BE-45A6-AAE1-719C65E27B9E@microsoft.com...

>I am supporting a company with 6 Windows 2003 servers in the domain. I can

> remote into 5 of OK. The 6th server is the issue. "Remote Desktop" is

> enabled

> on the System Properties/Remote screen. On Network

> Connections/Properties/Advanced/Firewall Settings/Advanced, under both

> Services and Exceptions Remote Desktop in enabled for TCP 3389. Portqry

> shows

> TCP 3389 (ms-wbt-service) LISTENING, UDP 3389 (unknown service) NOT

> LISTENING. However, when I attempt to remote connect, even from it's own

> client, it cannot connect.

>

> Any suggestions on how to make this work?

> Thanks

>

[Guest apaquette]

Re: Remote Destop (for administration)

 

Looking at this posting,

the Windows firewall is OFF,

running RDP v5.2, as are my other servers that I can remote into,

portqry tells me it is "listening" on TCP 3389,

I am attempting to log in as the administrator, and my client computers

easily remotes to several other servers

on the client, it is set for "Always connect, even if authentication fails",

I am using IPv4 addresses,

IPSEC is running, but it is also running on several servers that remote

connection works OK,

I am still looking to see why the "Allow users to connect remotely" is

"checked" but "greyed out",

Routing and Remote Accessed is disabled,

<hostname>:3389 doesn't help,

under terminal services configuration, RDP connection is enabled and the nic

is selected,

the server is running server 2003R2

I have about 30 servers in 10 separate domains (forests), and this is the

only one that I cannot remote into (all from the same client computer)

 

Still a puzzle....

 

 

"Soo Kuan Teo [MSFT]" wrote:

> Can you please try if the following help?

> http://forums.technet.microsoft.com/en/winserverTS/thread/da00a036-207f-43fb-838b-536db79468fe/

>

>

> --

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

>

> "apaquette" <apaquette@discussions.microsoft.com> wrote in message

> news:93A827B5-83BE-45A6-AAE1-719C65E27B9E@microsoft.com...

> >I am supporting a company with 6 Windows 2003 servers in the domain. I can

> > remote into 5 of OK. The 6th server is the issue. "Remote Desktop" is

> > enabled

> > on the System Properties/Remote screen. On Network

> > Connections/Properties/Advanced/Firewall Settings/Advanced, under both

> > Services and Exceptions Remote Desktop in enabled for TCP 3389. Portqry

> > shows

> > TCP 3389 (ms-wbt-service) LISTENING, UDP 3389 (unknown service) NOT

> > LISTENING. However, when I attempt to remote connect, even from it's own

> > client, it cannot connect.

> >

> > Any suggestions on how to make this work?

> > Thanks

> >

>

>