I'm attempting to RDC to another WinXP Pro computer in my domain/network.
I've entered the name, the FQDN, the IP address and all i get back is the msg:

"The client could not establish a connection to the remote computer.

The most likely causes for this error are:
1) Remote connections might not be enabled on the remote computer.
2) The maximum number of connections was exceeded at the remote computer.
3) A network error occured while establishing the connection."

I've configured the connection setup on the remote computer as instructions
show, and from my computer I'm able to RDC into my company's Win2K3 Servers
with no difficulty. Any ideas to point me in the right direction?

Case Matrix thought carefully and wrote on 11/19/2005 6:57 AM:
> I'm attempting to RDC to another WinXP Pro computer in my domain/network.
> I've entered the name, the FQDN, the IP address and all i get back is the msg:
>
> "The client could not establish a connection to the remote computer.
>
> The most likely causes for this error are:
> 1) Remote connections might not be enabled on the remote computer.
> 2) The maximum number of connections was exceeded at the remote computer.
> 3) A network error occured while establishing the connection."
>
> I've configured the connection setup on the remote computer as instructions
> show, and from my computer I'm able to RDC into my company's Win2K3 Servers
> with no difficulty. Any ideas to point me in the right direction?
>

If you've eliminated causes 1, 2 & 3, then another likely cause is a
firewall blocking TCP port 3389.

Lance
*****

A majority of ports are blocked at the firewall, however, this connection
isn't passing through the firewall. And if the port were blocked then why
would I be able to access Win2K3 Servers and not a WinXP Pro desktop.

"Lance" wrote:

>
>
> Case Matrix thought carefully and wrote on 11/19/2005 6:57 AM:
> > I'm attempting to RDC to another WinXP Pro computer in my domain/network.
> > I've entered the name, the FQDN, the IP address and all i get back is the msg:
> >
> > "The client could not establish a connection to the remote computer.
> >
> > The most likely causes for this error are:
> > 1) Remote connections might not be enabled on the remote computer.
> > 2) The maximum number of connections was exceeded at the remote computer.
> > 3) A network error occured while establishing the connection."
> >
> > I've configured the connection setup on the remote computer as instructions
> > show, and from my computer I'm able to RDC into my company's Win2K3 Servers
> > with no difficulty. Any ideas to point me in the right direction?
> >
>
> If you've eliminated causes 1, 2 & 3, then another likely cause is a
> firewall blocking TCP port 3389.
>
> Lance
> *****
>

I'm thinking of the firewall installed on the WinXP Pro desktop.

Lance
*****

Case Matrix wrote on 11/19/2005 8:00 AM:
> A majority of ports are blocked at the firewall, however, this connection
> isn't passing through the firewall. And if the port were blocked then why
> would I be able to access Win2K3 Servers and not a WinXP Pro desktop.
>
> "Lance" wrote:
>
>
>>
>>Case Matrix thought carefully and wrote on 11/19/2005 6:57 AM:
>>
>>>I'm attempting to RDC to another WinXP Pro computer in my domain/network.
>>>I've entered the name, the FQDN, the IP address and all i get back is the msg:
>>>
>>>"The client could not establish a connection to the remote computer.
>>>
>>>The most likely causes for this error are:
>>>1) Remote connections might not be enabled on the remote computer.
>>>2) The maximum number of connections was exceeded at the remote computer.
>>>3) A network error occured while establishing the connection."
>>>
>>>I've configured the connection setup on the remote computer as instructions
>>>show, and from my computer I'm able to RDC into my company's Win2K3 Servers
>>>with no difficulty. Any ideas to point me in the right direction?
>>>
>>
>>If you've eliminated causes 1, 2 & 3, then another likely cause is a
>>firewall blocking TCP port 3389.
>>
>>Lance
>>*****
>>

There are no local firewalls setup on each machine.

"Lance" wrote:

> I'm thinking of the firewall installed on the WinXP Pro desktop.
>
> Lance
> *****
>
> Case Matrix wrote on 11/19/2005 8:00 AM:
> > A majority of ports are blocked at the firewall, however, this connection
> > isn't passing through the firewall. And if the port were blocked then why
> > would I be able to access Win2K3 Servers and not a WinXP Pro desktop.
> >
> > "Lance" wrote:
> >
> >
> >>
> >>Case Matrix thought carefully and wrote on 11/19/2005 6:57 AM:
> >>
> >>>I'm attempting to RDC to another WinXP Pro computer in my domain/network.
> >>>I've entered the name, the FQDN, the IP address and all i get back is the msg:
> >>>
> >>>"The client could not establish a connection to the remote computer.
> >>>
> >>>The most likely causes for this error are:
> >>>1) Remote connections might not be enabled on the remote computer.
> >>>2) The maximum number of connections was exceeded at the remote computer.
> >>>3) A network error occured while establishing the connection."
> >>>
> >>>I've configured the connection setup on the remote computer as instructions
> >>>show, and from my computer I'm able to RDC into my company's Win2K3 Servers
> >>>with no difficulty. Any ideas to point me in the right direction?
> >>>
> >>
> >>If you've eliminated causes 1, 2 & 3, then another likely cause is a
> >>firewall blocking TCP port 3389.
> >>
> >>Lance
> >>*****
> >>
>

Is the XP Pro box your trying to access running NAV 2005 worm protection?
That causes issues like this. Also there are reports the new MS OneCare Live
Beta also causes issues. Lastly see this page for troubleshooting help...

http://theillustratednetwork.mvps.or...eshooting.html

--

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...

"Case Matrix" <CaseMatrix@discussions.microsoft.com> wrote in message
news98BED06-C964-4E9D-90F4-A077C24207A1@microsoft.com...
> There are no local firewalls setup on each machine.
>
> "Lance" wrote:
>
>> I'm thinking of the firewall installed on the WinXP Pro desktop.
>>
>> Lance
>> *****
>>
>> Case Matrix wrote on 11/19/2005 8:00 AM:
>> > A majority of ports are blocked at the firewall, however, this
>> > connection
>> > isn't passing through the firewall. And if the port were blocked then
>> > why
>> > would I be able to access Win2K3 Servers and not a WinXP Pro desktop.
>> >
>> > "Lance" wrote:
>> >
>> >
>> >>
>> >>Case Matrix thought carefully and wrote on 11/19/2005 6:57 AM:
>> >>
>> >>>I'm attempting to RDC to another WinXP Pro computer in my
>> >>>domain/network.
>> >>>I've entered the name, the FQDN, the IP address and all i get back is
>> >>>the msg:
>> >>>
>> >>>"The client could not establish a connection to the remote computer.
>> >>>
>> >>>The most likely causes for this error are:
>> >>>1) Remote connections might not be enabled on the remote computer.
>> >>>2) The maximum number of connections was exceeded at the remote
>> >>>computer.
>> >>>3) A network error occured while establishing the connection."
>> >>>
>> >>>I've configured the connection setup on the remote computer as
>> >>>instructions
>> >>>show, and from my computer I'm able to RDC into my company's Win2K3
>> >>>Servers
>> >>>with no difficulty. Any ideas to point me in the right direction?
>> >>>
>> >>
>> >>If you've eliminated causes 1, 2 & 3, then another likely cause is a
>> >>firewall blocking TCP port 3389.
>> >>
>> >>Lance
>> >>*****
>> >>
>>