Hi,
I am trying to use remote desktop connection to go from Windows 2000 at work
to a Windows Vista Business machine at home. I have set up my home router to
forward the correct ports and people are able to connect fine from other
computers (running Windows XP Pro).

Whenever I try to connect though from work using Windows 2000, it gives me
an error telling me it cannot connect or that the remote computer might be
too busy to accept connections. Except I have had people try the same
settings from other computers and they get in.

I am using RDC Client 5.1 at work on my Windows 2000 machine. The IT Help
Desk tells me it should be working (i.e. - not a firewall problem) but I
wanted to see if anyone here knew what might be wrong.

From past experience, I think I might have better luck getting a working,
timely answer here.

Thanks!
-Dan

Can you telnet home public IP port 3389?

--
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
"Dan" wrote in message
...
Hi,
I am trying to use remote desktop connection to go from Windows 2000 at
work
to a Windows Vista Business machine at home. I have set up my home router
to
forward the correct ports and people are able to connect fine from other
computers (running Windows XP Pro).

Whenever I try to connect though from work using Windows 2000, it gives me
an error telling me it cannot connect or that the remote computer might be
too busy to accept connections. Except I have had people try the same
settings from other computers and they get in.

I am using RDC Client 5.1 at work on my Windows 2000 machine. The IT Help
Desk tells me it should be working (i.e. - not a firewall problem) but I
wanted to see if anyone here knew what might be wrong.

From past experience, I think I might have better luck getting a working,
timely answer here.

Thanks!
-Dan

Hi Robert,
What do you mean by telnet? Would I test that be going to run and typing in:

"telnet [my ip address]:3389"?

-Dan


"Robert L. (MS-MVP)" wrote:

Can you telnet home public IP port 3389?

--
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
"Dan" wrote in message
...
Hi,
I am trying to use remote desktop connection to go from Windows 2000 at
work
to a Windows Vista Business machine at home. I have set up my home router
to
forward the correct ports and people are able to connect fine from other
computers (running Windows XP Pro).

Whenever I try to connect though from work using Windows 2000, it gives me
an error telling me it cannot connect or that the remote computer might be
too busy to accept connections. Except I have had people try the same
settings from other computers and they get in.

I am using RDC Client 5.1 at work on my Windows 2000 machine. The IT Help
Desk tells me it should be working (i.e. - not a firewall problem) but I
wanted to see if anyone here knew what might be wrong.

From past experience, I think I might have better luck getting a working,
timely answer here.

Thanks!
-Dan

I have also confirmed that I can connect to the computer fine through RDC if
I bring the PC physically into work and connect it to the LAN here via
ethernet.

I am using a VPN connection when it is at home. I will try on Monday to
investigate the telnet question!



"Dan" wrote:

Hi Robert,
What do you mean by telnet? Would I test that be going to run and typing in:

"telnet [my ip address]:3389"?

-Dan


"Robert L. (MS-MVP)" wrote:

Can you telnet home public IP port 3389?

--
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
"Dan" wrote in message
...
Hi,
I am trying to use remote desktop connection to go from Windows 2000 at
work
to a Windows Vista Business machine at home. I have set up my home router
to
forward the correct ports and people are able to connect fine from other
computers (running Windows XP Pro).

Whenever I try to connect though from work using Windows 2000, it gives me
an error telling me it cannot connect or that the remote computer might be
too busy to accept connections. Except I have had people try the same
settings from other computers and they get in.

I am using RDC Client 5.1 at work on my Windows 2000 machine. The IT Help
Desk tells me it should be working (i.e. - not a firewall problem) but I
wanted to see if anyone here knew what might be wrong.

From past experience, I think I might have better luck getting a working,
timely answer here.

Thanks!
-Dan

Hi Robert,

It does not appear that I can telnet to my computer or port.

I ran telnet - open - [my ip address] - got back "Could not open a
connection to host: Connect failed"

Then I tried open - [my ip address] 3389 - got back got back "Could not
open a connection to host on port 3389: Connect failed"

