+ Post New Thread
Results 1 to 10 of 10
Windows Thread, Terminal Server in Technical; I've set up Terminal Server on a bog standard computer with Win 2003 Standard Ed on it. All I did ...
  1. #1

    Join Date
    Jun 2008
    Posts
    731
    Thank Post
    118
    Thanked 66 Times in 54 Posts
    Rep Power
    31

    Terminal Server

    I've set up Terminal Server on a bog standard computer with Win 2003 Standard Ed on it. All I did on it was that I set it up to be a TS and nothing else. My issue is I'm not able to remote on to this server from another workstation in the domain. I believe remote desktop is enabled and I have enlisted myself in to the Remote Desktop Users security group but to no avail.

    Usually once RD is enabled you should be able to remote onto it. When TS is configured does this alter the server in some way that there is another method to connect to it remotely?

    Is there something I'm missing out?

  2. #2
    sammy's Avatar
    Join Date
    Nov 2006
    Location
    London
    Posts
    68
    Thank Post
    1
    Thanked 7 Times in 7 Posts
    Rep Power
    18

    Issues

    Hi Chuckster,

    assuming your workstation is in the same domain...and the ip address settings are correct....and the local domain policy on the 2003 server allows local logon you should have no issues logging in.

    Is the server connected to the domain or is it a standalone workgroup server?

    what error messages are you getting, they will allow you to diagnose the area to check quickly.

    is it that the logon window comes up but the local policy doesnt allow interactive logon...?

    or is it that you rdp client will not even touch the server interface and so the client is timing out ?

    if you fire across some more info im sure between us we can all work this out....i have seen TS be fininicky sometimes but its normally quite a puppy to work with.

  3. #3

    Join Date
    Jun 2008
    Posts
    731
    Thank Post
    118
    Thanked 66 Times in 54 Posts
    Rep Power
    31
    Quote Originally Posted by sammy View Post
    Hi Chuckster,

    assuming your workstation is in the same domain...and the ip address settings are correct....and the local domain policy on the 2003 server allows local logon you should have no issues logging in.

    Is the server connected to the domain or is it a standalone workgroup server?

    what error messages are you getting, they will allow you to diagnose the area to check quickly.

    is it that the logon window comes up but the local policy doesnt allow interactive logon...?

    or is it that you rdp client will not even touch the server interface and so the client is timing out ?

    if you fire across some more info im sure between us we can all work this out....i have seen TS be fininicky sometimes but its normally quite a puppy to work with.
    Hi Sammy,

    I have given the Server a static IP and it's connected on the domain and isn't a standalone. In a GPO I have put in a list of users that'll require using it. This is found in Computer configuration --> Windows Settings --> Local Policies --> User Rights Assignment --> Allow log on through Terminal Services

    When I launch remote desktop from a workstation and try connecting to the server, I get the following error message:

    This computer can't connect to the remote computer
    The connection was lost due to a network error. Try connecting again...


    If it was timing out, which it isn't, then that would have meant remote desktop isn't enabled.

  4. #4
    sammy's Avatar
    Join Date
    Nov 2006
    Location
    London
    Posts
    68
    Thank Post
    1
    Thanked 7 Times in 7 Posts
    Rep Power
    18

    Terminal

    hmmmm

    I have seen this tricky little one before, cant remmeber how i solved it though.

    Have you checked that the remote desktop port is open on the client firewall ?

    also, have you tried pinging the server ip address, make sure that your getting a reply

    also, have you tried connecting to the server ip address as opposed to the hostname of the server.

  5. #5

    Join Date
    Jun 2008
    Posts
    731
    Thank Post
    118
    Thanked 66 Times in 54 Posts
    Rep Power
    31
    I am able to ping the server using its IP address and also its name. Firewall is disabled and the remote desktop port is open, i.e. ticked.

    I've still not managed to get anywhere with this.

  6. #6
    sammy's Avatar
    Join Date
    Nov 2006
    Location
    London
    Posts
    68
    Thank Post
    1
    Thanked 7 Times in 7 Posts
    Rep Power
    18

    Terminal

    Hi Chuckster,

    scratching my head trying to remmeber this one....have you checked that the Terminal Services service is running on the client computer ? also which OS is on the client desktop ?

  7. #7
    altecsole's Avatar
    Join Date
    Jun 2005
    Location
    Whittington, Lancashire
    Posts
    286
    Thank Post
    40
    Thanked 36 Times in 26 Posts
    Rep Power
    26
    Try connecting to the console; open the run command and type:
    Code:
    mstsc -v server_name -console

  8. #8

    Ric_'s Avatar
    Join Date
    Jun 2005
    Location
    London
    Posts
    7,592
    Thank Post
    109
    Thanked 770 Times in 598 Posts
    Rep Power
    183
    Quote Originally Posted by altecsole View Post
    Try connecting to the console; open the run command and type:
    Code:
    mstsc -v server_name -console
    do you not mean
    Code:
    mstsc /console /v <servername>

  9. #9
    altecsole's Avatar
    Join Date
    Jun 2005
    Location
    Whittington, Lancashire
    Posts
    286
    Thank Post
    40
    Thanked 36 Times in 26 Posts
    Rep Power
    26
    Quote Originally Posted by Ric_ View Post
    do you not mean
    Code:
    mstsc /console /v <servername>
    They both do the same thing; so technically yes

  10. #10

    Join Date
    Jun 2008
    Posts
    731
    Thank Post
    118
    Thanked 66 Times in 54 Posts
    Rep Power
    31
    Thanks for all your suggestions guys. I appreciate it. The problem was that one of the students altered the IP address on a printer which happened to be the same IP for the terminal server. By changing the IP address to what it was before on the printer, I was soon able to remote on to the server.

SHARE:
+ Post New Thread

Similar Threads

  1. MS Terminal Server Sessions
    By Jonny_sims in forum Thin Client and Virtual Machines
    Replies: 6
    Last Post: 12th May 2010, 11:30 PM
  2. Anyone had a terminal server installed by RM
    By Ayaz in forum Thin Client and Virtual Machines
    Replies: 1
    Last Post: 13th August 2008, 10:55 PM
  3. Terminal Server
    By binky in forum Windows
    Replies: 16
    Last Post: 2nd April 2008, 01:14 PM
  4. Terminal Server
    By wesleyw in forum Thin Client and Virtual Machines
    Replies: 8
    Last Post: 26th February 2007, 01:03 PM
  5. HELP! RM Maths on Terminal Server
    By Kelyan in forum Thin Client and Virtual Machines
    Replies: 3
    Last Post: 4th December 2006, 02:05 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •