Home Forums AC on it's own server?

First, your computer's will have their same IP address, subnet mask, and default gateway along with their DNS whether the server is up or not. Now, the DNS on the computers will allow the clients to route to the server and access the ISP via the port forwarders. Now, if your server is down, it cannot do this, but your clients (all done via wizards). The only way for a client to know how to get to an ISP would be to have that IP in their DNS. This would mean that DNS would not be the server IP, which it should be IF the clients are going to access the server.

In reading on TechNet, it talks about exactly what you were saying. Thus the server would have to actually get its IP address from the router. This also makes the DNS issue problematic since if the server's IP (let's say 192.168.1.2) changes as it receives different IPs from the router (not that often), the DNS on each client, x.2 will not find the new IP address. The article goes on to say how Microsoft changes this by having the server match up DNS IPs.



This is the typical setup. You have the server IP at the top with 192.168.1.2, the subnet mask, telling the computer which of the octets to look at, the default gateway, which is identical to the inside private address of the router, and the DNS which is always the same as the server IP. In the scenario of the router, it would provide the settings to ALL computers, including the server on this 1.x subnet. The only difference would be that the server's IP would be dynamic. Not sure the advantage. I would have a hard time allowing it, my hands would shake, and I wouldn't sleep at night. Getting to the Internet seems like a very small advantage, and I am still trying to see why you could unless the port forwarders were there.

As to UPnP issue, I am not sure why it is behaving that way. I think it is trying to access it automatically and, for whatever reason, is not. You must have a compatible router, http://go.microsoft.com/fwlink/?LinkID=168957 although it does say it is enabled. There are many articles online which talk about doing it manually. Don't worry, it only took me two months to set up RWW, but that was a Cisco PIX command line issue.

You don't need a website, you need a public SSL certificate so that computers trying to access RWA, will know it can trust it. Sandeep stated 2011 will provide one for you. If so, you may have already installed it. Otherwise, you would need to purchase one for your server.



They are basically the same thing except RDC is a simple program to allow access and allows it quickly and securely. All computers must be enabled if you wish to access it, so you need to check the server under System Properties | Remote. Remote Web Access is a much more robust program allowing you to access the server and then access any computer you have permissions for. In 2011, you can now set up your view and make Remote Web Workspace so that you have quite a few things at your fingertips.