Remote Access ability suddenly stopped working

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

Guest

We've had remote access setup and working fine for more than a year but
suddenly last week our users have been unable to connect. I thought it might
have been a problem with our router so we replaced it, but we still have the
problem. I'm now wondering if maybe there was something changed in a Windows
update or something like that. Has anyone else had this problem. I'm at a
loss as to what the problem could be.
 
What's the error message?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
We've had remote access setup and working fine for more than a year but
suddenly last week our users have been unable to connect. I thought it might
have been a problem with our router so we replaced it, but we still have the
problem. I'm now wondering if maybe there was something changed in a Windows
update or something like that. Has anyone else had this problem. I'm at a
loss as to what the problem could be.
 
The message box reads as follows:

The client could not connect to the remote computer.

Remote connections might not be enabled or the computer might be too busy to
accept new connections. It is also possible that network problems are
preventing your connection.

Please try connecting again, later. If the problem continues to occur,
contract your administrator.
 
flls04 said:
We've had remote access setup and working fine for more than a year but
suddenly last week our users have been unable to connect. I thought it
might
have been a problem with our router so we replaced it, but we still have
the
problem. I'm now wondering if maybe there was something changed in a
Windows
update or something like that. Has anyone else had this problem. I'm at
a
loss as to what the problem could be.
Click to expand...


I presume your talking about XP Pro Remote Desktop?

If so can you access the PC from another PC on the same LAN using its
private LAN IP?

http://theillustratednetwork.mvps.o...andTroubleshooting.html#Test_on_the_local_LAN

If not then see this troubleshooting section...

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

If you can then make sure TCP Port 3389 is being forwarded correctly through
any firewall/router. One way to test that is run the
http://www.canyouseeme.org test from the PC your trying to connect to with
Remote Desktop.

--

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...
 
The machines we're trying to connect to are XP Pro using Remote Desktop. The
PC's are accessable to each other internally using the private LAN IP. We
did the test at canyouseeme.org on the ports we use for remote access and it
reports:

Error: I could NOT see your service on xx.xx.xx.xxx on port
(3389)/(3390)/(3391)
Reason: Connection timed out.

I'm sure this is significant, but I'm not sure why or what would cause this.

I'm now confirming all the settings as illustrated in the Remote Desktop
Setup & Troubleshooting guide you provided a link to.



:
 
This case studies may help,

The client could not connect to the remote computer Symptom: When trying to access TS/RDC, you may receive this error: The client could not connect to the remote computer. Remote connection might not be ...
www.chicagotech.net/remoteissues/rdc2.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
The message box reads as follows:

The client could not connect to the remote computer.

Remote connections might not be enabled or the computer might be too busy to
accept new connections. It is also possible that network problems are
preventing your connection.

Please try connecting again, later. If the problem continues to occur,
contract your administrator.
 
flls04 said:
The machines we're trying to connect to are XP Pro using Remote Desktop.
The
PC's are accessable to each other internally using the private LAN IP. We
did the test at canyouseeme.org on the ports we use for remote access and
it
reports:

Error: I could NOT see your service on xx.xx.xx.xxx on port
(3389)/(3390)/(3391)
Reason: Connection timed out.

I'm sure this is significant, but I'm not sure why or what would cause
this.

I'm now confirming all the settings as illustrated in the Remote Desktop
Setup & Troubleshooting guide you provided a link to.
Click to expand...

The fact that its failing the test on the canyouseeme site says to me you
don't have port forwarding setup correctly in the router...

Since you can connect locally from another PC on the network then you know
Remote Desktop is setup correctly on the 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...
 
We found the solution to our problem. Our configuration is cable modem -->
wireless router --> workgroup switch and we discovered that the internal ip
addresses in the wireless router had been reassigned and that in turn threw
off the port assignments. Once we reassigned the ports we were able to
connect.

Thank you for all of your time and advice.
 
flls04 said:
We found the solution to our problem. Our configuration is cable
modem -->
wireless router --> workgroup switch and we discovered that the internal
ip
addresses in the wireless router had been reassigned and that in turn
threw
off the port assignments. Once we reassigned the ports we were able to
connect.

Thank you for all of your time and advice.
Click to expand...


Excellent... Thanks for the feedback...

--

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...
 
Back
Top