Home > Connect To > This Computer Can't Connect To The Remote Computer Server 2008

This Computer Can't Connect To The Remote Computer Server 2008


Virus on the client? Are you doing this over a VPN perchance? 0 Poblano OP ITDBTC Apr 18, 2010 at 7:40 UTC Yes - A privately managed VPN across Cisco devices 0 Join Now Scenario: XP clients (in a workgroup) out on remote subnets trying to connect to a Windows Server 2008 Terminal Server. 3 terminal servers in environment, only 1 has the TECHNOLOGY IN THIS DISCUSSION Join the Community! navigate here

Support for NLA was released with Firmware 7.1.113 found in Firmware Package 7.1.3. Ihr Feedback wurde gesendet. Don't change or disable the network cards after licensing to prevent changing the Installation ID, which can affect the validity of the license. "This Terminal Disabled" A ThinManager administrator has disabled Note: In 2012, this must be done via Group Policy or Registry Key. https://social.technet.microsoft.com/Forums/office/en-US/59def614-9317-48e1-bc75-73cfb92e80af/unable-to-connect-to-terminal-server?forum=winserverTS

This Computer Can't Connect To The Remote Computer Server 2008

Recreated yet another virtual terminal server and clients can connect to both again. 7. Run the Terminal Server List Wizard and change to an administrative user name and password on the Terminal Server Name page of the Terminal Server List Wizard. Vincent und die Grenadinen Südafrika Surinam Swasiland Tadschikistan Taiwan Tansania Thailand Togo Trinidad und Tobago Tschad Tschechien Tunesien Türkei Turkmenistan Turks- und Caicosinseln Uganda Ukraine Ungarn Uruguay USA Usbekistan Vanuatu Venezuela

Check router address, IP Addresses, and Subnet Mask Using Static IP Has the ThinManager Server IP Address been entered in the IP Configuration Menu? No RDC seesions are effected connecting to these VMs ? "I think it has something to do with RDPv6. i have created yet another virtual terminal server and the thin clients can connect again to this one. Rdp This Computer Can't Connect To The Remote Computer Microsoft truncates the terminal names to 15 characters.

the VPN is dropping and not setting up fast enough for the RDP traffic to make it.  Doing the ping establishes the VPN and then the RPD works fine.  Common scenario. 0 This Computer Can't Connect To The Remote Computer Server 2003 Make sure that you are using a ThinManager Ready thin client that has sound capability. Change the subnet mask in the ACP Boot Loader menu. https://support.microsoft.com/en-us/kb/2477176 Check if a later version of firmware is available for your specific thin client has been released.

If the terminals are configured to use the other domain they will be unable to login. This Computer Can't Connect To The Remote Computer Server 2012 Related 2HP Compaq T20 Thin Clients & Windows Server 2008 R2: RDP Disconnects instantly3Improving screen redraw rate on thin-client over RDP to Server 2008 R21Server 2008 Domain Setup. When terminal server is in 2 domains and an administrator logs into the console with a domain account, it sets that as the default domain. Looking to get things done in web development?

This Computer Can't Connect To The Remote Computer Server 2003

Any tips on resolving this? windows-server-2008-r2 terminal-server thin-client rds share|improve this question edited Mar 7 '13 at 20:55 asked Feb 1 '13 at 20:41 ewwhite 153k49306583 add a comment| 1 Answer 1 active oldest votes up This Computer Can't Connect To The Remote Computer Server 2008 Join the community Back I agree Powerful tools you need, all for free. Cannot Rdp To Server 2008 R2 under terminal services they cant.

Static IP hasn't been set. check over here After the session is established, it will disconnect randomly Make sure each user is logging on with a unique user name. Does the DHCP server have addresses to give out? Any ideas? This Computer Can't Connect To The Remote Computer Server 2008 R2

PXE-E53: No boot filename received. Get this though, installed 3 updates which included IE9 today on the VTS1 which had no problems, restarted and now they cant connect to that one although it had been working Using flags vs. his comment is here No idea why we had this issue or the fact that safter teh 2nd rebuild turning the firewall off made a difference but with it on it still didn't work.....   Anyway, solution was static

