samprg
asked on
Remote Desktop
Hello,
I try to make remote desktop for windows 2008 thru modem Linksys WRT160n
I did :
1- I opened single port forwarding 3389 in the mode
2- I enabled remote desktop in the windows server 2008
Do I miss some thing?
Thanks
I try to make remote desktop for windows 2008 thru modem Linksys WRT160n
I did :
1- I opened single port forwarding 3389 in the mode
2- I enabled remote desktop in the windows server 2008
Do I miss some thing?
Thanks
1. Did you set a Forward rule to send the requests to your internal.server.ip over port 3389.
eg: http://portforward.com/english/routers/port_forwarding/Linksys/WRT160N/Remote_Desktop.htm
2. Enable remote desktop
eg: http://technet.microsoft.com/en-us/library/cc794832(WS.10).aspx
3. Do you have the firewall enabled to allow Remote Desktop enabled on the host?
If i had to guess the security context is still set to high.
let us know,
-Hades666
Make sure RDC is enabled and you have an account with permissions to connect with it.
ASKER
ZShaver:
I do not have any firewall software on the server
hades666:
1,2,3 I did
I do not have any firewall software on the server
hades666:
1,2,3 I did
From your client pc attempt the following.
1. Open CMD
2. Type "telnet your.ip.addr 3389"
Black screen Firewall openned.
Connection failed, your port forwarding or firewall is dening it.
Let us know,
Hades666
1. Open CMD
2. Type "telnet your.ip.addr 3389"
Black screen Firewall openned.
Connection failed, your port forwarding or firewall is dening it.
Let us know,
Hades666
Not all routers will support port forwarding from within the network to within the network
You may have to test this from another network, or give us the IP and we'll see if we get an RDP connect screen.
You may have to test this from another network, or give us the IP and we'll see if we get an RDP connect screen.
if you don't want your IP posted here you can email it to me and I'll try it rimtech@gmail.com
ASKER
From a client pc Windows 7, I got
'telnet' is not recognized as an internal or external command,
operable program or batch file.
'telnet' is not recognized as an internal or external command,
operable program or batch file.
lol, Telnet Client is not installed by default on Windows 7.
Install Telnet Client on Windows 7 or Windows Vista
On Windows 7, Windows Vista, you can use the Windows Features tool to install optional components.
To install Telnet Client on Windows 7 or Windows Vista
1.Click Start, and then click Control Panel.
2.On the Control Panel Home page, click Programs.
3.In the Programs and Features section, click Turn Windows features on or off.
4. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
5. In the Windows Features list, select Telnet Client, and then click OK.
Also, can you respond to the following:
1. where is this PC located?
2. Where is the client located?
Thanks,
Hades666
Install Telnet Client on Windows 7 or Windows Vista
On Windows 7, Windows Vista, you can use the Windows Features tool to install optional components.
To install Telnet Client on Windows 7 or Windows Vista
1.Click Start, and then click Control Panel.
2.On the Control Panel Home page, click Programs.
3.In the Programs and Features section, click Turn Windows features on or off.
4. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
5. In the Windows Features list, select Telnet Client, and then click OK.
Also, can you respond to the following:
1. where is this PC located?
2. Where is the client located?
Thanks,
Hades666
ASKER
ZShaver:
I use the router Linksys WRT160n, I also tested from outside is same thing, and I didn't get an RDP connect screen.
I use the router Linksys WRT160n, I also tested from outside is same thing, and I didn't get an RDP connect screen.
ASKER
hades666:
I got
Connecting To My.ip:3389...Could not open connection to the host, on por
t 23: Connect failed
Note:I tested it from same network and from home
I got
Connecting To My.ip:3389...Could not open connection to the host, on por
t 23: Connect failed
Note:I tested it from same network and from home
Great, so if you are getting connection failed from an internal source and and home Source, the issue is with your server setup.
Are you sure you have disabled ALL windows firewall profiles (domain,private and public) temporarily.
If you attempt to RDP to the server ifself from itself, You should get a login prompt but give an error that you cannot login to a logged in server.
As well, you Remote desktop settings, Are they enabled for allow all clients or only secure with NLA.
Let us know,
Hades666
Are you sure you have disabled ALL windows firewall profiles (domain,private and public) temporarily.
If you attempt to RDP to the server ifself from itself, You should get a login prompt but give an error that you cannot login to a logged in server.
As well, you Remote desktop settings, Are they enabled for allow all clients or only secure with NLA.
Let us know,
Hades666
you used the wrong telnet syntax
it's not colon port, it's space port
e.g.
you need to use
telnet hostname port
not
telnet hostname:port
it's not colon port, it's space port
e.g.
you need to use
telnet hostname port
not
telnet hostname:port
which is why it said it connected on port 23...
ASKER
ZShaver:
I got
C:\Users\W7>telnet My ip 3389
Connecting To my ip...Could not open connection to the host, on port 338
9: Connect failed
I got
C:\Users\W7>telnet My ip 3389
Connecting To my ip...Could not open connection to the host, on port 338
9: Connect failed
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
hades666:
I didn't have try to RDP from the server itself, I try to RDP from other computers (mine and my friend outside)
I didn't have try to RDP from the server itself, I try to RDP from other computers (mine and my friend outside)
Try it from itself. I want to see if you actually set it up correctly.
Thanks, Hades666
Thanks, Hades666
ASKER
hades666:
Good idea.
Yes, I have tried now from other compuer by local IP and it works fine
Good idea.
Yes, I have tried now from other compuer by local IP and it works fine
So RDP from a PC on the same network by local.ip.addr works.
If that is the case, your Port forwarding is the issue at the moment.
-Hades666
If that is the case, your Port forwarding is the issue at the moment.
-Hades666
ASKER
I willt leave to test in other network,
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I guessed it, I have tested the server and router at my home are work.
So I think, it's building network security
Thanks guys for help
So I think, it's building network security
Thanks guys for help
if there is any firewall software on the server you need to open up port 3389 in that aswell