Remote Desktop can't connect
|
2008-04-23, 09:18 PM
If you are using a VLAN, you don't need to forward any ports for RDP. Connect to the VLAN then simply use the machine name in Remote Desktop.
Having port 3389 open is never a good idea. If you have to forward ports,you should always change it to a random port number.
2008-04-23, 09:29 PM
whurlston Wrote:If you are using a VLAN, you don't need to forward any ports for RDP. Connect to the VLAN then simply use the machine name in Remote Desktop. The VLAN is behind the router so I think I need to open the RDP port. Agreed on not using 3389, that is asking for trouble. I'm going to turn off the administrator account also if I get it working.
2008-04-24, 12:59 AM
pastro Wrote:The VLAN is behind the router so I think I need to open the RDP port.Nope. If you connect to the VLAN with a network connection, you just start the VLAN network connection. You should then be able to ping the internal IP addresses of the machines in the network o which you connected. You can use those internal IP addresses or computer names (names may require internal DNS running, I can't remember) to remote desktop to the computer. I connect to client machines this way all the time and the only ports I have forwarded on the router are 47 and 1723 for the VPN. VPN is set up through Windows 2003 Server. It saves me from having to forward ports for each machine and remembering which machines use which port. I keep my home network on a different subnet from the host locations as well just to eliminate conflicts. Home: 192.168.15.x Host locations: 192.168.1.x
2008-04-24, 01:18 AM
whurlston Wrote:Nope. If you connect to the VLAN with a network connection, you just start the VLAN network connection. You should then be able to ping the internal IP addresses of the machines in the network o which you connected. You can use those internal IP addresses or computer names (names may require internal DNS running, I can't remember) to remote desktop to the computer. I think you get in through VPN and then you are past the router and connected to your local LAN. I can connect this way to a remote machine at work via VPN. I did disconnect the router here at home and tried it directly connected to the net, no difference. I can RDP to a machine at work via VPN but I don't have a way to test if I can make a connection without VPN. I going to try and get a friend to open his up. I think the important point is that it does work to my wife's work from some places, just not my house. Strangely if I do a port scan from my work to her work, I can see 3389 is open. If I try it from home 3389 does not answer. arghh..
2008-04-24, 01:29 AM
pastro Wrote:I did disconnect the router here at home and tried it directly connected to the net, no difference... That does sound like ports being blocked. If you can find a port that they are not blocking, I would try changing it to that.
2008-04-24, 07:09 AM
just some advice from someone who's stumbled through some hindrances (most of which i created myself in the first place
 )try to find out what/where it fails, try it the most stupid way possible i.e. get a notebook at your work & try to get that to work. if it's ok, take that notebook home & try again. if it fails, it must be your router at home (or maybe some setting at the wifes work regarding source IP? like blocking dynamic IPs?), try another router if possible (at some friends or so), if you have a spare router at home, try that. i hope you get the idea 
sub Wrote:Yep, what he said. curiosity killed the cat
2008-04-24, 03:21 PM
K.S. Wrote:just some advice from someone who's stumbled through some hindrances (most of which i created myself in the first place Definitely understand the idea. I tried taking the firewall out at home. Doesn't work. Using my laptop from work - Works. Using my laptop from home - Doesn't work. Tried from a friend on Timewarner from his home, Works. Seems like the only place that doesn't work is my house..
2008-04-24, 03:40 PM
Hmm, just as a shot in the dark, in your router for port 3389 (or whatever you may be using for RD) is it set to TCP? Just trying to think of something small that might have been missed...
EDIT: Nevermind, if it connects from other sources i guess it would be fine... Sorry
----------------------
[SIZE="1"]PVRX2 1.3.11 Shuttle SG33G5 Case Core2Duo E8400 3Ghz -- 4 GB RAM Hauppauge PVR-150 Adaptec AVC-3610 Dual Tuner Onboard Intel GMA 3100 through HDMI -- 500GB 37" Westinghouse LCD (1920 x 1080p) Projects Program Image Tool[/SIZE]
2008-04-24, 04:39 PM
pastro Wrote:Using my laptop from work - Works. stupid question: you're talking about one laptop you've tried in different locations? or do you have one laptop at work and another one at home? if you're talking about the same laptop from this 2 quotes pastro Wrote:I then forwarded port 3389 on the home router. She can connect to my machine from her work to home. This would indicate the router can pass the packets ok. Tried the other direction, no go. pastro Wrote:I did disconnect the router here at home and tried it directly connected to the net, no difference.... ... i would say: search for another port to use & redirect it at wifes work, seems like something in between blocks initial handshake in her direction. sub Wrote:Yep, what he said. curiosity killed the cat
2008-04-24, 06:17 PM
K.S. Wrote:stupid question: you're talking about one laptop you've tried in different locations? or do you have one laptop at work and another one at home? One laptop couple different spots. It works when I'm at my work, it doesn't from home. I have also tried my desktop from home with no luck. Just tried from my pvr, no luck either. It's definitely something on my home end, but with the firewall out, it seems like it should work... I swear it is something on my cable modem. |
|
|
