Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)
Hi,
I can connect from computer A to computer B, but not viceversa.
The error is:
"The Cliente could not connect to the remote computer
Romete connections might not be enabled or the computer might be too busy to
accept new connections.
It is also possible that networl problems are preventing your connection"
I think I've tried everything:
-Checked the Remote Desktop checkbox in Remote tab.
-Checked for Terminal Services running on both comps.
-Did netstat -an and port 3389 is listening on both.
-I work in a Workgroup, and connect by cablemodem to the Internet, IPs are
dynamic. Both are in the same workgroup.
-Disabled guest user (don't even know why).
-Restarted each comp a lot of times.
-Both answer to PINGs and can see each other in My Network Places.
-Logged on both from Adminitrative users with passwords.
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)
Make sure the new XP SP2 Windows Firewall is not enabled on PCA or that it
is configured to allow Remote Desktop access through TCP Port 3389.
--
Al Jarvi (MS-MVP Windows Networking)
Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com This posting is provided "AS IS" with no warranties, and confers no
rights...
"Gustavo" <die@spam.die> wrote in message
news:eB2rWTBhFHA.328@tk2msftngp13.phx.gbl...
> Hi,
> I can connect from computer A to computer B, but not viceversa.
>
> The error is:
>
> "The Cliente could not connect to the remote computer
> Romete connections might not be enabled or the computer might be too busy
> to accept new connections.
> It is also possible that networl problems are preventing your connection"
>
> I think I've tried everything:
> -Checked the Remote Desktop checkbox in Remote tab.
> -Checked for Terminal Services running on both comps.
> -Did netstat -an and port 3389 is listening on both.
> -I work in a Workgroup, and connect by cablemodem to the Internet, IPs are
> dynamic. Both are in the same workgroup.
> -Disabled guest user (don't even know why).
> -Restarted each comp a lot of times.
> -Both answer to PINGs and can see each other in My Network Places.
> -Logged on both from Adminitrative users with passwords.
>
> What else could I try to see if it works?
>
> Thanks for any help,
> Gustavo de la Espriella
>
>
>
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)
Yes, both firewalls are disabled. Still can't connect :-/
Gustavo
"Sooner Al [MVP]" <SoonerAl@somewhere.net.invalid> wrote in message
news:enns2hHhFHA.1052@TK2MSFTNGP10.phx.gbl...
> Make sure the new XP SP2 Windows Firewall is not enabled on PCA or that it
> is configured to allow Remote Desktop access through TCP Port 3389.
>
> --
>
> Al Jarvi (MS-MVP Windows Networking)
>
> Please post *ALL* questions and replies to the news group for the mutual
> benefit of all of us...
> The MS-MVP Program - http://mvp.support.microsoft.com > This posting is provided "AS IS" with no warranties, and confers no
> rights...
>
>
> "Gustavo" <die@spam.die> wrote in message
> news:eB2rWTBhFHA.328@tk2msftngp13.phx.gbl...
>> Hi,
>> I can connect from computer A to computer B, but not viceversa.
>>
>> The error is:
>>
>> "The Cliente could not connect to the remote computer
>> Romete connections might not be enabled or the computer might be too busy
>> to accept new connections.
>> It is also possible that networl problems are preventing your connection"
>>
>> I think I've tried everything:
>> -Checked the Remote Desktop checkbox in Remote tab.
>> -Checked for Terminal Services running on both comps.
>> -Did netstat -an and port 3389 is listening on both.
>> -I work in a Workgroup, and connect by cablemodem to the Internet, IPs
>> are dynamic. Both are in the same workgroup.
>> -Disabled guest user (don't even know why).
>> -Restarted each comp a lot of times.
>> -Both answer to PINGs and can see each other in My Network Places.
>> -Logged on both from Adminitrative users with passwords.
>>
>> What else could I try to see if it works?
>>
>> Thanks for any help,
>> Gustavo de la Espriella
>>
>>
>>
>
>
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)
Try telnet computerb 3389
Do you get a connection (i.e., blank screen) or does it time out?
---
Jeffrey Randow (Windows Networking MVP)
jeffreyr-support@remotenetworktechnology.com
http://www.networkblog.net (My Networking Blog)
http://www.remotenetworktechnology.com (Support Site)
On Sat, 9 Jul 2005 11:50:23 -0600, "Gustavo" <die@spam.die> wrote:
>Yes, both firewalls are disabled. Still can't connect :-/
>Gustavo
>
>"Sooner Al [MVP]" <SoonerAl@somewhere.net.invalid> wrote in message
>news:enns2hHhFHA.1052@TK2MSFTNGP10.phx.gbl...
>> Make sure the new XP SP2 Windows Firewall is not enabled on PCA or that it
>> is configured to allow Remote Desktop access through TCP Port 3389.
>>
>> --
>>
>> Al Jarvi (MS-MVP Windows Networking)
>>
>> Please post *ALL* questions and replies to the news group for the mutual
>> benefit of all of us...
>> The MS-MVP Program - http://mvp.support.microsoft.com >> This posting is provided "AS IS" with no warranties, and confers no
>> rights...
>>
>>
>> "Gustavo" <die@spam.die> wrote in message
>> news:eB2rWTBhFHA.328@tk2msftngp13.phx.gbl...
>>> Hi,
>>> I can connect from computer A to computer B, but not viceversa.
>>>
>>> The error is:
>>>
>>> "The Cliente could not connect to the remote computer
>>> Romete connections might not be enabled or the computer might be too busy
>>> to accept new connections.
>>> It is also possible that networl problems are preventing your connection"
>>>
>>> I think I've tried everything:
>>> -Checked the Remote Desktop checkbox in Remote tab.
>>> -Checked for Terminal Services running on both comps.
>>> -Did netstat -an and port 3389 is listening on both.
>>> -I work in a Workgroup, and connect by cablemodem to the Internet, IPs
>>> are dynamic. Both are in the same workgroup.
>>> -Disabled guest user (don't even know why).
>>> -Restarted each comp a lot of times.
>>> -Both answer to PINGs and can see each other in My Network Places.
>>> -Logged on both from Adminitrative users with passwords.
>>>
>>> What else could I try to see if it works?
>>>
>>> Thanks for any help,
>>> Gustavo de la Espriella
>>>
>>>
>>>
>>
>>
>
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)
"" wrote:
> Yes, both firewalls are disabled. Still can't connect :-/
> Gustavo
>
> "Sooner Al [MVP]" <SoonerAl@somewhere.net.invalid> wrote in
> message
> news:enns2hHhFHA.1052@TK2MSFTNGP10.phx.gbl...
> > Make sure the new XP SP2 Windows Firewall is not enabled on
> PCA or that it
> > is configured to allow Remote Desktop access through TCP
> Port 3389.
> >
> > --
> >
> > Al Jarvi (MS-MVP Windows Networking)
> >
> > Please post *ALL* questions and replies to the news group
> for the mutual
> > benefit of all of us...
> > The MS-MVP Program - http://mvp.support.microsoft.com > > This posting is provided "AS IS" with no warranties, and
> confers no
> > rights...
> >
> >
> > "Gustavo" <die@spam.die> wrote in message
> > news:eB2rWTBhFHA.328@tk2msftngp13.phx.gbl...
> >> Hi,
> >> I can connect from computer A to computer B, but not
> viceversa.
> >>
> >> The error is:
> >>
> >> "The Cliente could not connect to the remote computer
> >> Romete connections might not be enabled or the computer
> might be too busy
> >> to accept new connections.
> >> It is also possible that networl problems are preventing
> your connection"
> >>
> >> I think I've tried everything:
> >> -Checked the Remote Desktop checkbox in Remote tab.
> >> -Checked for Terminal Services running on both comps.
> >> -Did netstat -an and port 3389 is listening on both.
> >> -I work in a Workgroup, and connect by cablemodem to the
> Internet, IPs
> >> are dynamic. Both are in the same workgroup.
> >> -Disabled guest user (don't even know why).
> >> -Restarted each comp a lot of times.
> >> -Both answer to PINGs and can see each other in My Network
> Places.
> >> -Logged on both from Adminitrative users with passwords.
> >>
> >> What else could I try to see if it works?
> >>
> >> Thanks for any help,
> >> Gustavo de la Espriella
> >>
> >>
> >>
> >
> >
You should try using ip address insted of computer name, and make sure
that "Remote Access Auto Connection Manager" is enabled (service),
in saying this i have three windows PC’s (xp pro X2 and win 2k) and
FreeBSD with samaba server, and hat service is disabled on all the
windows machies yet it works very well.
On 10 Jul 2005 15:39:10 -0400, Sparda
<UseLinkToEmail@WindowsForumz.com> wrote:
>"" wrote:
> > Yes, both firewalls are disabled. Still can't connect :-/
> > Gustavo
> >
> > "Sooner Al [MVP]" <SoonerAl@somewhere.net.invalid> wrote in
> > message
> > news:enns2hHhFHA.1052@TK2MSFTNGP10.phx.gbl...
> > > Make sure the new XP SP2 Windows Firewall is not enabled on
> > PCA or that it
> > > is configured to allow Remote Desktop access through TCP
> > Port 3389.
> > >
> > > --
> > >
> > > Al Jarvi (MS-MVP Windows Networking)
> > >
> > > Please post *ALL* questions and replies to the news group
> > for the mutual
> > > benefit of all of us...
> > > The MS-MVP Program - http://mvp.support.microsoft.com > > > This posting is provided "AS IS" with no warranties, and
> > confers no
> > > rights...
> > >
> > >
> > > "Gustavo" <die@spam.die> wrote in message
> > > news:eB2rWTBhFHA.328@tk2msftngp13.phx.gbl...
> > >> Hi,
> > >> I can connect from computer A to computer B, but not
> > viceversa.
> > >>
> > >> The error is:
> > >>
> > >> "The Cliente could not connect to the remote computer
> > >> Romete connections might not be enabled or the computer
> > might be too busy
> > >> to accept new connections.
> > >> It is also possible that networl problems are preventing
> > your connection"
> > >>
> > >> I think I've tried everything:
> > >> -Checked the Remote Desktop checkbox in Remote tab.
> > >> -Checked for Terminal Services running on both comps.
> > >> -Did netstat -an and port 3389 is listening on both.
> > >> -I work in a Workgroup, and connect by cablemodem to the
> > Internet, IPs
> > >> are dynamic. Both are in the same workgroup.
> > >> -Disabled guest user (don't even know why).
> > >> -Restarted each comp a lot of times.
> > >> -Both answer to PINGs and can see each other in My Network
> > Places.
> > >> -Logged on both from Adminitrative users with passwords.
> > >>
> > >> What else could I try to see if it works?
> > >>
> > >> Thanks for any help,
> > >> Gustavo de la Espriella
> > >>
> > >>
> > >>
> > >
> > >
>
>You should try using ip address insted of computer name, and make sure
>that "Remote Access Auto Connection Manager" is enabled (service),
>in saying this i have three windows PC's (xp pro X2 and win 2k) and
>FreeBSD with samaba server, and hat service is disabled on all the
>windows machies yet it works very well.
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)
Tried telnet ("TELNET MyRemoteCompName 3389" ) on both computers, both
failed("Connect failed" ), but I still connect 1 way with remote desktop.
I have tried using IP, and it gives the same error.
In the meantime ive been using the "Beyond Remote Server/Client" Freeware,
which actually works pretty good. But I would really like to know why my
remote desktop doesnt work both ways, and would prefer to be using remote
desktop instead of third party freeware.
Thanks,
Gustavo
"Jeffrey Randow (MVP)" <jeffreyr-support@remotenetworktechnology.com> wrote
in message news:g7a3d1lrjlcrbtp2fu07mva943daj0kb2m@4ax.com...
> Did you try the "telnet" command?
> ---
> Jeffrey Randow (Windows Networking MVP)
> jeffreyr-support@remotenetworktechnology.com
> http://www.networkblog.net (My Networking Blog)
> http://www.remotenetworktechnology.com (Support Site)
>
> On 10 Jul 2005 15:39:10 -0400, Sparda
> <UseLinkToEmail@WindowsForumz.com> wrote:
>
>>"" wrote:
>> > Yes, both firewalls are disabled. Still can't connect :-/
>> > Gustavo
>> >
>> > "Sooner Al [MVP]" <SoonerAl@somewhere.net.invalid> wrote in
>> > message
>> > news:enns2hHhFHA.1052@TK2MSFTNGP10.phx.gbl...
>> > > Make sure the new XP SP2 Windows Firewall is not enabled on
>> > PCA or that it
>> > > is configured to allow Remote Desktop access through TCP
>> > Port 3389.
>> > >
>> > > --
>> > >
>> > > Al Jarvi (MS-MVP Windows Networking)
>> > >
>> > > Please post *ALL* questions and replies to the news group
>> > for the mutual
>> > > benefit of all of us...
>> > > The MS-MVP Program - http://mvp.support.microsoft.com >> > > This posting is provided "AS IS" with no warranties, and
>> > confers no
>> > > rights...
>> > >
>> > >
>> > > "Gustavo" <die@spam.die> wrote in message
>> > > news:eB2rWTBhFHA.328@tk2msftngp13.phx.gbl...
>> > >> Hi,
>> > >> I can connect from computer A to computer B, but not
>> > viceversa.
>> > >>
>> > >> The error is:
>> > >>
>> > >> "The Cliente could not connect to the remote computer
>> > >> Romete connections might not be enabled or the computer
>> > might be too busy
>> > >> to accept new connections.
>> > >> It is also possible that networl problems are preventing
>> > your connection"
>> > >>
>> > >> I think I've tried everything:
>> > >> -Checked the Remote Desktop checkbox in Remote tab.
>> > >> -Checked for Terminal Services running on both comps.
>> > >> -Did netstat -an and port 3389 is listening on both.
>> > >> -I work in a Workgroup, and connect by cablemodem to the
>> > Internet, IPs
>> > >> are dynamic. Both are in the same workgroup.
>> > >> -Disabled guest user (don't even know why).
>> > >> -Restarted each comp a lot of times.
>> > >> -Both answer to PINGs and can see each other in My Network
>> > Places.
>> > >> -Logged on both from Adminitrative users with passwords.
>> > >>
>> > >> What else could I try to see if it works?
>> > >>
>> > >> Thanks for any help,
>> > >> Gustavo de la Espriella
>> > >>
>> > >>
>> > >>
>> > >
>> > >
>>
>>You should try using ip address insted of computer name, and make sure
>>that "Remote Access Auto Connection Manager" is enabled (service),
>>in saying this i have three windows PC's (xp pro X2 and win 2k) and
>>FreeBSD with samaba server, and hat service is disabled on all the
>>windows machies yet it works very well.
>
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.