IIS and web RDP ports Svr 2008R2

[Dr. Pain]

Hi I hope someone can help.

Im obviously missing something totally obvious, but Im finding it hard to change the port number required to access web RDP on this server.

I change it in the IIS 7 management console, but when I put the \\servername:newport into the browser it just comes up with page cannot be found, but still works on the old port 80!

Wtf?!

This is even after restarting the website and restarting the server.

Is webRDP permanently bound to be accessed on port 80 and there is nothing you can do about it?

The other thing thats weird is that I cant connect to the webserver via its IP address, just its hostname... what on earth is going on?! I get a 404 error using the IP instead of the WSS2008R2 hostname.... Anyone got any ideas?

thanks.

 

[n30_mkii]

Why don't you share your fix encase anyone else has a similar issue, then close the thread under thread tools?

 

[Dr. Pain]

My mistake.

It still does it... Edit the bindings to change the listening port, and it makes no difference whatsoever. Still connects on port 80. Even after a site restart, webserver restart, and server restart.

No clue now! Im not really an IIS guy, more VMware.

I need to install VCenter on a box that I wish to administer via IIS Web RDP, hence needing to change the ports.

Sigh.. back to the drawing board on this one.

Its got to be something so simple.

 

[PAz]

There is a file called applicationHost.config. (%windir%\windows\system32\inetsrv\config)

Look in there, it will show the binding information for all your websites;

               <site name="test-site" id="3" serverAutoStart="true">
                <application path="/" applicationPool="test-site">
                    <virtualDirectory path="/" physicalPath="\\sharedconfig\test-sitefiles" userName="" />
                </application>
                <application path="/Content" applicationPool="test-site">
                    <virtualDirectory path="/" physicalPath="\\sharedconfig\test-sitefiles" userName="" />
                </application>
                <bindings>
             [B]       <binding protocol="http" bindingInformation="*:[COLOR="Red"]80[/COLOR]:test-site.fqdn" />
                    <binding protocol="http" bindingInformation="*:[COLOR="red"]80[/COLOR]:test-site" />[/B]
                </bindings>
            </site>

I've found IIS 7 doesn't always update the config files (and this was confirmed by my MS premier support ticket recently), so you might want to try changing the port manually in here and seeing what happens.

 

[Dr. Pain]

Yeah I see this in the file....

<site name="WebRDP" id="1">
<application path="/">
<virtualDirectory path="/" physicalPath="C:\Windows\WebRDP" />
</application>
<bindings>
<binding protocol="http" bindingInformation="192.168.0.23:555:WSS2008R2" />
</bindings>
</site>



Still connects on port 80 though!!

Madness I tell thee.

 

[two00lbwaster]

Hi there, do you have a web.config file in your site?

They usually have such settings in them too, however, they're specific to the site an override all other settings; I believe.

 

[PAz]

mmm you shouldn't be putting port info in web.config. Thats really for developer config.

(it's a good shout though, you should check it to make sure as it will win over applicationhost.config)