Reply Subscribe RELATED TOPICS: Cannot .RDP into a server until I ping it first Remote Desktop Can't Connect Telnet works but RDP doesn't Best Answer Poblano OP ITDBTC Apr 22, 2010 This Computer Can't Connect To The Remote Computer Windows 7 If you are using a Citrix Published Application, you may need to specify the ICA browser. If the XP clients try either of the other 2 terminal servers they work just fine without the need for a ping.

Can't do it during the day as all our apps are delivered via TS and it's a retail environment so would stop us being able to serve customers.......

This will display the Configuration for the Terminal Server. The other device type, of which there are many in the environment, is the HP T5510 Thin Client. Both were working then 1 just stopped accepting connections from Linux based thin client. 3. Remote Desktop Connection Not Working Windows 10 All rights reserved.Newsletter|Contact Us|Privacy Statement|Terms of Use|Trademarks|Site Feedback {{offlineMessage}} Try Microsoft Edge, a fast and secure browser that's designed for Windows 10 Get started Store Store home Devices Microsoft Surface PCs

Check the Subnet Mask in the ACP Boot Loader on the thin client. Creating your account only takes a few minutes. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.Would you like to participate? weblink I think it has something to do with RDPv6.

This problem occurs because the process that recovers the expired CALs from the Terminal Server license server did not restart when the Volume Shadow Copy Service finished the backup process, even Properly working sound will play a sound at boot and at login. Regards James Loker-Steele http://www.lokersteele.co.uk/ Marked as answer by Alan ZhuModerator Wednesday, May 18, 2011 2:52 AM Tuesday, May 17, 2011 7:38 AM Reply | Quote Microsoft is conducting an online survey Make sure you export your settings on the problem TS first just in case the import mucks things up.

It was a bit like XP and Vista...you know XP works brilliantly and vista just didnt. Perhaps there is a power save setting in effect that is shutting down some component causing there to be a delay in response? 0 Mace OP Texkonc Apr The interactive shadow must be checked in RemoteView on the ThinManager menu. Elux NG (had Elux RL on but wasnt up to date) so now on the old version and it works perfectly.

Network Level Authentication is OFF everywhere Connecting using the IP address doesnt work from them either. The terminals in the tree on the primary ThinManager Server show green while the terminals on the secondary are all red Enable automatic synchronization by selecting Manage > ThinManager Server List Updated them and all is now fine. As mentioned though, the thin client does connect to one of the Virtual Terminal Servers but not the other and they are both running windows 2008.

Dec 19, 2006 Jerold Schulman | Windows IT Pro EMAIL Tweet Comments 0 Advertisement A Terminal Services client may be unable to connect to a Terminal Services license server installed on The client is showing the time of the terminal server in a different time zone and not the local time Use the Time Zone Redirection Module on the client with the Retrieved from "http://www.thinmanager.com/kb/index.php?title=Common_Configuration_Problems&oldid=8095" Categories: TroubleshootingWindows Settings Personal tools Log in Namespaces Page Discussion Variants Views Read View source View history Actions Search Navigation Main page Categories Recent changes Random page Printable WinTMC is for PCs, not servers.

Always Prompt for Password may be setup and should be disabled: Start > Programs > Administrative Tools > Terminal Services Configuration (2003, 2008) or Remote Desktop Session Host Configuration (2008 R2) Multirow is cut off A Page of Puzzling An idiom or phrase for when you're about to be ill Word for fake religious people Is it possible to have 3 real Login to Terminal Server prompts for password even though the username and password are filled in ThinManager The password may be entered wrong in ThinManager. Make sure that the security policy of the terminal server or domain allows it: Start > Run > secpol.msc > OK Expand: Computer Configuration > Administrative Templates> Windows Components > Terminal

The Process information won't display for terminals with a name longer than 15 characters. Your solution looks pretty good.