Remote desktop connection problem

I got a router setup, I definiately forwarded port 3389
correctly because I got WOL working by forwarding that
port. I can do Remote Connection from another local
computer. But I tried to connect through the public IP
and it just says, The client could not connect to the
remote computer. Remote connections might not be
enabled.... etc etc. I tried enabling DMZ on my local ip
and still doesnt work. What can be the problem guys?

I've searched through the news group and found similar postings, but none of
them has helped.

I get the following connection problem with RDC.

"The client could not connect to the remote computer.
Remote connections might not be enabled or the computer might be too busy to
accept new connections.
It is also possible that network problems are preventing your connection.
Please try connecting again later. If the problem continues to occur,
contact your administrator."

Both machines are running XP Pro. They are on different LANs. Both have
cable modems
and sit behind routers. Port forwarding of 3389 is set on both routers. RDC
is enabled on both
machines. No proxy servers. Both machines have ICF turned off. Each
machine can ping the other.
I have added the user names to Remote Desktop Users and also through
gpedit.msc (Allow logon
through Terminal Services). I have remotely logged onto the router and
checked the log status to
verify that the 3389 packets are not denied by the router. netstat -a says
that both machines are
"listening" for port 3389. I have turned off and on the RDC. PingPlotter
says that there is zero packet
loss and an average of 25ms round trip.

Just as a sanity check, I removed the routers from both ends. Still receive
the same error.

Is there anything else that I can check / do?
This has been very frustrating. Any help would be very appreciated.

TIA,

Steve

on windows xp, some times there is a firewall that is
enabled...if you right click on "my network places" make
sure that the "local area connection" settings do not have
a padlock on it. or if you have any firewalls, remove
it..do not just disable it.

also if you have pc anywhere remove it
or if you have gotomypc..remove that too..


see if that works

I have done everything according to documentation to enable remote desktop
and have verified services started against another one that does allow
remote desktop connection.

I still get the error message from trying to connect:
---------------------------
Remote Desktop Disconnected
---------------------------
The client could not connect to the remote computer.

Remote connections might not be enabled or the computer might be too busy to
accept new connections.
It is also possible that network problems are preventing your connection.

Please try connecting again later. If the problem continues to occur,
contact your administrator.
---------------------------
OK Help
---------------------------


I don't think network nor routers is a problem - I am testing from another
computer in the same LAN.
The client and the test computer host can ping each other by IP. The client
computer can connect to other RDP server hosts.
I have not changed the listening port. so mstsc /v:IP_addr should have
worked just as the mstsc /v:IP_addr:3389. None worked
In explorer form client computer, I can use access the host computer
resources by UNC name. Normally, I would enable RDP immediately after
installation of XP pro. that gave me the least problem. This time around
someone has done the initial installation and had applied every single
updates available(critical and otherwise)

Do I have to install from scratch again?

Make sure you are not running the firewall on the remote machine.

"gg" <noEmailPls@nil.net> wrote in message
news:OgcdwZ8zDHA.2412@TK2MSFTNGP10.phx.gbl...

> I have done everything according to documentation to enable remote desktop
> and have verified services started against another one that does allow
> remote desktop connection.
>
> I still get the error message from trying to connect:
> ---------------------------
> Remote Desktop Disconnected
> ---------------------------
> The client could not connect to the remote computer.
>
> Remote connections might not be enabled or the computer might be too busy

to

> accept new connections.
> It is also possible that network problems are preventing your connection.
>
> Please try connecting again later. If the problem continues to occur,
> contact your administrator.
> ---------------------------
> OK Help
> ---------------------------
>
>
> I don't think network nor routers is a problem - I am testing from another
> computer in the same LAN.
> The client and the test computer host can ping each other by IP. The

client

> computer can connect to other RDP server hosts.
> I have not changed the listening port. so mstsc /v:IP_addr should have
> worked just as the mstsc /v:IP_addr:3389. None worked
> In explorer form client computer, I can use access the host computer
> resources by UNC name. Normally, I would enable RDP immediately after
> installation of XP pro. that gave me the least problem. This time around
> someone has done the initial installation and had applied every single
> updates available(critical and otherwise)
>
> Do I have to install from scratch again?
>
>

I already checked that. The advance setting show permit all and filtering
not turned on.

I also tried from the problem host:
mstsc /v:thisPCName
and it comes back with the expected message of "The client could not
connect. Your are already connected to the console of this computer. A new
console sesion can not be established"

The actual discernible difference between the work host and the problem host
in terms of registry for terminal services were a few bytes in the security
but the GUI level for local security policy, I can't see any security
problem preventing the functioning of the RDP.
The working host belongs to a domain while the problem host is yet to join
to the domain at customer site. the problem hosts while now belongs to the
same work group as the PC used for RDP client test.

"Rich Raffenetti" <raffenetti@attbi.com> wrote in message
news:O9KoI69zDHA.1760@TK2MSFTNGP10.phx.gbl...

> Make sure you are not running the firewall on the remote machine.
>
> "gg" <noEmailPls@nil.net> wrote in message
> news:OgcdwZ8zDHA.2412@TK2MSFTNGP10.phx.gbl...

> > I have done everything according to documentation to enable remote

desktop

> > and have verified services started against another one that does allow
> > remote desktop connection.
> >
> > I still get the error message from trying to connect:
> > ---------------------------
> > Remote Desktop Disconnected
> > ---------------------------
> > The client could not connect to the remote computer.
> >
> > Remote connections might not be enabled or the computer might be too

busy

> to

> > accept new connections.
> > It is also possible that network problems are preventing your

connection.

> >
> > Please try connecting again later. If the problem continues to occur,
> > contact your administrator.
> > ---------------------------
> > OK Help
> > ---------------------------
> >
> >
> > I don't think network nor routers is a problem - I am testing from

another

> > computer in the same LAN.
> > The client and the test computer host can ping each other by IP. The

> client

> > computer can connect to other RDP server hosts.
> > I have not changed the listening port. so mstsc /v:IP_addr should have
> > worked just as the mstsc /v:IP_addr:3389. None worked
> > In explorer form client computer, I can use access the host computer
> > resources by UNC name. Normally, I would enable RDP immediately after
> > installation of XP pro. that gave me the least problem. This time

around

> > someone has done the initial installation and had applied every single
> > updates available(critical and otherwise)
> >
> > Do I have to install from scratch again?
> >
> >

>
>

I've seen this behavior too...

Try running mstsc /v:thisPCName /console...

This should help some...

Jeffrey Randow (Windows Net. & Smart Display MVP)
jeffreyr-support@remotenetworktechnology.com

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

On Wed, 31 Dec 2003 14:16:08 -0700, "gg" <noEmailPls@nil.net> wrote:

>I already checked that. The advance setting show permit all and filtering
>not turned on.
>
>I also tried from the problem host:
> mstsc /v:thisPCName
>and it comes back with the expected message of "The client could not
>connect. Your are already connected to the console of this computer. A new
>console sesion can not be established"
>
>The actual discernible difference between the work host and the problem host
>in terms of registry for terminal services were a few bytes in the security
>but the GUI level for local security policy, I can't see any security
>problem preventing the functioning of the RDP.
>The working host belongs to a domain while the problem host is yet to join
>to the domain at customer site. the problem hosts while now belongs to the
>same work group as the PC used for RDP client test.
>
>"Rich Raffenetti" <raffenetti@attbi.com> wrote in message
>news:O9KoI69zDHA.1760@TK2MSFTNGP10.phx.gbl...

>> Make sure you are not running the firewall on the remote machine.
>>
>> "gg" <noEmailPls@nil.net> wrote in message
>> news:OgcdwZ8zDHA.2412@TK2MSFTNGP10.phx.gbl...

>> > I have done everything according to documentation to enable remote

>desktop

>> > and have verified services started against another one that does allow
>> > remote desktop connection.
>> >
>> > I still get the error message from trying to connect:
>> > ---------------------------
>> > Remote Desktop Disconnected
>> > ---------------------------
>> > The client could not connect to the remote computer.
>> >
>> > Remote connections might not be enabled or the computer might be too

>busy

>> to

>> > accept new connections.
>> > It is also possible that network problems are preventing your

>connection.

>> >
>> > Please try connecting again later. If the problem continues to occur,
>> > contact your administrator.
>> > ---------------------------
>> > OK Help
>> > ---------------------------
>> >
>> >
>> > I don't think network nor routers is a problem - I am testing from

