Connection problems using Web

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

Guest

I'm trying to connect to my home XP Pro PC from work using IE5. The home PC has IIS installed and I've forwarded 3389 and 80 on my Netgear DG834 router to the 198.168.0.2 address given from the ipconfig command. I've allowed users to connect remotely from the Systems Properties. The connection uses ICF but I've checked the boxes on the advanced settings for Remote Desktop and Web Server (HTTP).
From work I call the router IP address and get the MS Remote Desktop Web Connection screen. I leave the server field blank and simply click on connect and I get the message "The client coud not connect to the remote computer. Remote connections might not be enabled.....etc etc."
I've scanned this Newsgroup for hours and can't work out what I'm doing wrong.
Can anyone help...please
 
In the "server" field, I think you'll need to enter the public IP address of
your router....

If you have another computer on your home network, have you tested RD
connections from inside the LAN?

Not sure if the fact that you're running IE5 will cause problems as well -
any reason you aren't on IE6 SP1?
 
I've tried the router IP address, local IP address, server name and it still comes up with the same message. Unfortunately I don't have another pc inside the network to test. As far as IE5 is concerned, this is the standard build at work and there's nothing I can really do about that (much to my frustration
I've even read through one of those massive "War & Peace" size manuals on XP and I'm stil none the wiser
 
Try connecting using the normal Remote Desktop client, ie. not the web based method. If you can't
connect test with this telnet test...You need to test this from a remote location or dial into the
internet using a laptop, etc.

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

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

Mal said:
I've tried the router IP address, local IP address, server name and it still comes up with the
Click to expand...
same message. Unfortunately I don't have another pc inside the network to test. As far as IE5 is
concerned, this is the standard build at work and there's nothing I can really do about that (much
to my frustration)
I've even read through one of those massive "War & Peace" size manuals on XP and I'm stil none the
Click to expand...
wiser
 
Troubleshoot first by using just the plain remote desktop client...
The web client adds a level of complexity... See if you can connect
directly using just the plain client, and then we can see if there are
other issues...

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
Actually, no... This is a known bug of the web client...

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
I am currently experiencing the same situation as Mal. My difference is I am trying to connect from a remote location to my internal corporate network using IE6. I am currently attempting to utilize the Remote Desktop Web Connection. Our employees will connect to different sets of terminal servers depending on geographically where their home office is. I am able to connect with remote desktop to one server and telnet with port 3389 works also. I can complete this with both the name space and IP. When connecting to the Web Connection from the inside all tends to work, but of course I am translating to an internal address on the local LAN. Still seems like I am missing something on the firewall. I am currently running Cisco Firewall with NAT. Is there a fix or a workaround for the known issue with the web interface?
 
Is TCP Port 80 (IIS) open in the firewall? Since you can connect from a remote location with the
Remote Desktop client the only thing left is the IIS port.

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

Erick said:
I am currently experiencing the same situation as Mal. My difference is I am trying to connect
Click to expand...
from a remote location to my internal corporate network using IE6. I am currently attempting to
utilize the Remote Desktop Web Connection. Our employees will connect to different sets of terminal
servers depending on geographically where their home office is. I am able to connect with remote
desktop to one server and telnet with port 3389 works also. I can complete this with both the name
space and IP. When connecting to the Web Connection from the inside all tends to work, but of
course I am translating to an internal address on the local LAN. Still seems like I am missing
something on the firewall. I am currently running Cisco Firewall with NAT. Is there a fix or a
workaround for the known issue with the web interface?
 
In reading some of the other post, I am seeing some replies to questions similar to this stating to just hit connect and it will connect you to a server. Yes this is true in my case, but it hooks me directly to the computer that has IIS running. In my case I need for different groups to hook to a different server. Any other directions of assistance would help? I think there are many people with the same issue. ----- Erick wrote: ----

Yes, port 80 is open. I get the web interface but cannot connect to a server when asking which server

----- Sooner Al wrote: ----

Is TCP Port 80 (IIS) open in the firewall? Since you can connect from a remote location with th
Remote Desktop client the only thing left is the IIS port

--
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.co
This posting is provided "AS IS" with no warranties, and confers no rights..

Erick said:
I am currently experiencing the same situation as Mal. My difference is I am trying to connec
Click to expand...
from a remote location to my internal corporate network using IE6. I am currently attempting t
utilize the Remote Desktop Web Connection. Our employees will connect to different sets of termina
servers depending on geographically where their home office is. I am able to connect with remot
desktop to one server and telnet with port 3389 works also. I can complete this with both the nam
space and IP. When connecting to the Web Connection from the inside all tends to work, but o
course I am translating to an internal address on the local LAN. Still seems like I am missin
something on the firewall. I am currently running Cisco Firewall with NAT. Is there a fix or
workaround for the known issue with the web interface
 
In this case, specify the "public" ip address of the machine you want
to connect to... Please note that you will not be able to connect to
any other computers behind your firewall... In this case, you would
need to forward additional ports and re-write the web client to refer
to the new ports..

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
Back
Top