morellana

Is it a DC or a member server?

try running the system file checker, it may prompt for the installation cd so have it handy . sfc /scannow or try this first... on C:\program files\Internet Explorer\Setup double click on setup.exe, that will start the ie installer program and ask if you want to repair it.

kind of, if it's not in that list it will not work under windows 2003 or at least will not work properly even with the manufacturers drivers, so check for a supported before buying a new one. Mario

I'm running 9c... have you checked if the video adapter is listed in the windows 2003 catalog? If not, better be thinking of buyin' a new one, but check first if it is supported, try selling the old adapter to a friend that is running XP Mario

If they are in the same site they replicate every 15 minutes, but manually you have to go to AD Sites and Services, Select Default first Site, select the server you want to replicate from, select ntds settings and the in the connection object right click and replicate now. To save the dns config, just integrate every zone into AD, if they are already integrated, just install DNS on the other DC, because it's integrated the zone data will be replicated to the other DC within the AD Replication. To backup the DHCP there are two methods: 1. Save this Key in the original server: HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\DHCPServer highlight the Configuration key 2. Copy these files DHCP.MDB, DHCP.PAT, j50*.log in \winnt\system32\DHCP and then stop the service in the original server. 3. Install the DHCP Server in the other server, after that stop the service in the dhcp console. 4. Restore the three files (DHCP.MDB, DHCP.PAT, j50*.log) to\winnt\system32\DHCP 5. Insert the registry key you just exported to the registry in the new dhcp server 6. Start the service, authorize the server, Activate the scope if needed, then reconcile it. Method two: For me this is an easier and more effective method. the difference between this and the first one is that the first keeps the information about the leases, but if you want to do things quick and fault proof use this. in the Command prompt in the original server: netsh dhcp server dump > c:\dchpconfig.txt copy it to the same path in the new server, stop the old dhcp, authorize the new one, and then in the command line netsh exec c:\dhcpconfig.txt (to recover all, except active leases) then refresh de dhcp console. (you can use any name instead of dhcpconfig, but it must be a txt) Mario

Try with the latest XP drivers for the Video Card, it's possible that when you are installing them this system will tell you that they aren't digitally signed, but it's worth a try, i had the same problem and when i did this it worked.

check if it's enabled in the remote tab in the system properties and check if port 3389 tcp is open

When having a multiple site infrastructure AD designates a bridgehead per site, this setting is automatic by default, although you can set it manually is not recommended. This is because each bridgehead communicate with the bridgehead of the other sites in order to use efficiently the network bandwith, when each bridgehead receives the repplication data then it propagates it to the servers that are in the same site. Your PDC emu may generate outbound because it also has the RID master role. There are various reasons going through my head: 1. the pdc emu holds the GPOs, that are replicated thru the FRS, remember that when a PC boots or a user logs they poll a DC to check for the GPs, and each DC must check the GPOs with the PDC (Which holds the templates in the SYSVOL folder and that's what the FRS replicates to the other DC's) 2. The Rid master dessignates blocks of RID numbers to all servers in the domain, this numbers allows the creation of the objects of the AD, RID numbers are unique and are vital part of the SID that is generated when creatin and object. 3. the PDC holds "the last word" when authenticating a system in another DC Fails 4. It has the HOUR of the domain. Kerberos is the authentication protocol in AD so it is spread in all DCs 'cause they all can authenticate users and generate Ticket Granting Tickets to access resources on a Domain. NTLM auth is not supported by win98 only LM, win 2k and after use Kerberos, AD supports LM, NTLM, NTLM v2 and Kerberos. Mario.

try configuring the SUS server as a secure nat client, and maybe you can tell us the configuration that you made to the service in the SUS admin page

Right click the ou where the user accounts are and select "delegate control..." in the assitant select the help desk team, click next and select a common task, you should see there the "reset password" task and the user creation and management creation tasks... Mario

try this command on the laptop... it will reset the network adapter configuration in the registry netsh int ip reset anyfilename.txt then try a repair on the network adapter.

