HELP Please, Please...Remote Desktop Connection

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am on the road right now trying desparetly to access my home computer with remote desktop connection and by using my ip address in the explorer address bar. It says the client could not connect to the remote computer. On the road I use a tablet pc with XP pro tablet edition, at home I have XP pro behind a Linksys router. I have RDC enabled on both, user accounts and passwords, and have forwarded port 3389 on the router. Now when I tried to add users I could only add users for RDC from the local computer, however, I am trying to connect as an administrator so that shouldn't matter as administrators automatically have access. I have pinged the home machine successfully, I have administered the router settings remotely, yet I still can not connect. I do not use ICF. The home system has a high speed connection, and right now I am connected to the hotel's high speed. How do I check if portr 3389 tcp connections are being allowed out from the remote site? I did connect to my router just now and it seemed fine. I even tried briefly without the firewall and opening all ports, still nothing.
 
Presuming you tested this on your home LAN before traveling its possible the router is not
forwarding correctly. Use this telnet test to further isolate the problem...

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q187628

Personally, I think its doubtful the hotel is blocking TCP Port 3389 outbound, but of course
anything is possible. Can you call the help desk for the hotels broadband provider to see what they
say?

If you had access to a dialup connection to the public internet using your Tablet PC and could
connect to your home PC via Remote Desktop then obviously that would indicate the hotel ISP is
blocking the port outbound.

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...

BIGROCK said:
I am on the road right now trying desparetly to access my home computer with remote desktop
Click to expand...
connection and by using my ip address in the explorer address bar. It says the client could not
connect to the remote computer. On the road I use a tablet pc with XP pro tablet edition, at home I
have XP pro behind a Linksys router. I have RDC enabled on both, user accounts and passwords, and
have forwarded port 3389 on the router. Now when I tried to add users I could only add users for RDC
from the local computer, however, I am trying to connect as an administrator so that shouldn't
matter as administrators automatically have access. I have pinged the home machine successfully, I
have administered the router settings remotely, yet I still can not connect. I do not use ICF. The
home system has a high speed connection, and right now I am connected to the hotel's high speed. How
do I check if portr 3389 tcp connections are being allowed out from the remote site? I did connect
to my router just now and it seemed fine. I even tried briefly without the firewall and opening all
ports, still nothing.
 
In the router, are you forwarding by IP?

Any chance the internal local IP of the workstation has changed?
 
Thanks to all for replying thus far. Yes, I had tested the connection on my LAN and connectios were fine. I am now at a different hotel and still can't make it go. I did telnet(I really know nothin about this, so bear with me as I walk you through what I did) I ran cmd and from there typed telnet tserv 3389 and realized "tserv" was suppose to be my computer name (from system properties tab??). So I ran telnet mysystemname 3389 and received the same message "could not open connection to the host, on port 3389: Connect Failed". Then I ran cmd again with my ip address in place of computer name but forgot to add the port number and received the same message as above but the port number said port 23, then entered telnet myipaddress 3389 and received the error message as above with port 3389

In the router, are you forwarding by IP

As I can administer the router remotely I can tell you exactly what I have done
Well, seems I can't connect now, I did yesterday though. from what I remember I made traffic to 3389 forward to the internal ip address of that worksation compute

Any chance the internal local IP of the workstation has changed?

Possible, but I have been trying for months to do this. I am certain that the internal ip is the same as I last checked. I have DHCP automatically configure but I control be selecting the starting and ending range of the 2 computers behind the router, and my laptop when connected at home. I did have port 3389 forwarded to the 2 addressess of the 2 computers behind the router but I have toggled this to use just port forwarding to the one computer I want to connect to

Any ideas? On the remote tab of system properties, the select remote users option, and select locations under the advaced options I only see the local computer and not any of the workgroup computers (even when connected to the LAN) is his normal

Regards
Mar
 
You may be able to check the current IP of the workstation on the DHCP page
of the router--I can't recall what info is displayed there--not very much,
as I recall.

In a workgroup situation, security is all local--so seeing just the local
users is normal.

bigrock said:
Thanks to all for replying thus far. Yes, I had tested the connection on
my LAN and connectios were fine. I am now at a different hotel and still
can't make it go. I did telnet(I really know nothin about this, so bear
with me as I walk you through what I did) I ran cmd and from there typed
telnet tserv 3389 and realized "tserv" was suppose to be my computer name
(from system properties tab??). So I ran telnet mysystemname 3389 and
received the same message "could not open connection to the host, on port
3389: Connect Failed". Then I ran cmd again with my ip address in place of
computer name but forgot to add the port number and received the same
message as above but the port number said port 23, then entered telnet
myipaddress 3389 and received the error message as above with port 3389.

In the router, are you forwarding by IP?

As I can administer the router remotely I can tell you exactly what I have
done.
Well, seems I can't connect now, I did yesterday though. from what I
remember I made traffic to 3389 forward to the internal ip address of that
worksation computer

Any chance the internal local IP of the workstation has changed?

Possible, but I have been trying for months to do this. I am certain that
the internal ip is the same as I last checked. I have DHCP automatically
configure but I control be selecting the starting and ending range of the
2 computers behind the router, and my laptop when connected at home. I did
have port 3389 forwarded to the 2 addressess of the 2 computers behind the
router but I have toggled this to use just port forwarding to the one
computer I want to connect to.

Any ideas? On the remote tab of system properties, the select remote users
option, and select locations under the advaced options I only see the
local computer and not any of the workgroup computers (even when connected
to the LAN) is his normal?

Regards,
Mark
Click to expand...
->
 
I had my wife check myipaddress.com and everyting checked out as it was suppose to. I am using the correct ip address.
 
No - that's the Internet address. We know you have that right, 'cause you
can remote admin the router.

The question is what is the local IP address of the XP host box.

You can get that via IPCONFIG at a command prompt on the box.

Compare that with the forwarding setting in the router.
 
Bill

OK now I know what you mean and I will check when I can, but I am sure that it hasn't changed as even though I had dhcp configure the addresses, I had the settings as such that the automatic ip addresses would be (where I'd set them statically) through the paramaters of starting ip address. does that sentence make sense
After looking at the Linksys page I think that the problem may be with the selecting the option of DHCP to configure the ip addresses, even though I had the selection constrained to give me the ip address that I wanted. I have changed the system ip address to a static ip and changed some router settings(to not use DHCP as well), but there must be some other router settings that I will see when i am physicalli in front of the unit, I had made the changes I mention over the phone with my wife's help
The router is WRT54G by the way.
 
If you make the IP setting on the PC manually, these are what you need to
set:

1) IP address
2) subnet mask
3) default gateway (the router's IP address)
4) DNS server (also the router's IP address--or--your ISP's DNS server
addresses)

Missing number 3 will have negative effects!

I haven't worked with your router model, but I think it is very similar to
the BEFSR series I have worked with, in terms of these settings.
 
A coworker at my office has that router and it is very similar to the
BEFSR series....

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
Back
Top