| 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 | ||
| 599304 | 2007-10-09 09:00: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. So your RTA1320 is NOT connected to the WAN port on the WRT54G? |
CYaBro (73) | ||
| 599305 | 2007-10-09 09:04:00 | No, because that didn't work when I was setting it up. Its just connected to another normal ethernet port and I set its IP outside the range of the automatically assigned IP addresses by the DHCP on the RTA1320. | WarNox (8772) | ||
| 599306 | 2007-10-09 09:39:00 | 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? YES "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." This means that your port forward is working but an issue somewhere else. When you have been trying to remote have you only been using the connection from the university? Are you an administrator their and do you have local admin rights? tsweb requires the remote desktop activex to be installed on the client. If you don't have admin rights then this could/will fail. Policies could be in place to disable ActixeX installs. The university firewall could be set block Activex downloads and also to block port 3389 going out. This could explain all your problems. Suggest you try from another PC from a network that isn't locked down. If still having trouble disable the firewall on your router. What does the event log say? What errors are there if any when you try to connect. Also check the logs on the router. |
berryb (99) | ||
| 599307 | 2007-10-09 20:55:00 | I only tried from the university yesterday, usually I've been trying other friends computers. But yes, I believe that the university routers will have Access-Lists blocking all sorts of traffic. I will have a look at the logs and see what it comes up with, if they have even been enabled. Is there any way that the WRT54G could be blocking some requests? |
WarNox (8772) | ||
| 599308 | 2007-10-10 08:29:00 | Is the firewall on the router enabled. As I have said disable this if enabled to test if it is blocking traffic. But since you have added the PC in the DMZ then nothing should be blocking it. Are the computers you are trying from have ActiveX set to enabled or prompt. They could be disabled which would block tsweb. Check the IIS logs to see what it reports at the times you try to connect. You could also try and set tsweb back to port 80 just to test. If PC still in DMZ then no other changes beside XP's firewall. |
berryb (99) | ||
| 599309 | 2007-10-13 23:54:00 | Ok so I did some more playing around and still no luck. I will check the IIS logs next. I tried fully removing the WRT54G from the network and had the computer go straight to the actual router. This still did not let me connect. I also turned off all the firewalls and the routers firewall is off. This still didn't help. Windows firewalls is off too. The activeX control was set to prompt and I accepted it so thats not the problem. The error I get is: VBScript: Remote Desktop Disconnected The client could not connect to the remote computer. Remote connection might not be enabled or the computer might be too busy to accept new connections. It is also possible that network problems are prevent your connection. |
WarNox (8772) | ||
| 599310 | 2007-10-14 00:55:00 | Dont know if this will help (www.mcse.ms) As it says on the above site The answer was pretty simple for me. I actually got it working with help from one of the other users online. You need to open port 4125 TCP to your server from the firewall to get Remote Web Workplace going. Give that a shot and I'm pretty sure it will work. If not let me know. |
Speedy Gonzales (78) | ||
| 1 2 3 | |||||