MSTSC problem

  • Thread starter Thread starter bobtom1
  • Start date Start date
B

bobtom1

I recently updated my firmware in my linksys wrt54g router and then MSTSC
quit working. I keep getting cannot connect to host computer error message.
I've tried rolling back the firmware and still can't connect. Now I've heard
of problems with other linksys products not being able to be configured if
you update the firmware. however I can still make changes to other programs
through my router. do you think this is a router problem. I am using xp pro
on both machines, and RDC use to work until I updated my firmware. What can I
do to try and fix this?
 
bobtom1 said:
I recently updated my firmware in my linksys wrt54g router and then MSTSC
quit working. I keep getting cannot connect to host computer error
message.
I've tried rolling back the firmware and still can't connect. Now I've
heard
of problems with other linksys products not being able to be configured if
you update the firmware. however I can still make changes to other
programs
through my router. do you think this is a router problem. I am using xp
pro
on both machines, and RDC use to work until I updated my firmware. What
can I
do to try and fix this?

So the host PC you want to remotely access/control with Remote Desktop (RDP)
is behind the Linksys router? Have you forwarded TCP Port 3389 through the
router to the static LAN IP of the host PC? Can you connect to the host PC
from another PC on the same LAN using the static LAN IP of the host PC?

--

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...
How to ask a question
http://support.microsoft.com/KB/555375
 
Sooner said:
I recently updated my firmware in my linksys wrt54g router and then MSTSC
quit working. I keep getting cannot connect to host computer error
[quoted text clipped - 9 lines]
can I
do to try and fix this?

So the host PC you want to remotely access/control with Remote Desktop (RDP)
is behind the Linksys router? Have you forwarded TCP Port 3389 through the
router to the static LAN IP of the host PC? Can you connect to the host PC
from another PC on the same LAN using the static LAN IP of the host PC?
I have changed from the default ports of 3389 and It use to work on the ports
I changed to from 3389 and now it doesn't But yes it is forwarded in my
router. and as for being able to connect to the host computer from another pc
I only have 2 pcs my laptop and my desktop which is the host, and no I can't.
 
bobtom1 via WindowsKB.com said:
Sooner said:
I recently updated my firmware in my linksys wrt54g router and then MSTSC
quit working. I keep getting cannot connect to host computer error
[quoted text clipped - 9 lines]
can I
do to try and fix this?

So the host PC you want to remotely access/control with Remote Desktop
(RDP)
is behind the Linksys router? Have you forwarded TCP Port 3389 through the
router to the static LAN IP of the host PC? Can you connect to the host PC
from another PC on the same LAN using the static LAN IP of the host PC?
I have changed from the default ports of 3389 and It use to work on the
ports
I changed to from 3389 and now it doesn't But yes it is forwarded in my
router. and as for being able to connect to the host computer from another
pc
I only have 2 pcs my laptop and my desktop which is the host, and no I
can't.

Check to see if someone has not changed the listening port back to TCP Port
3389 or to another port. Remember that you need to reboot the PC if you
change the listening port in the registry.

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

If you can't connect from another PC on the same LAN, using the LAN IP of
the host, then you will never connect from the public internet.

http://theillustratednetwork.mvps.org/RemoteDesktop/TroubleshootingDiagrams/Basic.html

Make sure the Terminal Services service is running. Also on the host PC run
the "netstat -a" command and make sure the PC is listening on the new port.

http://theillustratednetwork.mvps.o...pSetupandTroubleshooting.html#Troubleshooting

Have you added a new software firewall to the host? Are you running anything
like NAV worm protection or OneCare Live that may be blocking incoming
Remote Desktop requests? I have also seen reports that a Cisco VPN client
will block incoming Remote Desktop requests.

--

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...
How to ask a question
http://support.microsoft.com/KB/555375
 
I got it figured out thanks for your help. I never use to have to typ it in
like so xxx.xxx.x.xxx:yyyy y being port number. So I tried it that way and
now it works.
[quoted text clipped - 15 lines]
I only have 2 pcs my laptop and my desktop which is the host, and no I
can't.

Check to see if someone has not changed the listening port back to TCP Port
3389 or to another port. Remember that you need to reboot the PC if you
change the listening port in the registry.

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

If you can't connect from another PC on the same LAN, using the LAN IP of
the host, then you will never connect from the public internet.

http://theillustratednetwork.mvps.org/RemoteDesktop/TroubleshootingDiagrams/Basic.html

Make sure the Terminal Services service is running. Also on the host PC run
the "netstat -a" command and make sure the PC is listening on the new port.

http://theillustratednetwork.mvps.o...pSetupandTroubleshooting.html#Troubleshooting

Have you added a new software firewall to the host? Are you running anything
like NAV worm protection or OneCare Live that may be blocking incoming
Remote Desktop requests? I have also seen reports that a Cisco VPN client
will block incoming Remote Desktop requests.
 
Back
Top