Search results for query: *

I'll assume that you are using RRAS and AD to do your VPN. The authN is going to be with the user's credentials as they are in your domain. So, it really doesn't matter wha the SID of the user or the computer at the remote is - the authentication is going to be for the username and password AS...

Check here. This will greatly ease your pain - and, it works pretty well, too. You will need a copy of the Win2k ResKit tools. http://www.winnetmag.com/Windows/Article/ArticleID/16252/16252.html MSServerMVP

Making them a Power User on the local workstation will give them this right, but you may not want the added baggage that this brings with it. If all that you want them to do is to beable to change the system time, then you can modify an existing GPO or create a new GPO that will grant the User...

Firstly, let me see if I understand: You've upgraded a DC to Server 2003 and Exchange 2003 and the PDC role still exists on a 2000 DC? (I only mention the upgrade because I've never seen this 673 issue pop up except on upgrades, interestingly enough....) If this is the case, move the PDC role...

cardiffdutch, You'll want to dril into the domain that you want to change and find the SOA record. Should be at or near the top. Right click the SOA record and bring up the properties. You will then be able to change the Serial number and the refresh interval from here. SN at the top...

hokus, TCP/IP is not a protocol that shares well with other processes on the same box. So, for all intents and purposes - you have done the correct troubleshooting and already know the answer. Port 443 can either be used by the Secure Gateway or for SSL on the Web Server. But, not both...