Forum Home
Press F1
Thread ID: 83642	2007-10-08 05:20:00	Remote Desktop :S	WarNox (8772)	Press F1

Post ID	Timestamp	Content	User
599294	2007-10-08 08:56:00	What address are you using when trying to connect remotely?	CYaBro (73)
599295	2007-10-08 20:50:00	Are you using your WAN IP Address when connecting from the net? Have you tried to Remote desktop on 3389 not using tsweb? Ping response should be enabled on the router for testing but once working doesn't have to be enabled.	berryb (99)
599296	2007-10-08 21:20:00	Got Win XP Pro on both computers. I figure firewalls are not a problem since I can remote desktop to that computer from inside my LAN. It must be some setting on my router (RTA1320) thats blocking it. Since I cannot get anyone to ping my external ip address either. I'm not nearly as smart as half you guys... but as far as I know, if you're firewalled on a LAN, doesn't the sheer fact you are on a LAN bypass 90% if not all the benefits of a firewall? Firewall imo blocks OUTSIDE network traffic... like.. not on the same IP If you can do it on your same network, that's the reason firewall isn't an issue, your other PC on the same network has the SAME IP as the PC You're attempting to work on...	DigitalMessiah (7649)
599297	2007-10-08 23:51:00	I'm not nearly as smart as half you guys... but as far as I know, if you're firewalled on a LAN, doesn't the sheer fact you are on a LAN bypass 90% if not all the benefits of a firewall? Firewall imo blocks OUTSIDE network traffic... like.. not on the same IP If you can do it on your same network, that's the reason firewall isn't an issue, your other PC on the same network has the SAME IP as the PC You're attempting to work on... You are correct that if tsweb and RDP can be accessed from within the LAN then client firewalls are not the issue. Tsweb and RDP are on different ports and two different methods of remote desktop. When the poster quotes "Remote Desktop", is it both methods or just the one they are referring to as working from the LAN? Are you trying both? You haven't changed the defualt RDP port in the registry from 3389? Seems to me to be a port forwarding issue. Maybe try and set 192.168.1.100 in the DMZ zone of the router. Also most times the port forwarding disables thoses ports on any firewall enabled on the router. I have had times I have also had to allow these ports in the firewall as well even though the manual says you don't need to. I can't remember your router model so this may or may not help.	berryb (99)
599298	2007-10-09 01:27:00	You should have to do anything with port 1987.....you need the external address, which you can get by setting up DDNS at ddns.org. From any pc outside your network, you would put in the rdp client 222.xxx.xxx.xxx (routers external facing address) the router will forward the request to the ip address stipulated.	SolMiester (139)
599299	2007-10-09 02:58:00	Well I've tried both ways, the tsweb way and the RD client way, neither works. Port '1987' I set by following this tutorial a while ago (www.microsoft.com). And no I haven't changed the port value '3389' in the registry, I checked and its still set to that. I haven't bothered with ddns/no-ip.org yet because my external IP is always the same anyway. So if I do: 60.xxx.xxx.xxx:1987 the router will forward on port '1987' and not do anything with port '3389'? and if I enter '60.xxx.xxx.xxx' in the RD client the router should automatically forward on port '3389'? Well either way isn't working and both the ports are forwarded to the correct computer. If I go to (http://www.canyouseeme.org/) and test port '3389' I get the error (I could not see your service...) but if I test port '1987' it says (Success: I can see your service on 60.xxx.xxx.xxx on port (1987) Your ISP is not blocking port 1987). I've really got no idea what else to try. oh and Im a bit skeptical about trying DMZ, because than that computer will get bombarded with all sorts of unwanted junk and not be protected at all by the router.	WarNox (8772)
599300	2007-10-09 03:55:00	See why I suggested usingTeamviewer ( . teamviewer . com/index . aspx" target="_blank">www . teamviewer . com), :rolleyes: When windows Remote desktop works it works good, but sometimes it can be a real pain in the Butt to get setup, even if "everything" is right . Team Viewer does every thing Xp remote does and more, also you can use any Windows OS . The hardest thing to setup is allowing it through your firewall . Oh and rembering your assigned user address Eg . User: 123567 :Password 1234 It also has quick support, meaning a simple exe file can be downloaded to the persons PC, they tell you the temp user numbers / password over the phone enter the details from your PC and thats it - your in after letting it through the firewall of course . Quick support gives you 5 minutes at a time, the full free version gives you 24 hours / month of actual connection time (not actual running time) Thats a fair amount of time if you think about it . I got 8 PC's in my LAN and can connect to any of them any time, from any place (as long as the internets not down) Total cost $0 . 00	wainuitech (129)
599301	2007-10-09 05:50:00	So both RD and tsweb work from the LAN? In IIS have you got any access restrictions set in directory security? This could allow access from the LAN but disallow from the router/gateway. You have got RD enabled on the PC? (silly question I know but I have to ask!) DMZ was a short term suggestion to see if it was a port forward issue or not.	berryb (99)
599302	2007-10-09 07:59:00	Yes both RD and tsweb work from the lan, that is because my router has nothing to do with it when im just doing stuff withing my lan. I tried this but deleting all the port forwarding entries. I cannot see any special access restrictions set in directory security. And RD must be enabled if I can access the computer from the LAN, mustn't it? I put up the DMZ, as '192.168.1.100', and tried RD/tsweb to the computer and no luck. I tried this from another remote desktop connection though, would that matter? I connected to the university of auckland, and then tried to remote desktop back to myself. The thing with tsweb is that the connect screen is displayed, therefore something must be working correctly. Because if I put 60.xxx.xxx.xxx:4444 (so a wrong port number, instead of '1987'), nothing is displayed. But if I use '1987' I get the webpage with the connect button displayed. wainuitech: Yes I know that the other program would probably be easier to use, but I've put so many hours troubleshooting into this that I do not just want to give up :) but probably will in the end anyway.	WarNox (8772)
599303	2007-10-09 08:26:00	Oh I forgot to mention one thing that I didn't think was relevant. But my home setup is like this: INTERNET | | RTA1320 (router) | | WRT54G (router but only used as access point) |...................................| |...................................| Laptop (can.................MainPC (trying to remote destkop to) connect to MainPC) There is nothing configured on the WRT54G, but I figured it wouldn't be blocking anything since my LAN connections work and they go through it.	WarNox (8772)
1 2 3