id="info"

Question

Locked

the client could not connect to the remote computer.

By globalsocialite ·
I am getting the error: "the client could not connect to the remote computer. remote connections might not be enabled or thecomputer 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."

I get this when remoting from home over vpn onto on our 2003 db server in a domain running ad. however, when i remote to another server in the same domain, then from that server remote into the db server with the previous error, i can get in.

does dns forwarding have anything to do with this or should i look somewhere else?

This conversation is currently closed to new comments.

14 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Answers

Collapse -

Remoting

by p.j.hutchison In reply to the client could not conn ...

It depends on how Terminal Services are setup. By default admin TS mode will only allow two sessions at once. To clear a session, the use MUST logout and not just close the TS window.
Use Terminal Services Manager to logout disconnected sessions.

Collapse -

tsc limitations

by globalsocialite In reply to Remoting

Its not the a problem with the default 2 person logons. I cleared them out and tied to log on and no joy.

Collapse -

TS

by vp In reply to Remoting

Hi I am am having some problems with certain computers not been able to connect to Terminal Server. It is not a license issue as we have enough. Not too sure why my server is blocking certain computers. Any help would be great.

Collapse -

How is Your DNS setup?

by juan18_c In reply to the client could not conn ...

Remeber that forwarding to your ISP is very important you want every IP to be resolved correctly. As of to the setup of your forward-lookup / reverse-lookup zones. it is crucial you have at lest a forward lookup. Can you give us an insight on your network setup.

Collapse -

On the level of "is it plugged in", have you changed "hosts"?

by daveo2000 In reply to How is Your DNS setup?

Check your "hosts" file to make sure that you haven't added the hostname you are trying to reach with a stale IP address.

Unlikely to be your problem but little things can bite you when you least expect it.

Collapse -

hosts file

by globalsocialite In reply to On the level of "is it pl ...

I havent changed any hosts. but the dns is handeled by another group that actually runs the building (not my company)

Collapse -

connecting probs

by globalsocialite In reply to How is Your DNS setup?

We are having problems connecting to to the server over VPN, but are not having the problem from the office. Last week I had the same problem with a different server and the problem went away the next day.

Over the VPN I can ping the problem server but cannot telnet to port 3389 on it (rdp port)
I can telnet to 3389 on any other server over the VPN.

Everything works fine from a computer inside the network so Im thinking that leaves the VPN as the culprit. Maybe the problem is with the ACL's?

Collapse -

I have same issue- Remote Desktop thru VPN - Active Directory

by Hawk73ku In reply to connecting probs

I can not do a remote desktop connection through VPN and authenticated through IAS and Active Directory.

I can use Dameware (remote control) and control the server but terminal services isn't cooperating.

Previous questions didn't seem to get answers.

Collapse -

Resolution: Remote Desktop thru VPN

by Hawk73ku In reply to I have same issue- Remote ...

I could not do a Remote Desktop Connection through VPN and authenticated by IAS and Active Directory. I was receiving the same message "the client could not connect to the remote computer. remote connections might not be enabled or thecomputer 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." I could RDC from the LAN though.

The hint of port blocking by the routner got me looking at CISCO. I entered the following commands in my CISCO router and all is well.

access-list 102 permit ip 192.168.1.0 0.0.0.255 192.168.2.0 0.0.0.255

interface loopback 0
ip address 1.1.1.1 255.255.255.255
no shut

route-map NONAT permit 10
match ip address 102
set interface loopback0

interface bvi1
ip policy route-map NONAT

Collapse -

Cisco ACL fixed my problem also

by jaredt In reply to Resolution: Remote Deskto ...

Good call. We just replaced our Netopia router with a Cisco 2821 and I started getting the same RDC error on our TSWeb Terminal Server. I allowed https traffic through the FW to the server but forgot to allow port 3389 also.
Thanks,
Jared

Back to Networks Forum
14 total posts (Page 1 of 2)   01 | 02   Next

Hardware Forums