Terminal Services Not connecting

[jcurtiss]

I installed TS on 2k server in remote admin mode. i can't connect with TS client or xp remote desktop. i can't telnet to port 3389 either, and there is no firewall between the client and host; including personal firewalls. the TS service appears to be running on the server.

 

[PMuller]

I am no expert, but have messed around (and been messed around) with and by terminal server. What you dont say ishow you are trying to connect. 1/ Can you ping the server from your WS? 2/ Have you set the server up in Remote Admin mode or in Application mode. In either case you need to set the policy to allow access.. open the routing and remote access snap in, expand the server running RRAS and check the remote access policies.. there should be one entry - double click the entry in the right pane and see if it is set to "Grant ...." the default is "Deny.."

Good luck.. now if I could just find someone to help me with my problem!!

 

[jcurtiss]

yes, i can ping it, and i can log onto it (it's the domain controller.) what i can't do is telnet to it on port 3389. which tells me that terminal services isn't REALLY running, even though it says it is in Services. i can telnet to it on port 80, where IIS is running. telnet to is on port 5631, where pcanywhere is running. but can't telnet to port 3389, where terminal services is running. it's in remote admin mode. the users in question are given permissions to connect remotely; but from what i've read about TS i should be able to telnet to port 3389 on a server running TS.

 

[PMuller]

I have to pass on your efforts with telnet... I have not tried that, so know nothing about it.. however I do know that if you set up TS in remote admin mode only two users can connect at one time. Forgive me for hammering on this.. but as I know not a lot about telnet, I would suggest you try to connect to your server with the remote desktop client of WINXP... if you cant then you have not set the service up correctly. I have spent hours reading win2000 server guides etc.. and messing around with a test system... so most of my experience is self taught... which means I cant give you a sound reason for trying it any other way than what I have.. Hope it helps.
Peter

 

[jcurtiss]

from my original post, "i can't connect with TS client or xp remote desktop."

the idea behind telnetting is that if TS is running, it has to be listening, and it's supposed to be listening on 3389. if i check services, Terminal Services is running. do a net start from a command line, Terminal Services is running. the only thing i can think of is that my server doesn't meet some hardware requirement, although it DOES install fine and i can't find any listings of hardware requirements for TS.

 

[alliknowisnetworking]

Hardware is not the problem, If so you wouldnt of been able to install 2000 itself.

How are you trying to get in? IP or DNS name? do a
netstat -a see if its actually listening for connections of port 3389. You might wanna stop term srvc, and close port 3389, then restart term srvc, and open the port back up.

Is this a straight client to server connection (i.e a test type thing)or are you on a working network (i.e in a company work environment?)

check your client side also because port 3389 has to be open on that side too. Let us know if this helped,and if you find a fix let us know what ya did.

 

[PMuller]

I agree with "al" its not a harware problem if you can log on to the server in the regular manner. This is software. From a practical perspective I would simply take a WINXP pc... and use remote desktop ... when asked for the address of the host server.. type in its ip address. Then let use know what message you get.

I had a little think last night, and this morning I tried to telnet into our own (working) TS... I got no response either.. even though it is listening on the portd 'Al' mentioned.

Peter

 

[basst]

Are you running SP2 on the XP desktop?

 

[PMuller]

On the telnet attempt... I spoke to a colleague who told me that TS will not respond to a telnet prompt, because TS works with encrypted data.. Telent does not know how to decrypt any responses it might get, and therefore times out.

back to the remote desktop attempt me thinks

Peter

 

[jcurtiss]

i have attempted this with xp2 remote desktop. i have attempted it with the remote desktop client for 2000 pro, as well as the terminal services client for 2000 pro. this is a domain at my house with one server that is the domain controller and DNS server and TS server. name resolution is not the problem. i have a 2000 pro desktop and an xp pro sp2 laptop. neither can connect.

but thanks for testing the telnet; this is probably a permissions issue then, wouldn't you think? however, the wording of the error is the same as the one i get when i try to remote desktop to a computer that is known to NOT be running TS, like if i try to remote desktop to a 2000 pro pc at work:
*****
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 connections.

Please try connecting again later. If the problem continues to occur, contact your administrator.

*****

 

[technome]

Telnet, through the command telnet "server name or IP" 3389 ,registers a connection on my 2000 TS, locally or via a vpn remote. Something is blocking the telnet

http://support.microsoft.com/kb/187628/EN-US/

I did have a problem connecting RDC at my office TS server until I turned off SMB signing.

 

[jcurtiss]

except i'm not on a WAN, i'm in a 2 bedroom apartment connecting through a $30 linksys switch, which i'm pretty sure is incapable of blocking telnet.

where do i turn off smb signing?

 

[CodingIsFun]

I had a similar problem:

Check that the router is set to reroute to port 3389 for that particular IP.

Make sure the Internet Protocol for the client TCP/IP Properties has the preferred DNS set to your domain controller IP and not your internet provider.

If the router is setup to reroute correctly try going directly to the router IP port 3389 (e.g. 1.1.1.1:3389).

If none of these work, I have a few other things to check.

cif

 

[technome]

For SMB signing search google for disable SMB signing

At my office I have a linksys also with the default setting, telnet has no problems for machines on the office network internally, without 3389 port redirection. I have VPN connections so remotes have no problem with telnet, goes through a tunnel, so I need not redirect port 3389.

 

[jcurtiss]

these attempts are not going through a router. they are on the local subnet. but for the record, my linksys box is currently forwarding port 3389 to the ip address of my server; waiting patiently for the day that i can get the server to accept inbound TS connections. the clients have 1 (one) DNS server statically set in their TCP/IP settings. and that 1 (one) DNS server is my domain controller, my DNS server, my terminal services server to which i cannot connect. it will not connect by name nor will it connect by ip address, although i can ping and nslookup and UNC and http and ftp the and map network drives and add network printers on the server by both name and ip address. this is not an issue on the network, nor is it a name resolution issue. this is an issue with the TS server setup, or some AD permission i'm missing.

 

[basst]

You need to be a member of the domain admins group to connect to TS. You say you cannot connect using the TS client. What does this mean?? Do you get to the logon screen or do you get a error message before you get that far?

 

[jcurtiss]

the error message comes up as soon as i click 'connect' on remote desktop. i never see the windows logon screen. as i said, it's the same error message i get when i attempt to connect to a machine that i know is NOT running terminal services.

i am a domain admin.

 

[basst]

Try using the Microsoft Terminal Services client.
I have seen servers that cannot be connected with the Remote Desktop but Terminal Services client works ok.

 

[technome]

For a test I would connect a machine directly to the server without a switch or router in between.

 

[jsentelle]

May sound like a silly question, but have you gone to the user account on the domain controller and checked the box that says "Allow logon to terminal server"?