hidden hit counter
Help!

Remote Desktop could not connect

 
Post new topic   General Reply to Topic (not reply to a specific post)    Forums Home -> Work Remotely RSS
Next:  Remote Desktop - Local Printers and Drives  
Author Message
KDrop
External


Since: Mar 15, 2006
Posts: 10



PostPosted: Mon Dec 11, 2006 9:14 pm    Post subject: Remote Desktop could not connect
Archived from groups: microsoft>public>windowsxp>work_remotely (more info?)

I have windows XP pro on my desktop and lap top I use at home. I recently
moved office space and am no longer able to connect to my desktop. It wasn't
a problem before. At first I thought my port 3389 was closed but had my IT
guy make sure it is open. I grabbed the new IP address and made sure both
computers were configured to allow remote desktop connection. when trying to
sign in using this new IP address, I keep getting the error :
"The client could not connect to the remote computer.

Remote connections might not be enabled or the computer may be too busyto
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."

Any ideas? I poured through these threads and am pretty sure I have
everything configured correctly.


--
Thanks

Ken
Back to top
KDrop
External


Since: Mar 15, 2006
Posts: 10



PostPosted: Tue Dec 12, 2006 1:37 pm    Post subject: Re: Remote Desktop could not connect [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Robert,

No I couldn't. So that probably means there is an issue with my port being
blocked right? My error read: "Could not open connection to the host, on
port 3389: connect failed"
--
Thanks

Ken


"Robert L [MVP - Networking]" wrote:

> Can you telnet port 3389? Or this search result may help,
>
> The client could not connect to the remote computerSymptom: When trying to access TS/RDC, you may receive this error: The client could not connect to the remote computer. Remote connection might not be ...
> www.chicagotech.net/remoteissues/rdc2.htm
>
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "KDrop" wrote in message
> I have windows XP pro on my desktop and lap top I use at home. I recently
> moved office space and am no longer able to connect to my desktop. It wasn't
> a problem before. At first I thought my port 3389 was closed but had my IT
> guy make sure it is open. I grabbed the new IP address and made sure both
> computers were configured to allow remote desktop connection. when trying to
> sign in using this new IP address, I keep getting the error :
> "The client could not connect to the remote computer.
>
> Remote connections might not be enabled or the computer may be too busyto
> 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."
>
> Any ideas? I poured through these threads and am pretty sure I have
> everything configured correctly.
>
>
> --
> Thanks
>
> Ken
Back to top
KDrop
External


Since: Mar 15, 2006
Posts: 10



PostPosted: Tue Dec 12, 2006 1:58 pm    Post subject: Re: Remote Desktop could not connect [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Also, I don't have MacAfee as that article stated as a possiblity for my
error...
--
Thanks

Ken


"KDrop" wrote:

> Robert,
>
> No I couldn't. So that probably means there is an issue with my port being
> blocked right? My error read: "Could not open connection to the host, on
> port 3389: connect failed"
> --
> Thanks
>
> Ken
>
>
> "Robert L [MVP - Networking]" wrote:
>
> > Can you telnet port 3389? Or this search result may help,
> >
> > The client could not connect to the remote computerSymptom: When trying to access TS/RDC, you may receive this error: The client could not connect to the remote computer. Remote connection might not be ...
> > www.chicagotech.net/remoteissues/rdc2.htm
> >
> >
> > Bob Lin, MS-MVP, MCSE & CNE
> > Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> > How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> > "KDrop" wrote in message
> > I have windows XP pro on my desktop and lap top I use at home. I recently
> > moved office space and am no longer able to connect to my desktop. It wasn't
> > a problem before. At first I thought my port 3389 was closed but had my IT
> > guy make sure it is open. I grabbed the new IP address and made sure both
> > computers were configured to allow remote desktop connection. when trying to
> > sign in using this new IP address, I keep getting the error :
> > "The client could not connect to the remote computer.
> >
> > Remote connections might not be enabled or the computer may be too busyto
> > 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."
> >
> > Any ideas? I poured through these threads and am pretty sure I have
> > everything configured correctly.
> >
> >
> > --
> > Thanks
> >
> > Ken
Back to top
KDrop
External


Since: Mar 15, 2006
Posts: 10



PostPosted: Tue Dec 12, 2006 4:37 pm    Post subject: Re: Remote Desktop could not connect [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Yes, that is what it said so the RDC must be enabled. Still stuck on this...
--
Thanks

Ken


"Robert L [MVP - Networking]" wrote:

> Make sure the RDC is enabled. Quoted from http://www.chicagotech.net/forum1.htm
>
> "At the command prompt, type qwinsta. If the RDP-TCP listener is running, you receive the following output:
> rdp-tcp 65536 Listen rdpwd"
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "KDrop" wrote in message
> Also, I don't have MacAfee as that article stated as a possiblity for my
> error...
> --
> Thanks
>
> Ken
>
>
> "KDrop" wrote:
>
> > Robert,
> >
> > No I couldn't. So that probably means there is an issue with my port being
> > blocked right? My error read: "Could not open connection to the host, on
> > port 3389: connect failed"
> > --
> > Thanks
> >
> > Ken
> >
> >
> > "Robert L [MVP - Networking]" wrote:
> >
> > > Can you telnet port 3389? Or this search result may help,
> > >
> > > The client could not connect to the remote computerSymptom: When trying to access TS/RDC, you may receive this error: The client could not connect to the remote computer. Remote connection might not be ...
> > > www.chicagotech.net/remoteissues/rdc2.htm
> > >
> > >
> > > Bob Lin, MS-MVP, MCSE & CNE
> > > Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> > > How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> > > "KDrop" wrote in message
> > > I have windows XP pro on my desktop and lap top I use at home. I recently
> > > moved office space and am no longer able to connect to my desktop. It wasn't
> > > a problem before. At first I thought my port 3389 was closed but had my IT
> > > guy make sure it is open. I grabbed the new IP address and made sure both
> > > computers were configured to allow remote desktop connection. when trying to
> > > sign in using this new IP address, I keep getting the error :
> > > "The client could not connect to the remote computer.
> > >
> > > Remote connections might not be enabled or the computer may be too busyto
> > > 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."
> > >
> > > Any ideas? I poured through these threads and am pretty sure I have
> > > everything configured correctly.
> > >
> > >
> > > --
> > > Thanks
> > >
> > > Ken
Back to top
Display posts from previous:   
Post new topic   General Reply to Topic (not reply to a specific post)    Forums Home -> Work Remotely All times are: Eastern Time (US & Canada)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum