Connecting to Terminal Server?

[Ovatvvon]

I setup Terminal server on one windows 2000 server machine, and tested the connection on the local area network (behind the same router, working with private ip's: 192.168....) and everything worked perfectly.

I since moved it to a remote location. I can still access it after setting up the port 3389 to forward to the machine, and can get to the login screen. However, the problem is it will not let me login. I am providing the correct password, but keep getting an error saying the machine cannot log me on and to make sure my user name and domain are correct (they are), and to make sure caps lock isn't on (it's not).

Does anyone know what might be causing this to fail? Do passwords get transmitted over a different port? Or is it requird to have a VPN? Any thoughts / suggestions?

-Ovatvvon :-Q

 

[mrmoneymatters]

I am not sure why you can't logon, but I can tell you that you don't have to have a vpn, and passwords aren't sent over a different port.

Network Admin
A+, Network+, MCSA 2000, MCSE 2000

 

[Hockeman]

Generally opening terminal services ports on your firewall is a bad idea unless your terminal server is in a DMZ. Concerning the password thing, try typing your password in the username box just to be sure that you are entering it correctly, and then put your username back and type the password in the password box. Also, Make sure you try to logon with your administrator account first to be sure you have your rights setup correctly. If the user doesn’t have the “log on locally” right you will not be able to logon to the server. Good luck!!

http://www.sentigy.com

"Experince That Counts

 

[Ovatvvon]

Yep, I am entering the password correctly, and I also tried with the administrator account, and I still receive the same error.

(I'm not worried too much about the security aspect as this is a development/test server without much on it.)

-Ovatvvon :-Q