>another

>> > computer in the same LAN.
>> > The client and the test computer host can ping each other by IP. The

>> client

>> > computer can connect to other RDP server hosts.
>> > I have not changed the listening port. so mstsc /v:IP_addr should have
>> > worked just as the mstsc /v:IP_addr:3389. None worked
>> > In explorer form client computer, I can use access the host computer
>> > resources by UNC name. Normally, I would enable RDP immediately after
>> > installation of XP pro. that gave me the least problem. This time

>around

>> > someone has done the initial installation and had applied every single
>> > updates available(critical and otherwise)
>> >
>> > Do I have to install from scratch again?
>> >
>> >

>>
>>

>

thanks.

Too bad that I already reinstall.
"Jeffrey Randow (MVP)" <jeffreyr-support@remotenetworktechnology.com> wrote
in message news:2cqevvkck8k59e48heovgfca93jabkq36o@4ax.com...

> I've seen this behavior too...
>
> Try running mstsc /v:thisPCName /console...
>
> This should help some...
>
> Jeffrey Randow (Windows Net. & Smart Display MVP)
> jeffreyr-support@remotenetworktechnology.com
>
> Please post all responses to the newsgroups for the benefit
> of all USENET users. Messages sent via email may or may not
> be answered depending on time availability....
>
> Remote Networking Technology Support Site -
> http://www.remotenetworktechnology.com
> Smart Display Support - http://www.smartdisplays.net
> Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
>
> On Wed, 31 Dec 2003 14:16:08 -0700, "gg" <noEmailPls@nil.net> wrote:
>

> >I already checked that. The advance setting show permit all and filtering
> >not turned on.
> >
> >I also tried from the problem host:
> > mstsc /v:thisPCName
> >and it comes back with the expected message of "The client could not
> >connect. Your are already connected to the console of this computer. A

new

> >console sesion can not be established"
> >
> >The actual discernible difference between the work host and the problem

host

> >in terms of registry for terminal services were a few bytes in the

security

> >but the GUI level for local security policy, I can't see any security
> >problem preventing the functioning of the RDP.
> >The working host belongs to a domain while the problem host is yet to

join

> >to the domain at customer site. the problem hosts while now belongs to

the

> >same work group as the PC used for RDP client test.
> >
> >"Rich Raffenetti" <raffenetti@attbi.com> wrote in message
> >news:O9KoI69zDHA.1760@TK2MSFTNGP10.phx.gbl...

> >> Make sure you are not running the firewall on the remote machine.
> >>
> >> "gg" <noEmailPls@nil.net> wrote in message
> >> news:OgcdwZ8zDHA.2412@TK2MSFTNGP10.phx.gbl...
> >> > I have done everything according to documentation to enable remote

> >desktop

> >> > and have verified services started against another one that does

allow

> >> > remote desktop connection.
> >> >
> >> > I still get the error message from trying to connect:
> >> > ---------------------------
> >> > Remote Desktop Disconnected
> >> > ---------------------------
> >> > The client could not connect to the remote computer.
> >> >
> >> > Remote connections might not be enabled or the computer might be too

> >busy

> >> to
> >> > accept new connections.
> >> > It is also possible that network problems are preventing your

> >connection.

> >> >
> >> > Please try connecting again later. If the problem continues to occur,
> >> > contact your administrator.
> >> > ---------------------------
> >> > OK Help
> >> > ---------------------------
> >> >
> >> >
> >> > I don't think network nor routers is a problem - I am testing from

> >another

> >> > computer in the same LAN.
> >> > The client and the test computer host can ping each other by IP. The
> >> client
> >> > computer can connect to other RDP server hosts.
> >> > I have not changed the listening port. so mstsc /v:IP_addr should

have

> >> > worked just as the mstsc /v:IP_addr:3389. None worked
> >> > In explorer form client computer, I can use access the host computer
> >> > resources by UNC name. Normally, I would enable RDP immediately

after

> >> > installation of XP pro. that gave me the least problem. This time

> >around

> >> > someone has done the initial installation and had applied every

single

> >> > updates available(critical and otherwise)
> >> >
> >> > Do I have to install from scratch again?
> >> >
> >> >
> >>
> >>

> >

>