I just wanted to make sure that I am doing this right.. I havent dont it yet. But before I try I just want some user input. Basicly all I need to do is login to my domain server from a remote client. In theory should this work? Go to remote client computer and change the dns address to the domain server static ip. then just connect to the domain the usual way? Is this correct?

Basicly all I need to do is login to my domain server from a remote client. When you say remote, do you mean outside of the LAN? As in, you wish to connect say from your home PC, across the internet to a server at your place of business. Login how? Are you trying to map a network drive to a share or do you wish to remotely administer the server?

I want to be connected to the office domain from my house. :D

forgot to add one more thing... login to the domain via roaming profile.

Assuming you're using a SOHO router that is capable of a port forward and that you're using RDC (remote desktop connection) to connect. You would first have to enable RDC connections on the target machine at work. You would then create a port forward on your router. RDC uses port 3389 so you would forward 3389 on your SOHO router and point it to the IP address of the server you wish to RDC to. My recommendation is to NOT use a roaming profile login to your domain as this would require the transfer of a lot of profile data from the server across the WAN link to your home PC. If it were me, I'd create another account on your domain for remote access that isn't roaming. This would reduce the amount of data transferred upon login to a minimum..............unless of course you want have a long slow login process when you connect remotely!?!?

It shouldnt be to slow as I do have a 21mbps downl speed and 15 up. and in total only 2 maybe 3 computers would be connected at a time.

It shouldnt be to slow as I do have a 21mbps downl speed and 15 up. I'm guessing that's at work. What do you have at home? Regardless, roaming profiles will still load VERY slowly as once you're crossing the internet, you're crossing a VERY busy network and since it's a contention based network..........well, just expect long delays at login while your profile loads. You may not believe me now, but you will. and in total only 2 maybe 3 computers would be connected at a time. 2 or 3 computers would be connected to what? You want to establish remote connections from 2 or 3 different computers outside your local network to this one server? If that's correct, you should have said so at the outset. Your original post made it sound like a single remote connection to the server. Allowing multiples will require a different method entirely. Start researching RRAS on microsofts website and also VPN's. In order to connect multiple external connections to your work network, you'll need to use one or the other method. Is this an AD integrated domain or a workgroup? Oh and if you care, the lack of capitalization is not only harder to read it's actually very unprofessional. If you wish to work in the IT industry and be taken seriously, and be seen as a professional, you should try typing with proper grammar and capitalization.