Windows Server TechCenter >
Windows Server Forums
>
Terminal Services
>
Error while connecting to TS Windows Server 2008 R2
Error while connecting to TS Windows Server 2008 R2
- Hello Guys,
I'm having problems when the remote office clients try to connect to TS.
Customers can connect the VPN to access the server normally.
Customers who are in remote offices connect to the central office through
a dedicated link, so you can access all network resources.
This same remote office clients can access the TS windows server 2003,
but can not access the TS windows server 2008 R2.
The tab:
"Allow connections from computers running any version of Remote Desktop (less secure)" --->is already enabled.
Would anyone tell me what can this happening?
Thanks for your help.
Hugs.
Gustavo Santos
Answers
- Hello Guys,
could find what was going wrong.
In the gateway configuration of my server I was directed to my Isa server, and the direction should be for my router
When I headed to the Isa Server another route was followed for the communication between the server and client.
I was able to visualize this error with Network Monitor, assessing the exchange of packets and ping could visualize what the TTL (TTL and was different on the server and the client when running the ping), and ultimately could not confirm the problem with Tracert seeing that the server was doing a route and another client.
After you make an exchange gateway, directing all traffic to my router, everything worked normally.
thank you all for your help.
Thank you very very much
Gustavo Santos- Proposed As Answer byRobert Maijen Friday, November 06, 2009 9:24 AM
- Marked As Answer byLionel Chen - MSFTMSFT, ModeratorFriday, November 06, 2009 9:36 AM
All Replies
- Hi Gustavo, Could you please tell the exact error message you get when trying to connect to TS? Are you using a RD Gateway Server in between? Thanks, Mauruthi. G
Hi Mauruthi,
Following is the message that is returned when the client's remote office tries to connect to TS server:
This computer can not connect to the remote computer.
Try connecting again. If the problem persists, contact the
owner of the remote computer or network administrator.
Thanks for your help
Gustavo Santos- Hi Gustavo,
Going by the information you have given, I am assuming the following; please correct me if I am wrong:
1) The client computer is already connected to the central office network and is able to access other computers in the central office such as the Windows 2003 TS.
2) You are trying to connect directly to the Windows 2008 R2 TS computer from the clients, without using a Remote Desktop Gateway in between.
Could you please try out the following steps:
1) Ping the TS Server to see if its able to resolve the IP address and reach it. To do this, Open a command prompt and type:
ping tsServerComputerName
2) Try to remote connect to the TS Server by using its FQDN. (example: mycomputer.CompanyDomainName.com)
3) Are you able to remote desktop into the Windows 2008 R2 computer from a client computer which is inside the Central Office (rather than a Remote Client)?
Thanks,
Mauruthi. G One more question: What is the Operating System of the Client Computer(s)?
Thanks,
Mauruthi. G- Hello Mauruthi,
the information is correct.
Steps performed:
1 - I can ping the server by name and IP it.
2 - Inside the office I can connect using the name
and the server IP. In remote offices can drop the name
and IP but can not access the server using remote desktop.
3 - Yes In the central office can access.
Another fact that may be important is that my clients who are
connected to VPN, can also access the server and
use the remote desktop.
All clients are windows XP with SP3 installed.
Thanks for your help!
Gustavo Santos - Gustavo,
When you ping the server, are you doing it from a machine that is having issue? Just making sure.
Sounds like the issue has to do with the direct link. You must have a point to point connection? Anything in the router logs of interest?
Also, are the clients that do connect running Win XP SP3?
Just to be sure, are the clients from the remote office added to the Remote Desktop Users group on the R2 terminal server?
Hope this helps,
Kristin L. Griffin
Co-Author of the Windows Server 2008 Terminal Services Resource Kit (and a SUPER BIG fan of the Microsoft RDV Team!!!) - Hello,
yes, I am running on a machine with the problem.
It is a direct link, where the workstations have access direct the resources of the central office.
I looked at the router and not have to log on or connection error blockade.
Yes, all clients are Win XP SP3.
Yes, all customers are in the group RDUsers.
If you have any configuration that I have to look just post that I check.
Thanks for your help!
Gustavo Santos - Hello Guys,
Is there a rule in windows firewall to block other IP's from connecting?
It is the following.
The ip of my network is 192.1.1.1 - 254/16
The ip of my servers is 192.1.0.1 - 254/16
The ip of my remote office is: 192.10.10.1 - 254/16
The ip of my VPN is: 192.255.255.1 - 254/32
Is there a lock?
Gustavo Santos - Hi,
If you are using the Windows Firewall, could you please check the following in the Windows 2008 R2 server:
1) Go to Start -> Administrative Tools -> Windows Firewall with Advanced Security
2) Click on Inbound Rules
3) Double click the item which says 'Remote Desktop (TCP-in)'
4) Make sure that the 'Enabled' check box is checked
5) Under the item which says 'Action', the 'Blocked' checkbox shouldnt be checked.
6) Click on the 'Scope' tab.
7) You can select the IP address ranges for allowing Remote Desktop Connections in this tab.
8) Click on the 'Advanced' tab and make sure that the settings (Profiles & Interface Types) are enabled/allowed for the required network.
9) In the 'Computers' tab, verify if the Remote Client Computers are being allowed if the 'Only allow connections from these computers' is checked.
Thanks,
Mauruthi. G - Hi,
I did all the test and I made the settings did not work.
Occurred the same problem.
I looked at eventvwr and showed no error, both the server and the workstation.
any other tips?
Thanks for your help!
Gustavo Santos - Can you RDP to any other machines (like other client machines) located in the same office as the terminal server?
If you have windows firewall running a simple test would be to turn it off on the server and client, just to test. If your connection works then, you know you have some Windows Firewall work to do.
Hope this helps,
Kristin L. Griffin
Co-Author of the Windows Server 2008 Terminal Services Resource Kit (and a SUPER BIG fan of the Microsoft RDV Team!!!) - Hello Guys,
could find what was going wrong.
In the gateway configuration of my server I was directed to my Isa server, and the direction should be for my router
When I headed to the Isa Server another route was followed for the communication between the server and client.
I was able to visualize this error with Network Monitor, assessing the exchange of packets and ping could visualize what the TTL (TTL and was different on the server and the client when running the ping), and ultimately could not confirm the problem with Tracert seeing that the server was doing a route and another client.
After you make an exchange gateway, directing all traffic to my router, everything worked normally.
thank you all for your help.
Thank you very very much
Gustavo Santos- Proposed As Answer byRobert Maijen Friday, November 06, 2009 9:24 AM
- Marked As Answer byLionel Chen - MSFTMSFT, ModeratorFriday, November 06, 2009 9:36 AM
