Questions

Problem with Remote Desktop web Connection

Tags:
+
0 Votes
Locked

Problem with Remote Desktop web Connection

saifoelbahri
hi,
I have problem to remote desktop web connection.
my office using ADSL Modem Ovislink ARM-104 to connect the internet and sharing to all user.
All user using windows xp Professional.
My ISP gived to my company just 1 IP public.
I just able to remote dekstop web connection user's computer on internal network, but when i remote from outside through internet its doesn't work. There is message "the specified remote computer could not be found. verify that you have typed the correct computer name or ip address, and then try connection again."
I have install IIS and setting port at windows firewall to be able remote desktop.So how to remote desktop user's computer from outside through internet.Is it the router problem?
please help....
sorry if my english not fluent..

thank in advance
  • +
    0 Votes
    scott_heath

    It sounds like a near consumer level router. To be honest I think what you should use is a VPN connection if you want to Remote Desktop to several PCs, but ehre is your alternative. You choose one system that you want to Remote Desktop then you forward TCP 3389 on the router to the IP of that system. Once you have gotten control of that desktop you can then Remote Desktop to other PCs in the company.

    +
    0 Votes
    saifoelbahri

    Ok thanks Scott for your Suggestion.
    the problem is.. My internet server still windows 2000 Professional, it cannot to remote. or i have to convert to windows Xp prof first..
    i appreciate your time to writed down this
    sorry my english not fluent

    ifoel

    +
    0 Votes
    scott_heath

    Windows 2000 Professional, not Server? You can forward packets coming to port TCP 3389 to any PC on your network, it doesn't have to be the IIS server. Is this how you network is setup?

    Internet -> Firewall/Router -> Internal Network

    +
    0 Votes
    saifoelbahri

    Hi Scott
    Yes you are right, Windows 00 prof is not Server.
    i just want to explain how the flow my network. First internet getting down from ISP and connect to Adsl Modem Ovislink, from Modem connect to one PC with system Windows 2000 Prof. from PC connect to Switch. Maybe u have question why not directly sharing from ADSL Modem to user? because that modem just have 4 ports..its not enough, coz so many user in my office.
    so from switch we sharing to all user.. each user getting gateway with IP windows 00 prof and DNS from ISP.
    is it clear.. or u have sugestion with my probelm..
    the problem with the router modem. i able log on to setup router modem. i just dont know where a part to change.I have canged NAT router forward port 3389, and forward port 3389 each user.. but stil not work..

    any idea scott
    thanks in advance

    +
    0 Votes
    3xp3rt

    Your problem is the following:
    You can?t make a VPN connection to your LAN, because there is no domain.
    For making a remote desktop connection you must be a member of the LAN.
    The other way is forwarding the RDP port on your router. For detailed suggestion see the following Q&A: http://techrepublic.com.com/5208-6230-0.html?forumID=101&threadID=205763

    +
    0 Votes
    saifoelbahri

    Hi 3Xp3rt
    thanks alot for your atantion
    i awill find out and pay atantion for your advice.
    if you dont mind, whould you give me the link user's guide all about setup VPN windows xp prof.
    for you know. i have tried forward port 3389 in firewall user and router but it doesn't work.
    my ip public is 222.124.XX.XX and my private IP is 192.168.X.XXX. is it right when i remote follow this : IP_Pulic:number_Port or IP_private:number_Port?

    sorry i beginner to do this

    thanks in advance

    +
    0 Votes
    3xp3rt

    Where is not server or domain, just a router, depending on type of router you can use the following technique: The router has a public IP address, and the computers have some 192.168?.. address. So you can set all this 192.168? IP?s on the router with port range start at 3389 and end at 3389 (RDP port). When you enable one of the 192.168?IP on port range forwarding (or depending on type of router Application, or Gaming) and save these settings, you can connect via RDP to that computer using the public IP address.

    +
    0 Votes
    iceblast21

    What I don't get is why no tech article ANYWHERE is giving accurate, complete advice!

    I have the host computer with Remote Desktop enabled. I have forwarded the correct port. But I still cannot connect to the host computer!

    From what I understand, you need 1 of 2 things for Remote Desktop:

    A) A VPN, which features the most secure, most direct method of connection.

    or

    B) An actual website hosting the "tsweb" webpage, with which you could enter: IP_address:Port/tsweb/ to connect to the PC!

    Is this accurate??? All of the online resources simply tell you to install Remote Desktop, enter the IP, and BAM! You're connected. But this is ridiculously inaccurate and misleading!

    +
    0 Votes
    scott_heath

    If you have the web service for remote desktop you can use a web browser to hit the http://computername/tsweb but if you are using the standard Remote Desktop connection client that is not necessary. Obviously web connection will use Port 80 for HTTP but standard connections are made over TCP Port 3389.

    +
    0 Votes
    iceblast21

    That information is really the same I've found all over the web! I appreciate the effort, but I still don't understand what it's trying to tell me...

    Do you need a VPN for Remote Desktop?

    I think you need to host a website to use Remote Desktop Web, or you need a VPN to use the regular R.D.!

    I have neither of those set up right now, so I am having trouble using Remote Desktop. After over a week of research, I'm no where closer to figuring out the archaic program, and we've just gone with GotoMyPc. But I'd still like to know how to feasibly set up a remote connection without monthly fees.

    +
    0 Votes
    scott_heath

    Okay, so you already know the solution, so what's the question? It's not archaic but it can be complicated. If you have an internet connection then you have a firewall sitting on it stopping external communications from getting in. Forward an external port to TCP Port 3389 on the box you want to RDP. Once you are connected you can RDP to any box on your network. Or buy a hardware firewall solution from SonicWall, http://www.sonicguard.com , that has a built in VPN solution as well. Those are basic solution because it's hard to get into too many details without a full scope of what you need. Different needs obviously require different solutions. If this is a small company and you have 2 people who need to be able to RDP their desktops then I say you use two random external ports, say 45001 and 45002 and forward them to the two desktops in question. if your external IP is 169.254.1.1 and your 2 internal IPs are 10.1.1.1 and 10.1.1.2 then it would look like this:
    169.254.1.1:45001 -> 10.1.1.1:3389
    169.254.1.1:45002 -> 10.1.1.2:3389
    It's not terribly secure, but then it's not terribly insecure either. I'm sure most Security professionals would not recommend it though.

    If you have 15 people who need RDP access then if it's still a small company without a CCNE on hand then buy a SonicWall router with the necessary VPN connections. This may require some configuration to ensure your network remains secure. VPN access would be the preferred mode of connectivity because of it's secure communications and login procedures before you even get to the RDP.

    If this is a large company with 30+ people needing this sort of access I would bring in a company that handles VPN implementations to help you.

    Regardless of the solution you go with you WILL have to open your self to the outside world in some way. There are other technologies and products that can provide what you are looking for at varying prices and security risks and, to be honest, VPN implementation is not my forte. I have used the port forwarding technique for other small companies who wanted a zero cost solution (well besides my fee). I have also brought in SonicWall routers for companies that didn't mind spending a few grand and really wanted VPN connectivity for RDP, Exchange, and Files System access. You can also create yourself a DMZ for internet facing applications such as this, but then you need someone who really understands routing to ensure that no unwanted traffic makes it's way out of the DMZ onto your network. It can be a serious security risk.

    Anyway, I hope this sheds a bit more light on the topic. Good luck to you.

    +
    0 Votes
    iceblast21

    It's so hard to tell what I'm communicating accurately, and what people are perceiving accurately.

    Thusly, I should tell you the RD works great WITHIN the network. But I am trying to access the network from the outside.

    In that case, the RD is simply not responding. I was thinking I needed to host some website as a portal into the network, because I simply cannot access the computer any other way.

    My original idea was to access the external IP of the ROUTER, plus the open port, and in that way FORWARD the connection to the internal PC. So the web address would be External_IP_of_ROUTER:3389/tsweb. But this didn't work. And RD couldn't connect directly to it either (using the RD program and not IE).

    We have a small company with only 2-3 computers needing remote access. And right now, I'd be happy with just 1 computer with remote access.

    So how can I create a remote connection, from the outside, that can go into the computer I want to remotely connect. I don't care to necessarily connect to and access the server (though I trust that's not exactly something I can option out of).

    I just don't get the problem: 3389 is being forwarded, and I get no connection from the outside... I should be typing in the External IP of the router, plus the :3389, right?

    +
    0 Votes

    Yes

    scott_heath

    If the router is configured to forward port TCP 3389 requests to an internal IP then yes it should work by opening the RDP program and entering the router's external IP address. TSWEB uses port 80 because it is HTTP. If you want to use the web interface then you need to forward port 80 reguests to port 80 on the internal PC. What kind of router is this? Do you have multiple internal networks? Is there any other firewalls?

    +
    0 Votes
    iceblast21

    I tried connecting remotely using the method you described, but I had no luck.

    I'm using a Netopia Cayman Router, with a Dell unmanaged Network Switch. Does my PC need to be connected directly INTO the Netopia Router for this to work???

    We have only one network here, and a firewall from Symantec (which is located on the network Server).

    +
    0 Votes
    scott_heath

    If port forwarding is not working for you there could be a number of reasons. Depending on the complexity of your network setup another firewall or router could be set to block that type of communication. The short answer is: VPN or HTTP is not a required part of the RDP solution. The exception is: Everything depends on your network environment.

    Use a sniffer to see what is happening to the packets. Or just go with the SonicWall solution I mention in my other posts. It gives you a secure VPN to work with and I bet you can get what's needed for under $2000. if the expense it to high then give some more details and we'll see what we can do.

    +
    0 Votes
    iceblast21

    We're paying $20 a month for GotoMyPC, and this is a small company. What benefit is there to paying the $2000 up front? Does it handle a lot more computers?

    Thanks for all of your suggestions! I really appreciate it!

    +
    0 Votes
    scott_heath

    That would handle 50 VPN connections. You can get a decent 10 person VPN router from SonicWall for under $400. It just depends on your needs.

    +
    0 Votes
    iceblast21

    I only need 2-3 connections anyways, so a 10 connection system for under $400 would be GREAT! I work for a small company, with maybe 10 computers total.

    I will look into SonicWall for this. Thanks for all the help!!!

    +
    0 Votes
    iceblast21

    Courtesy of PCWorld... "LogMeIn"

    A free program that does the same basic thing as GoToMyPC. Also has an upgrade that you pay for (but way cheaper than GoToMyPC).

    I might try that program out and forego this headache...

    As far as I know, we have no firewalls set to automatically block out remote access. But then again, I didn't set up the network, nor am I a network expert. I just know that Remote Desktop has proven to be incredibly difficult to get going.. (although I can run it fine from WITHIN the network).

    Thanks for the help (how do I thumb you??? I can't find the link!)!

    +
    0 Votes
    scott_heath

    I don't know how to rate a post. I've not asked a question here yet. I would think it would be on the post that you found helpful.

    BTW, I'm not sure what ports the client portion of LogMeIn is listening on, but if you firewall is blocking 3389, I bet it's blocking twhatever LogMeIn uses as well. It would be horribly insecure to just have all sorts of ports open. Standard setup is everything closed then open what you need.

    Some products get around this by initiating a connection from the client to the server via port 80 which firewalls will allow outbound. Then the "server" you access via your web browser at the remote location uses the existing connection to communicate on port 80 with the client. Yahoo messenger used port 80 which made it a favorite over MM, AIM, or ICQ for people who like to IM at work.

    +
    0 Votes
    iceblast21

    I wouldn't want to leave all ports open in any way, so I do exactly what you mentioned: open ports as necessary. But when I opened port 3389, I still couldn't get XP's Remote Desktop to work... even though the port-forwarding thing should have worked...

    In any event, the program proved unwieldy and we just went with GoToMyPC! But I'd like to experiment with LogMeIn just as soon as I find some time to get to that. The tip was from PCWorld, so it has to have some legitimacy to it, right?

    +
    0 Votes
    yurki3

    Hi there all readers.. i signed up to techrepublic just because i wanted to reply to this thread.
    I cant understand though why there is no reply button in every post. =/

    Anyhow, i have few things in my mind.. . .
    One is that i have used year or two home switch/router (Linksys BEFSX41) which says i is also VPN endpoint..
    (There's also possibility to use DMZ networks.)
    And Linksys was quite cheap when i bought it, about 60€ i think.

    Officially im am IT-professional, having certificates etc. but i have found this topic being tricky one aswell.
    It's possibly because you don't need to do this very often unless you are doing it for living allready.. meaning helpdesk/consulting etc.

    Iceblast mentioned TSWEB couple times, and seemed like he was little confused about it.
    It does not actually need hosting/creating websites or skills to do that.
    TSWEB installs from: RUN -> appwiz.cpl -> windows components -> IIS -> World Wide Web Service -> Remote Desktop Web Connection.

    And it does its 'site' automatically, only what is needed to configure there is port if one wants to change it.

    It's annoying how this things can't be tested unless going elsewhere and try to connect, to just notice that it isn't working.
    Then goes couple months when remembering this thing again, do something to it and go to test again and so on.
    It's couple years now when i have been trying to solve this issue.

    Like someone said, WEB is full of information but accurate enough instructions are still hard to find.
    Maybe it is unclear for real experts to understand what is unclear to less pro users.. . . =P

    +
    0 Votes
    davidfc

    I was confused about this too. Seems there is Remote desktop and remote desktop web. What this person wants to do is the second, which is simpler than configuring domains remotely. This linked article got me up and running:
    http://www.microsoft.com/windowsxp/using/networking/expert/northrup_03may16.mspx

    Now if I could only figure out how to print with this like I could with Gotomypc....

    +
    0 Votes
    scott_heath

    I'm glad my advice could be of some help. Feel free to rate my answer as helpful so I can get another little thumbs up thingy.

    +
    0 Votes
    dinass

    my client computers are unable to connect to the remote computer, whenever i try connecting they tell me "if the the server is already logged on if the client should log on, the server have to logoff" and if i click on yes to log on the server will just log off and the client get connected so please i need help on this issue.

    +
    0 Votes
    iceblast21

    What I don't get is why no tech article ANYWHERE is giving accurate, complete advice!

    I have the host computer with Remote Desktop enabled. I have forwarded the correct port. But I still cannot connect to the host computer!

    From what I understand, you need 1 of 2 things for Remote Desktop:

    A) A VPN, which features the most secure, most direct method of connection.

    or

    B) An actual website hosting the "tsweb" webpage, with which you could enter: IP_address:Port/tsweb/ to connect to the PC!

    Is this accurate??? All of the online resources simply tell you to install Remote Desktop, enter the IP, and BAM! You're connected. But this is ridiculously inaccurate and misleading!

    +
    0 Votes
    scott_heath

    I'm glad my advice could be of some help. Feel free to rate my answer as helpful so I can get another little thumbs up thingy.

    +
    0 Votes
    dinass

    my client computers are unable to connect to the remote computer, whenever i try connecting they tell me "if the the server is already logged on if the client should log on, the server have to logoff" and if i click on yes to log on the server will just log off and the client get connected so please i need help on this issue.

  • +
    0 Votes
    scott_heath

    It sounds like a near consumer level router. To be honest I think what you should use is a VPN connection if you want to Remote Desktop to several PCs, but ehre is your alternative. You choose one system that you want to Remote Desktop then you forward TCP 3389 on the router to the IP of that system. Once you have gotten control of that desktop you can then Remote Desktop to other PCs in the company.

    +
    0 Votes
    saifoelbahri

    Ok thanks Scott for your Suggestion.
    the problem is.. My internet server still windows 2000 Professional, it cannot to remote. or i have to convert to windows Xp prof first..
    i appreciate your time to writed down this
    sorry my english not fluent

    ifoel

    +
    0 Votes
    scott_heath

    Windows 2000 Professional, not Server? You can forward packets coming to port TCP 3389 to any PC on your network, it doesn't have to be the IIS server. Is this how you network is setup?

    Internet -> Firewall/Router -> Internal Network

    +
    0 Votes
    saifoelbahri

    Hi Scott
    Yes you are right, Windows 00 prof is not Server.
    i just want to explain how the flow my network. First internet getting down from ISP and connect to Adsl Modem Ovislink, from Modem connect to one PC with system Windows 2000 Prof. from PC connect to Switch. Maybe u have question why not directly sharing from ADSL Modem to user? because that modem just have 4 ports..its not enough, coz so many user in my office.
    so from switch we sharing to all user.. each user getting gateway with IP windows 00 prof and DNS from ISP.
    is it clear.. or u have sugestion with my probelm..
    the problem with the router modem. i able log on to setup router modem. i just dont know where a part to change.I have canged NAT router forward port 3389, and forward port 3389 each user.. but stil not work..

    any idea scott
    thanks in advance

    +
    0 Votes
    3xp3rt

    Your problem is the following:
    You can?t make a VPN connection to your LAN, because there is no domain.
    For making a remote desktop connection you must be a member of the LAN.
    The other way is forwarding the RDP port on your router. For detailed suggestion see the following Q&A: http://techrepublic.com.com/5208-6230-0.html?forumID=101&threadID=205763

    +
    0 Votes
    saifoelbahri

    Hi 3Xp3rt
    thanks alot for your atantion
    i awill find out and pay atantion for your advice.
    if you dont mind, whould you give me the link user's guide all about setup VPN windows xp prof.
    for you know. i have tried forward port 3389 in firewall user and router but it doesn't work.
    my ip public is 222.124.XX.XX and my private IP is 192.168.X.XXX. is it right when i remote follow this : IP_Pulic:number_Port or IP_private:number_Port?

    sorry i beginner to do this

    thanks in advance

    +
    0 Votes
    3xp3rt

    Where is not server or domain, just a router, depending on type of router you can use the following technique: The router has a public IP address, and the computers have some 192.168?.. address. So you can set all this 192.168? IP?s on the router with port range start at 3389 and end at 3389 (RDP port). When you enable one of the 192.168?IP on port range forwarding (or depending on type of router Application, or Gaming) and save these settings, you can connect via RDP to that computer using the public IP address.

    +
    0 Votes
    iceblast21

    What I don't get is why no tech article ANYWHERE is giving accurate, complete advice!

    I have the host computer with Remote Desktop enabled. I have forwarded the correct port. But I still cannot connect to the host computer!

    From what I understand, you need 1 of 2 things for Remote Desktop:

    A) A VPN, which features the most secure, most direct method of connection.

    or

    B) An actual website hosting the "tsweb" webpage, with which you could enter: IP_address:Port/tsweb/ to connect to the PC!

    Is this accurate??? All of the online resources simply tell you to install Remote Desktop, enter the IP, and BAM! You're connected. But this is ridiculously inaccurate and misleading!

    +
    0 Votes
    scott_heath

    If you have the web service for remote desktop you can use a web browser to hit the http://computername/tsweb but if you are using the standard Remote Desktop connection client that is not necessary. Obviously web connection will use Port 80 for HTTP but standard connections are made over TCP Port 3389.

    +
    0 Votes
    iceblast21

    That information is really the same I've found all over the web! I appreciate the effort, but I still don't understand what it's trying to tell me...

    Do you need a VPN for Remote Desktop?

    I think you need to host a website to use Remote Desktop Web, or you need a VPN to use the regular R.D.!

    I have neither of those set up right now, so I am having trouble using Remote Desktop. After over a week of research, I'm no where closer to figuring out the archaic program, and we've just gone with GotoMyPc. But I'd still like to know how to feasibly set up a remote connection without monthly fees.

    +
    0 Votes
    scott_heath

    Okay, so you already know the solution, so what's the question? It's not archaic but it can be complicated. If you have an internet connection then you have a firewall sitting on it stopping external communications from getting in. Forward an external port to TCP Port 3389 on the box you want to RDP. Once you are connected you can RDP to any box on your network. Or buy a hardware firewall solution from SonicWall, http://www.sonicguard.com , that has a built in VPN solution as well. Those are basic solution because it's hard to get into too many details without a full scope of what you need. Different needs obviously require different solutions. If this is a small company and you have 2 people who need to be able to RDP their desktops then I say you use two random external ports, say 45001 and 45002 and forward them to the two desktops in question. if your external IP is 169.254.1.1 and your 2 internal IPs are 10.1.1.1 and 10.1.1.2 then it would look like this:
    169.254.1.1:45001 -> 10.1.1.1:3389
    169.254.1.1:45002 -> 10.1.1.2:3389
    It's not terribly secure, but then it's not terribly insecure either. I'm sure most Security professionals would not recommend it though.

    If you have 15 people who need RDP access then if it's still a small company without a CCNE on hand then buy a SonicWall router with the necessary VPN connections. This may require some configuration to ensure your network remains secure. VPN access would be the preferred mode of connectivity because of it's secure communications and login procedures before you even get to the RDP.

    If this is a large company with 30+ people needing this sort of access I would bring in a company that handles VPN implementations to help you.

    Regardless of the solution you go with you WILL have to open your self to the outside world in some way. There are other technologies and products that can provide what you are looking for at varying prices and security risks and, to be honest, VPN implementation is not my forte. I have used the port forwarding technique for other small companies who wanted a zero cost solution (well besides my fee). I have also brought in SonicWall routers for companies that didn't mind spending a few grand and really wanted VPN connectivity for RDP, Exchange, and Files System access. You can also create yourself a DMZ for internet facing applications such as this, but then you need someone who really understands routing to ensure that no unwanted traffic makes it's way out of the DMZ onto your network. It can be a serious security risk.

    Anyway, I hope this sheds a bit more light on the topic. Good luck to you.

    +
    0 Votes
    iceblast21

    It's so hard to tell what I'm communicating accurately, and what people are perceiving accurately.

    Thusly, I should tell you the RD works great WITHIN the network. But I am trying to access the network from the outside.

    In that case, the RD is simply not responding. I was thinking I needed to host some website as a portal into the network, because I simply cannot access the computer any other way.

    My original idea was to access the external IP of the ROUTER, plus the open port, and in that way FORWARD the connection to the internal PC. So the web address would be External_IP_of_ROUTER:3389/tsweb. But this didn't work. And RD couldn't connect directly to it either (using the RD program and not IE).

    We have a small company with only 2-3 computers needing remote access. And right now, I'd be happy with just 1 computer with remote access.

    So how can I create a remote connection, from the outside, that can go into the computer I want to remotely connect. I don't care to necessarily connect to and access the server (though I trust that's not exactly something I can option out of).

    I just don't get the problem: 3389 is being forwarded, and I get no connection from the outside... I should be typing in the External IP of the router, plus the :3389, right?

    +
    0 Votes

    Yes

    scott_heath

    If the router is configured to forward port TCP 3389 requests to an internal IP then yes it should work by opening the RDP program and entering the router's external IP address. TSWEB uses port 80 because it is HTTP. If you want to use the web interface then you need to forward port 80 reguests to port 80 on the internal PC. What kind of router is this? Do you have multiple internal networks? Is there any other firewalls?

    +
    0 Votes
    iceblast21

    I tried connecting remotely using the method you described, but I had no luck.

    I'm using a Netopia Cayman Router, with a Dell unmanaged Network Switch. Does my PC need to be connected directly INTO the Netopia Router for this to work???

    We have only one network here, and a firewall from Symantec (which is located on the network Server).

    +
    0 Votes
    scott_heath

    If port forwarding is not working for you there could be a number of reasons. Depending on the complexity of your network setup another firewall or router could be set to block that type of communication. The short answer is: VPN or HTTP is not a required part of the RDP solution. The exception is: Everything depends on your network environment.

    Use a sniffer to see what is happening to the packets. Or just go with the SonicWall solution I mention in my other posts. It gives you a secure VPN to work with and I bet you can get what's needed for under $2000. if the expense it to high then give some more details and we'll see what we can do.

    +
    0 Votes
    iceblast21

    We're paying $20 a month for GotoMyPC, and this is a small company. What benefit is there to paying the $2000 up front? Does it handle a lot more computers?

    Thanks for all of your suggestions! I really appreciate it!

    +
    0 Votes
    scott_heath

    That would handle 50 VPN connections. You can get a decent 10 person VPN router from SonicWall for under $400. It just depends on your needs.

    +
    0 Votes
    iceblast21

    I only need 2-3 connections anyways, so a 10 connection system for under $400 would be GREAT! I work for a small company, with maybe 10 computers total.

    I will look into SonicWall for this. Thanks for all the help!!!

    +
    0 Votes
    iceblast21

    Courtesy of PCWorld... "LogMeIn"

    A free program that does the same basic thing as GoToMyPC. Also has an upgrade that you pay for (but way cheaper than GoToMyPC).

    I might try that program out and forego this headache...

    As far as I know, we have no firewalls set to automatically block out remote access. But then again, I didn't set up the network, nor am I a network expert. I just know that Remote Desktop has proven to be incredibly difficult to get going.. (although I can run it fine from WITHIN the network).

    Thanks for the help (how do I thumb you??? I can't find the link!)!

    +
    0 Votes
    scott_heath

    I don't know how to rate a post. I've not asked a question here yet. I would think it would be on the post that you found helpful.

    BTW, I'm not sure what ports the client portion of LogMeIn is listening on, but if you firewall is blocking 3389, I bet it's blocking twhatever LogMeIn uses as well. It would be horribly insecure to just have all sorts of ports open. Standard setup is everything closed then open what you need.

    Some products get around this by initiating a connection from the client to the server via port 80 which firewalls will allow outbound. Then the "server" you access via your web browser at the remote location uses the existing connection to communicate on port 80 with the client. Yahoo messenger used port 80 which made it a favorite over MM, AIM, or ICQ for people who like to IM at work.

    +
    0 Votes
    iceblast21

    I wouldn't want to leave all ports open in any way, so I do exactly what you mentioned: open ports as necessary. But when I opened port 3389, I still couldn't get XP's Remote Desktop to work... even though the port-forwarding thing should have worked...

    In any event, the program proved unwieldy and we just went with GoToMyPC! But I'd like to experiment with LogMeIn just as soon as I find some time to get to that. The tip was from PCWorld, so it has to have some legitimacy to it, right?

    +
    0 Votes
    yurki3

    Hi there all readers.. i signed up to techrepublic just because i wanted to reply to this thread.
    I cant understand though why there is no reply button in every post. =/

    Anyhow, i have few things in my mind.. . .
    One is that i have used year or two home switch/router (Linksys BEFSX41) which says i is also VPN endpoint..
    (There's also possibility to use DMZ networks.)
    And Linksys was quite cheap when i bought it, about 60€ i think.

    Officially im am IT-professional, having certificates etc. but i have found this topic being tricky one aswell.
    It's possibly because you don't need to do this very often unless you are doing it for living allready.. meaning helpdesk/consulting etc.

    Iceblast mentioned TSWEB couple times, and seemed like he was little confused about it.
    It does not actually need hosting/creating websites or skills to do that.
    TSWEB installs from: RUN -> appwiz.cpl -> windows components -> IIS -> World Wide Web Service -> Remote Desktop Web Connection.

    And it does its 'site' automatically, only what is needed to configure there is port if one wants to change it.

    It's annoying how this things can't be tested unless going elsewhere and try to connect, to just notice that it isn't working.
    Then goes couple months when remembering this thing again, do something to it and go to test again and so on.
    It's couple years now when i have been trying to solve this issue.

    Like someone said, WEB is full of information but accurate enough instructions are still hard to find.
    Maybe it is unclear for real experts to understand what is unclear to less pro users.. . . =P

    +
    0 Votes
    davidfc

    I was confused about this too. Seems there is Remote desktop and remote desktop web. What this person wants to do is the second, which is simpler than configuring domains remotely. This linked article got me up and running:
    http://www.microsoft.com/windowsxp/using/networking/expert/northrup_03may16.mspx

    Now if I could only figure out how to print with this like I could with Gotomypc....

    +
    0 Votes
    scott_heath

    I'm glad my advice could be of some help. Feel free to rate my answer as helpful so I can get another little thumbs up thingy.

    +
    0 Votes
    dinass

    my client computers are unable to connect to the remote computer, whenever i try connecting they tell me "if the the server is already logged on if the client should log on, the server have to logoff" and if i click on yes to log on the server will just log off and the client get connected so please i need help on this issue.

    +
    0 Votes
    iceblast21

    What I don't get is why no tech article ANYWHERE is giving accurate, complete advice!

    I have the host computer with Remote Desktop enabled. I have forwarded the correct port. But I still cannot connect to the host computer!

    From what I understand, you need 1 of 2 things for Remote Desktop:

    A) A VPN, which features the most secure, most direct method of connection.

    or

    B) An actual website hosting the "tsweb" webpage, with which you could enter: IP_address:Port/tsweb/ to connect to the PC!

    Is this accurate??? All of the online resources simply tell you to install Remote Desktop, enter the IP, and BAM! You're connected. But this is ridiculously inaccurate and misleading!

    +
    0 Votes
    scott_heath

    I'm glad my advice could be of some help. Feel free to rate my answer as helpful so I can get another little thumbs up thingy.

    +
    0 Votes
    dinass

    my client computers are unable to connect to the remote computer, whenever i try connecting they tell me "if the the server is already logged on if the client should log on, the server have to logoff" and if i click on yes to log on the server will just log off and the client get connected so please i need help on this issue.