OK man, this will be long, so please read carefully: Critical updates, and other types of updates other than service packs, cannot be directly integrated into installation files. Instead, you can follow these steps to automatically apply critical updates to a newly installed computer: Open the \i386\dosnet.inf file, and add svcpack to the [OptionalSrcDirs] section. For example, this section will now contain: [OptionalSrcDirs] uniproc svcpack Note The Dosnet.inf file included with Windows 2000 already contains the [OptionalSrcDirs] section, but you might have to create the section for Windows XP and Windows Server 2003. Create a \i386\svcpack\ folder. Copy the update packages that you want to integrate, such as WindowsServer2003-KB999997-x86-ENU.exe, to the \i386\svcpack\ folder. Rename the packages to fit the 8.3 naming convention using the format KB######.exe, where ###### is the Microsoft Knowledge Base article number associated with the update. Open a command prompt, and extract each of the update packages to a unique temporary folder. For example, to extract the files for an update package to a folder named C:\ExtractedUpdates\KB824145\, type the following command at a command prompt: KB824145 /X:C:\ExtractedUpdates\KB824145\ From the Update subfolder of the folder you extracted the update to, copy the catalog file, KB######.cat, to the \i386\svcpack\ folder. Locate the binary files included with the update. Security updates, critical updates, update rollups, drivers, and feature packs for Windows contains two copies of the same files in the RTMGDR and RTMQFE folders, which were created when you extracted the update. Files in the xxxGDR folders contain only general distribution release (GDR) class fixes. Files in the xxxQFE folders are cumulative and contain both the GDR-class fixes and all previous hotfixes that affect the included binaries, and they should generally be used for integrated installations. Some updates include different versions of files to be applied to computers with different service pack levels. These files will be placed in a folder named after the next sequential service pack. For example, if your installation source is Windows 2000 Service Pack 1, you must use the files from the SP2QFE directory. For each binary file (such as .exe, .dll, or .sys files) included in the folder you extracted the update to, determine whether the same file exists in the \i386 folder. The files in the \i386 folder might have an underscore for the last character in the file’s extension. For example, Rpcss.dll is named Rpcss.dl_ in the \i386 folder. If there are two copies of a file, delete the original file from the \i386 folder. Look in the folder into which you extracted the update for any subfolders that have the same name as a subfolder of the \i386 installation folder. If a folder contains any such subfolders, copy the updated binary files to the appropriate subfolder of \i386. For example, if the update included a subfolder named Uniproc, copy the files in the Uniproc folder to \i386\Uniproc. For each file that you copied, except for KB######.cat, look in the \i386\Dosnet.inf file to determine if the file name is listed in the [Files] section. All the files that are listed in the [Files] section are preceded by “d1,”. If a file is not listed, add an entry using the format d1,filename. For example, if the update contains Win32k.sys, add d1,win32k.sys to the [Files] section of \i386\Dosnet.inf. This addition ensures that the updated versions of the files are copied during Windows setup. Delete the \i386\Svcpack.in_ file. Use Notepad to create a Svcpack.inf text file in the \i386 folder. To do so, use the appropriate following content, depending on whether you want to deploy a single update or multiple updates. Replace ###### with the Knowledge Base article numbers for your update .cat file: For Windows 2000 installations: [Version] Signature="$Windows NT$" MajorVersion=5 MinorVersion=0 BuildNumber=2195 [setupData] CatalogSubDir="\i386\svcpack" [ProductCatalogsToInstall] KB######.cat [setupHotfixesToRun] KB######.exe /Z /M For Windows XP installations: [Version] Signature="$Windows NT$" MajorVersion=5 MinorVersion=1 BuildNumber=2600 [setupData] CatalogSubDir="\i386\svcpack" [ProductCatalogsToInstall] KB######.cat [setupHotfixesToRun] KB######.exe /Z /M For Windows Server 2003 installations: [Version] Signature="$Windows NT$" MajorVersion=5 MinorVersion=2 BuildNumber=3790 [setupData] CatalogSubDir="\i386\svcpack" [ProductCatalogsToInstall] KB######.cat [setupHotfixesToRun] KB######.exe /Z /M

If you want to have multiple boot... Yes you can install windows 2000 after XP or XP after 2003, those versions work with 3 special boot files, ntldr, boot.ini, and ntdetect.com you just have to save these 3 files in a disk, usb flash key or something else, remove the hidden, system and read only attributes before beggining the installation of the older OS, after you finish installing win 2000 copy back the files you just saved and voila!, oh, and don't forget to edit the boot.ini file so that it includes the list of OS and where (the partition or disk) the system has to go to load them. Just wanted to share this information with you all. Mario.

probably the domain you're member of has a trust relationship established with other domain, that's the reason when you see more than one domain in the logon to box.

Why should you use a Sound Card on a Server???? is it a streaming media server or something like that?