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.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Terminal Services Not connecting
- Thread starter jcurtiss
- Start date
Been away for a couple of days and thought about this. I have alsmost exactly the same configuration as you... Server in the office (at home) AD installed all service packs (2000) and a linksys router. I have also seen the message you are getting. Here are a couple of things..
1/ I suppose you have set the user account to allow dial in.. I know, I know, you dont even get as far as the dial in.. attempt you get the reject message as soon as you hit enter after entering the IP address. Just want to eliminate everything.
2/ Is your router working as the DHCP server? or is DHCP activated in the server? (linksys DHCP servers are on by default)
3/ What is the address of the DNS server as handed out by the DHCP server... (not that it should matter just checking)
4/ does IPCONFIG report back the correct ip addresses and subnets.. ie does it actually report back what you think it should be reporting back?
5/ If your traffic is going over the router, which it might be.. (try a tracert) the router may be the problem. Some linksys router (so I have read) do not handle TS properly (although they should). You might try to replace the router with a cheapie switch just to try it out. (activate DHCP on the server OR give your workstation a fixed IP address for the test)
6/ try issuin the netstat -a command on the server to see that it is listening on port 3889.
7/ Are you running a firewall on the server.. liek norton or macafee.. that would block the incomming traffic.
8/ Are your running port blocking (Macafee blocks some ports by default) on your workstation?
Everything your write makes me think that it is a port blocking problem... not a network error or an authorisation error. Clearly your workstation is not getting out to the server on the port it wants to which is why you get the error message...
Are you trying to run a VPN tunnel from the workstation as well as trying the TS session...
I know lots of 'Already tried that' but its all I can come up with.
1/ I suppose you have set the user account to allow dial in.. I know, I know, you dont even get as far as the dial in.. attempt you get the reject message as soon as you hit enter after entering the IP address. Just want to eliminate everything.
2/ Is your router working as the DHCP server? or is DHCP activated in the server? (linksys DHCP servers are on by default)
3/ What is the address of the DNS server as handed out by the DHCP server... (not that it should matter just checking)
4/ does IPCONFIG report back the correct ip addresses and subnets.. ie does it actually report back what you think it should be reporting back?
5/ If your traffic is going over the router, which it might be.. (try a tracert) the router may be the problem. Some linksys router (so I have read) do not handle TS properly (although they should). You might try to replace the router with a cheapie switch just to try it out. (activate DHCP on the server OR give your workstation a fixed IP address for the test)
6/ try issuin the netstat -a command on the server to see that it is listening on port 3889.
7/ Are you running a firewall on the server.. liek norton or macafee.. that would block the incomming traffic.
8/ Are your running port blocking (Macafee blocks some ports by default) on your workstation?
Everything your write makes me think that it is a port blocking problem... not a network error or an authorisation error. Clearly your workstation is not getting out to the server on the port it wants to which is why you get the error message...
Are you trying to run a VPN tunnel from the workstation as well as trying the TS session...
I know lots of 'Already tried that' but its all I can come up with.
- Thread starter
- #23
should i start including the following in a signature so it's in every post?
*********************
from my march 23 post:
"from my original post, "i can't connect with TS client or xp remote desktop."
no host-based firewall anywhere. no dhcp, everything is static. dns is correct, traffic is all on the same subnet.
**********************
"telnet localhost 3389" on the ts server does not connect, while "telnet localhost" plus 80, 23, 21. or 5631 (pcanywhere) all connect. i may only be a CCNP, but i'm pretty sure there is no router between my server and itself. i'll check though.
-John
i can't connect with TS client or xp remote desktop.
no host-based firewall anywhere. no dhcp, everything is static. dns is correct, traffic is all on the same subnet.
*********************
from my march 23 post:
"from my original post, "i can't connect with TS client or xp remote desktop."
no host-based firewall anywhere. no dhcp, everything is static. dns is correct, traffic is all on the same subnet.
**********************
"telnet localhost 3389" on the ts server does not connect, while "telnet localhost" plus 80, 23, 21. or 5631 (pcanywhere) all connect. i may only be a CCNP, but i'm pretty sure there is no router between my server and itself. i'll check though.
-John
i can't connect with TS client or xp remote desktop.
no host-based firewall anywhere. no dhcp, everything is static. dns is correct, traffic is all on the same subnet.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question