So by "access the internet" you mean "accept incoming remote desktop connections from the internet"? I'm sorry, but I am still not clear on what you are actually trying to do here. For the offsite computer - it doesn't necessarily have to be a member of your AD domain. It doesn't have to be associated with your DNS domain either. If AD authentication is required for your backup solution, I would suggest setting up a VPN for the offsite computer to connect to. Otherwise, just treat it like any other Internet host and authenticate it by whatever means your backup solution provides. The ISA server might come in handy for that.

0

ok, this is my situation. i work for a webhosting company. we have a network and domain for webhosting. now we are going to offer remote desktops. so i have created a domain for that purpose. with 1 DC, and 1-5 client pc's. all the client pc's and the DC have static ip's. now after i built the server (DC for new domain) i joined my first client pc to the domain. but it cannot see the internet. i cant get my client pc to pick up an internet connection from my DC, they just need regular web browsing access. because once my users login to their remote desktop, i need them to have internet access via a web browser. so my DC had one nic connected to a router, that is directly connected to the net. and the other nic connected to a new hub, used for the new domain. so my client pc's have one nic, and it goes to the new hub, so you see there is no direct connection for them to the internet, as there is for the DC. so how do i setup that DC to allow users on the domain internet access. what would my default gateway on the clients be? would i point the clients DFGW to the ip of the external nic on the DC? (the nic plugged into the router) now my DC having one connection the the existing router, has internet access, and is using the name servers from my existing webhosting network. and that nic has an internal static ip, the default gateway is set for the router that it is plugged into, and the name servers it points to are unix name servers we use in the webhosting network. this is how i allowed internet access to the DC. but i cant seem to configure my clients to pick up that access from the DC. now if your wondering why im doing it like this, it is for security, i can not have my remote desktop users plugged into my webhosting network. so this is where i am. trying to either use my existing dns servers (although they are unix) or make my DC also a DNS server for the new network. not sure which way to go. but falling fast. i really should have paid more attention to DNS before now. but here i am . lost. learning the hard way... :) thanks for all your help. i REALLY do appreciate it.

0

Thanks for the additional information. I think I understand what you are trying to do now. As far as I can tell, domain names and DNS have nothing to do with the problem at hand. Ignore the domain thing for now, it will just confuse the issue. Do you have public IP addresses for your client PCs? From your description it sounds like you don't. In that case, given how you have them networked, you are going to use the server (the DC) as a router. To set this up, run the Manage Your Server wizard and add a Remote Access/VPN role. This is pretty easy to do, and will result in your client PCs being able to access the Internet. Setting things up this way will make it more difficult to run remote desktop sessions on the client PCs. Without individual public IP addresses for them, you will have to use port forwarding on the DC server (which is now a router too) to make the client PCs accessible from the Internet. This will work, but it is kind of a kludge and not really the best way to do it.

0

thats EXACTLY what im trying to do,( i dont know why i couldnt form it into words, i have been fighting with this for over a week, im going insane) i need the DC to act as a router, for my client pc's . they do have public ip's, so they should be accessable from the net. meaning they are 65.82.xx.x and not 192.168.1.x, i am going to go run the Manage Your Server wizard and add a Remote Access/VPN role right now, be back in a few minutes :)

0

No problem, Eliziabeth. I call that a brain block - when I'm so focused on problem X, I can't get past it to think about problems Y and Z :) Router, not NAT server, (I don't recall offhand what these options are labelled in the wizard) is the type of remote access server you will want to configure. Good luck :)

0

well i have configured the remote access, but im not sure thats what i need. i looked into my isa server, and it is not allowing my clients, so now i have to battle with ISA 2004. shouldnt be too bad. but look for me screaming for help on the forum :) thanks again for all of your help, :) Elizabeth

0