Re: Connection problems using Web

From: Erick (anonymous_at_discussions.microsoft.com)
Date: 03/15/04 

Date: Mon, 15 Mar 2004 07:26:08 -0800

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 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" <anonymous@discussions.microsoft.com> wrote in message
          news:70D366B8-CE04-4EF1-A3D8-523C517660F4@microsoft.com...
> 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?