Tom's Hardware > Forum > Windows XP > Windows XP General Discussion > Remote Desktop Browser Access Problem

Remote Desktop Browser Access Problem

Forum Windows XP : Windows XP General Discussion - Remote Desktop Browser Access Problem

Tom's Hardware: Over 1.4 million members in 6 different countries available to answer all your high-tech questions. Sign up now! Its free!
Word :    Username :           
 

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

 

I have 2 XP Computers behind a Linksys router setup for remote desktop
connections. I have UPnP forwarding enabled on my router, with Ext Port 3380
being forwarded to int. port 3389 on comptuer A, and Ext Port 3390 being
forwarded to int. port 3389 on computer B. I have no problem accessing
either computer from the outside using the Remote Desktop Client, specyfing
the port by xxx.xxx.xxx.xxx:3380 or 3390 repectively. I have installed IIS
Remote Desktop Web Connection and World Wide Web Service form the additional
componenets available. I have verified the services are started and running.
Computer A has the Web Site information setup for its internal IP addres, and
port 3380. Computer B has the Web Site information setup for its internal IP
addres, and port 3390. I cannot access either of these machines through the
a web broswer. I do know the correct syntax : http://xx.xx.xx.xxx:3380/tsweb
- however I receive the "page cannot be found" error. Can Anyone
Help??? During testing I noticed that if used Port Range Forwarding and
forwarded port 3390 on computer be to the internal IP address for computer B,
the web browser access would establish a connection, however I never got a
desktop (just a white screen), and the Remote Desktop Client didn't work
(even though I left the UPnP forwarding enabled). Any help would be greatly
appreciated. Is there any way have both the Remote Desktop Client and Remote
Desktiop Web Access work for two XP Professional computers behind a router?

Sponsored Links
Register or log in to remove.

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

 

try checking this web site out...dont know if will spark an idea of what
might be wrong but its worth a try....
http://www.microsoft.com/windowsxp [...] may16.mspx


"Jon" wrote:

> I have 2 XP Computers behind a Linksys router setup for remote desktop
> connections. I have UPnP forwarding enabled on my router, with Ext Port 3380
> being forwarded to int. port 3389 on comptuer A, and Ext Port 3390 being
> forwarded to int. port 3389 on computer B. I have no problem accessing
> either computer from the outside using the Remote Desktop Client, specyfing
> the port by xxx.xxx.xxx.xxx:3380 or 3390 repectively. I have installed IIS
> Remote Desktop Web Connection and World Wide Web Service form the additional
> componenets available. I have verified the services are started and running.
> Computer A has the Web Site information setup for its internal IP addres, and
> port 3380. Computer B has the Web Site information setup for its internal IP
> addres, and port 3390. I cannot access either of these machines through the
> a web broswer. I do know the correct syntax : http://xx.xx.xx.xxx:3380/tsweb
> - however I receive the "page cannot be found" error. Can Anyone
> Help??? During testing I noticed that if used Port Range Forwarding and
> forwarded port 3390 on computer be to the internal IP address for computer B,
> the web browser access would establish a connection, however I never got a
> desktop (just a white screen), and the Remote Desktop Client didn't work
> (even though I left the UPnP forwarding enabled). Any help would be greatly
> appreciated. Is there any way have both the Remote Desktop Client and Remote
> Desktiop Web Access work for two XP Professional computers behind a router?

Reply to Anonymous
Tom's Hardware > Forum > Windows XP > Windows XP General Discussion > Remote Desktop Browser Access Problem
Go to:

There are 774 identified and unidentified users. To see the list of identified users, Click here.

Please mind

You are about to answer a thread that has been inactive for more than 6 months.
If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.

Add a reply Cancel
Sponsored links
  • Ask the community now
  • Publish
Ad
They won a badge
Join us in greeting them