Can not get Remote Connection Working on XP Pro

  • Thread starter Thread starter Jack Ray
  • Start date Start date
J

Jack Ray

I have two PC connected by a linksys wireless router(WRT54G) in a
workgroup.(Computer A and computer B)

I want to set one of them up(Computer A) as a Host for a remote connection.
I could not make a connection from the outside.

I had done the following to set up the Remote Access:

I checked off "Allow users to connect Remotly to this computer" on the
Remote tab under System. remote and changed the windows firewall to allow
remote desktop.

I looked in users. There are no users setup but it shows that I already have
access since I am an administrator.

I set the port 3389 to forward to the internal ip address on Computer A on
my linksys router. I did not set up a static ip address yet on Computer
A(The address has not changed. I have not rebooted the computer.) In the
short term, I am assuming that this is not the source of my problem.

When I could not connect:

I went through the troubleshooting on the attached document.
http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html


netstat -a shows Computer A as listening to Port 3389

Port query also shows port 3389 as listening.

Telnet appears to work using the internal ip address or the computer name.
(The screen stays black and there is a blinking curser)
The instruction refer to using the Host name. (not sure what this means)


http://www.canyouseeme.org/ I receive the following error Error: I could
not see your service on xxx.x.xxx.xx on port (3389)
Reason: Connection timed out ( substituted the x's for this posting)

I receive the seame message if I try port 80.


Terminal services is running


After trying for hours to Connect Computer A, I decided to try connnecting
Computer B

I set Computer B with the same settings. Netstat -a does not show Port3389.
I did not have access to a computer from the outside so I tried a remote
connectiion from Computer A (on the same network) and was able to make a
connection from A to B.
I then checked the network cards on both machines and they were configred
the same, I also checked the local policies and they appear to be the same.
I can connect from A to B(Host) but can not connect from B to A(Host). This
seems to work no matter what setting I have on the linksys router(Port
forwarding)

I have a Cisco VPN adaptor set up on Computer A which is used to connect to
my work. I did not make any changes to that adapter. I am just mentioning
thius in case it may have a bearing on the situation.

I beleive that I am up to date with Window XP Updates.

I tried to set up Group policy for Terminal Services but this ended up
causing the "Allow users to connect Remotly to this computer" check box on
the remote tab of the sytem menu to be greyed out. I ended up changing all
the settings back to "not configured" The allow....Remote...etc" checkbox
is now available again. But the connection from B to A(Host) is still not
working)

I looked in the registry on Computer A and it does show 3389 as the value
for Remote Desktop.

I spoke with our network administrator and he told me that linksys has a
checkbox for allowing remote users in addirion to the port forwarding. I
checked all of the screens and could not find anything I am on Version
Firmware V202.2.2 for the WRT54G wireless router.


Any help in figuring this situation out would be appreciated.


Jack
 
My guess is the Cisco VPN software may be the problem on A... Can you remove
it or disable it?

Note that testing over the local LAN is only valid if you use the local
static LAN IP of the PC your trying to access/control. It is not a valid
test to use the public IP of the router.

TCP Port 80 is used by IIS if you want to use the web based Remote Desktop
method...

http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/pree_rem_bgek.asp

--

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...
 
I had the same problem in the past, even with VPN disabled it wouldn't work
so I had to remove it from the registry. To keep VPN utility I moved the VPN
entries in the registry (.../Microsoft/Windows/CurrentVersion/Run) to a
single user (not all users) and removed the entries from "all users". It
wont work if the user with the VPN is logged on, so you need to reboot
directly to the other user so be sure VPN is completly turned off.
Hope this helps, at least it worked for me.
 
jprac


Thank you for the info. I wish I had posted my question earlier. I was able
to establish a connection on my local lan.

Instead of changing my registry settings, I just stopped the Cisco Service.

The remote connection seems to be working. I will know tomorrow whem I test
it from work.

Jack
 
Back
Top