RD Over web has problems connecting

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

Guest

I'm having problems connecting via Remote Desktop over the web. Our company
has two buildings. Location 1 is a cable line with a PIX 501 firewall, and
location 2 is DSL with a Sprint modem.

I enabled Remote Desktop Connections on a computer at location 1, added one
specific user to be authorized to connect, and set the TCP port for IIS on
that computer to 1313.

I opened up ports 3389 and 1313 on the firewall, and have static routes
configured to forward both of them to the machine I want to connect to. I
applied that ACL to the outside interface of the PIX and logged out of
Windows on the server so it doesn't ask permission when I try to connect via
Remote Desktop.

From location 2, I set up an identical username and password to the one I
permitted to access the server at location 1 with Remote Desktop.

When I go to the url http://publicIP:1313/tsweb, I get the correct log in
screen set up for location 1. Good. But when I put in the private IP address
of the machine I want to connect to, it delays and then gives me the
following error:

"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
connnections. It is also possible that network problems are preventing your
connection. Please try connecting again later. If the problem continues to
occur, contact your administrator."

- Remote connections are indeed enabled, judging by the steps I've already
mentioned completing
- The machine serves a total of one network application, which 2-3 users use
actively probably a maximum of 15% of their day.
- "Network problems" couldn't possibly be any more vague
- I've tried connecting over the course of a week
- "My administrator" is me. I've talked to tech support at Cisco to make
sure the PIX was configured correctly, however, as well as tech support from
the people who make our inventory software to make sure there are no port
conflicts. No leads from either of them. Any ideas?
 
Travis....
even though yer running xp pro on both machines, and u checked on allow
remote desktopping, and allowed the ports on both sites correctly, and told
both PCS windows firewalls to allow rdp, alot of times i've found the program
hasn't been actuated from the PC's. u need to go into control panel,
add/remove programs, add/remove windows components on the left, and go to
internet information services (iis), and then world wide web services, and
check on remote desktop web connection. you'll need to have yer xp pro disk
in for the drivers yer PC will need. reboot afterwards, and then try to
connect. also, try turning off the windows firewalls completely on both PCs
in question. try this and let me know how it goes.
 
Remote Desktop Web Connection is only a delivery mechanism for the ActiveX
RDP Client and configuration, is does NOT have to be installed on the Remote
Desktop Host. For that matter, if the remote client has an RDP Client
installed, i.e. mstsc.exe which comes with Windows XP and can be downloaded
and installed on other Win32 OS, there is no need to connect via Remote
Desktop Web Connection, i.e. you can just enter the address of the RDP Host
in your Remote Desktop Client.

The Remote Desktop Web Connection does not do any kind of routing, nor does
it connect the client to the Remote Desktop Host, it is just a webpage that
provides the client with the ActiveX Remote Desktop Client software &
connection configuration needed to connect to a Remote Desktop Host.
 
Back
Top