> Is this file server part of the domain you're talking about in another
Hmm... not sure which thread. The server in question here is part of a
> If so, you don't want to allow anonymous port 80 access.
Right, I do not.
>While you might
> be using SSL (443) to manage your routers (as you replied in a later
> post), you can change that to any port you want and properly setup SSL
> on your internal LAN side server and disable HTTP.
Sure, I can change it in the router. I'm not a web guy, so I don't know how
to setup SSL. I see the box in IIS for SSL port. How is that going to
> You can not set the port using external DNS, so, just change the router
> management port, since that would only impact you.
And that's what I don't understand about internet hosts/DNS. For example,
if I created an "A" record for "vpn", and someone setup a VPN client, they
could just put in vpn.domain.com, versus the ip address. But they wouldn't
have to specify a port number, the client takes care of that. If someone on
the internet wants to access our internal website, and it's not the default
port of 80, how does AppName.DomainName.com get forwarded to the IIS server,
if a port number isn't specified. That's what I'm hoping to get to. That
they just enter (from the internet) AppName.DomainName.com. But if a port
number isn't specified in a browser, isn't 80 assumed?