[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 351
  • Last Modified:

Remote Desktop Connection

Hi All,

Im running windows 2003 on a server connected to a workgroup. I have 5 systems running windows XP Pro.
My question is how would i go about allowing the windows 2003 machine to allow multiple remote desktop connections to the machine from the XP Pro clients.
Is there something specific that i need to do or is this something that i dont need to worry about?  the machines will just connect and i dont need to do anything special on the 2003 server system.
0
Eaddy Barnes
Asked:
Eaddy Barnes
  • 12
  • 12
  • 3
  • +1
3 Solutions
 
bluetabCommented:
You need to configure Terminal Services on the 2003 machine and add the appropriate TS licenses.  You can configure Terminal Services by using the "Manage Your Server" utility.
0
 
artthegeekCommented:
You need to be licensed for Terminal Services.  by default, 2003 server will allow a minimal number of connections for Administration.
You can change this in Add/Remove Programs, Add/Remove Windows Components.  Again, though you can run demo for a while, you'll need to purchase licenses.
0
 
ormerodrutterCommented:
Remember when configuring TS you set it to run in Application Mode. You need to purchase one CAL for each user. You have 120 days to purchase your licence (90 days for w2k server) and after that TS will stop connecting TS user if no licences are installed.
http://www.microsoft.com/technet/community/en-us/terminal/terminal_faq.mspx

However there is one exception in licencing. If you OWN your XP Pro licence before 24/04/2003 then you ARE eligible for a complimentary Windows Server 2003 TS CAL (i.e. no need to purchase TS licence in that case). See this for more info :-
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/tscaltransfaq.mspx

0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Eaddy BarnesITAuthor Commented:
Hi again,

I went to the tscc dialog box and i see that theirs a connection already in there:

Connection  RDP-tcp
Transport   tcp
Type Microsoft RDP 5.2

that allows 2 connections.
I dont think that i would need more than these two connections bein connected to at 1 time.
any way any of u can kick start me on how i can configure this to connect to it using remote desktop connection.

Ive put the server on the workgroup and was just trying to fiddle with the network adapter by adding an IP address & subnet.

Then went into the properties for the already installed connection but im somewhat confused on what to do next.


thx in advance  
0
 
bluetabCommented:
what happens when you go RDP from a workstation and try to connect to the server?
0
 
Eaddy BarnesITAuthor Commented:
I get this:

The client could not connect to the remote computer.

Remote connections might not be enabled or the computer 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 teh problem continues to occur, contact your administrator
0
 
bluetabCommented:
I'm assuming you get this error even when trying to log in as a Domain Admin.  Is the Terminal Servies service started?  You should also look in the Terminal Services Manager just to make sure there are no other active sessions besides the console.  
0
 
Eaddy BarnesITAuthor Commented:
hi bluetab theres two sessions running one is console and the other says

Server-
Session - RDP-tcp
User - blank
ID- 65537
State - listen
 - microsoft RDP-tcp
0
 
bluetabCommented:
The console session is the session logged in on the server console.  Right click the rdp-tcp session and choose reset.  That will kill that session.  You should still be able to log in since only one RDP session is being used but try logging in after resetting that connection and let me know.  
0
 
Eaddy BarnesITAuthor Commented:
OK just reset it and tried again, took awhile longer this time to return an error, same as above.
One thing though when i go to goto network places on the XP machine and to view workgroup computers i can see the server computer icon..

Also i put static ips into the network adapter

IP address 192.168.1.10
SUbnet 255.255.255.0
Gateway 192.168.1.1

if this helps

0
 
bluetabCommented:
What is the IP address of the server? What is the DNS server on your desktop?  Try connecting to the server by typing in the IP address instead of computer name.  If the DNS server is not configured properly the computer name will not resolve correctly to the IP address and you will get the error message that you mentioned above.
0
 
Eaddy BarnesITAuthor Commented:
still not working.
0
 
bluetabCommented:
What is the IP address of the server and what is the DNS server on the desktop?
0
 
Eaddy BarnesITAuthor Commented:
Ip on server is 192.168.1.103 , DNS of desktop is 208.59.69.2
0
 
bluetabCommented:
Have you verified that the TS services is running in services.msc?  Is your network a domain or workgroup?  

Here's the ultimate test to figure out if the problem is with the workstations or with the server.  Can you Remote Desktop to the server while logged into the server?  While logged into the server open Remote Desktop and try to connect to the server.  If you can then we know the server is configured correctly and we need to make some adjustments on the workstations, if you can't then the problem is on the server.
0
 
Eaddy BarnesITAuthor Commented:
Hi bluetab,

its a workgroup and yep I can Remote Desktop to the server while logged into the server with no problems
0
 
bluetabCommented:
Did you try connecting to the server via IP address instead of computer name?
0
 
Eaddy BarnesITAuthor Commented:
Yep tried via Ip address and it was unsuccessful
0
 
bluetabCommented:
Can you ping the server from the workstation or access shared files?  It sounds like the workstation and server are not on the same network.  
0
 
Eaddy BarnesITAuthor Commented:
yeah they are on same workgroup i checked and double checked that  and no when i ping it i get timed out..

Its defenitely on the same workgroup
0
 
artthegeekCommented:
It sounds like you don't have IP connectivity between the two.  
How do they connect (physically) to the network and each other?  
Is the Windows Firewall active on the PC?
0
 
bluetabCommented:
I agree with artthegeek.  Since you can not ping the server the computers may not be on the same physical network.  Are they all plugged into a working switch?  Are the two computers and server able to access the Internet (easiest way to see if they cables and network cards are working).  Next, do you have any software firewalls installed on the server or workstations.  If so disable those.
0
 
Eaddy BarnesITAuthor Commented:
hey dudes,

sorry for the late delay i will try this as soon as im home and report back to u.
0
 
Eaddy BarnesITAuthor Commented:
ok guys now I can see all workstations, shared drives and folders from the server on the work group but not vise versa. unable to see the server from the stations.
0
 
bluetabCommented:
What changes did you make?
0
 
Eaddy BarnesITAuthor Commented:
turned off firewall on the workstations
0
 
bluetabCommented:
Here's a Microsoft KB article:
http://support.microsoft.com/kb/308127
0
 
artthegeekCommented:
When you say you can't see, you mean by browsing the network?
Can you terminal into the server from the workstations now (by name or IP)?

Please check the properties of the network connection on the workstation & see if File and Printer Sharing for Microsoft Networks is installed.  What other protocols appear?

When you ping by name - does it resolve the name to an address?
Also - I'm concerned about the DNS server specified in the workstation settings.  It sounds like a public DNS that won't resolve local names.
Would you please open a cmd window, type ipconfig/all on workstation and server and post for us?

0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 12
  • 12
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now