Does that mean it is a local firewall issue?

-Dan



"Robert L. (MS-MVP)" wrote:

Can you telnet home public IP port 3389?

--
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
"Dan" wrote in message
...
Hi,
I am trying to use remote desktop connection to go from Windows 2000 at
work
to a Windows Vista Business machine at home. I have set up my home router
to
forward the correct ports and people are able to connect fine from other
computers (running Windows XP Pro).

Whenever I try to connect though from work using Windows 2000, it gives me
an error telling me it cannot connect or that the remote computer might be
too busy to accept connections. Except I have had people try the same
settings from other computers and they get in.

I am using RDC Client 5.1 at work on my Windows 2000 machine. The IT Help
Desk tells me it should be working (i.e. - not a firewall problem) but I
wanted to see if anyone here knew what might be wrong.

From past experience, I think I might have better luck getting a working,
timely answer here.

Thanks!
-Dan

Make sure the [my ip address] is the public IP address. If we can't telnet
port 3389, we should double check the firewall or port forwarding.

--
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
"Dan" wrote in message
news
Hi Robert,

It does not appear that I can telnet to my computer or port.

I ran telnet - open - [my ip address] - got back "Could not open a
connection to host: Connect failed"

Then I tried open - [my ip address] 3389 - got back got back "Could not
open a connection to host on port 3389: Connect failed"

Does that mean it is a local firewall issue?

-Dan



"Robert L. (MS-MVP)" wrote:

Can you telnet home public IP port 3389?

--
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
"Dan" wrote in message
...
Hi,
I am trying to use remote desktop connection to go from Windows 2000 at
work
to a Windows Vista Business machine at home. I have set up my home
router
to
forward the correct ports and people are able to connect fine from
other
computers (running Windows XP Pro).

Whenever I try to connect though from work using Windows 2000, it gives
me
an error telling me it cannot connect or that the remote computer might
be
too busy to accept connections. Except I have had people try the same
settings from other computers and they get in.

I am using RDC Client 5.1 at work on my Windows 2000 machine. The IT
Help
Desk tells me it should be working (i.e. - not a firewall problem) but
I
wanted to see if anyone here knew what might be wrong.

From past experience, I think I might have better luck getting a
working,
timely answer here.

Thanks!
-Dan

That is the public IP address (and I know my router port forwarding is
working correctly since I can connect from other locations home).

By firewall, is there anything on my work computer that I would have control
over? Or any work around where I can tell the RDC client to use a different
port at work to try sending it out through?



"Robert L. (MS-MVP)" wrote:

Make sure the [my ip address] is the public IP address. If we can't telnet
port 3389, we should double check the firewall or port forwarding.

--
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
"Dan" wrote in message
news
Hi Robert,

It does not appear that I can telnet to my computer or port.

I ran telnet - open - [my ip address] - got back "Could not open a
connection to host: Connect failed"

Then I tried open - [my ip address] 3389 - got back got back "Could not
open a connection to host on port 3389: Connect failed"

Does that mean it is a local firewall issue?

-Dan



"Robert L. (MS-MVP)" wrote:

Can you telnet home public IP port 3389?

--
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
"Dan" wrote in message
...
Hi,
I am trying to use remote desktop connection to go from Windows 2000 at
work
to a Windows Vista Business machine at home. I have set up my home
router
to
forward the correct ports and people are able to connect fine from
other
computers (running Windows XP Pro).

Whenever I try to connect though from work using Windows 2000, it gives
me
an error telling me it cannot connect or that the remote computer might
be
too busy to accept connections. Except I have had people try the same
settings from other computers and they get in.

I am using RDC Client 5.1 at work on my Windows 2000 machine. The IT
Help
Desk tells me it should be working (i.e. - not a firewall problem) but
I
wanted to see if anyone here knew what might be wrong.

From past experience, I think I might have better luck getting a
working,
timely answer here.

Thanks!
-Dan