cluberti

Pskill from sysinternals is a good kill utility as well.

Yes, and Exchange server should have valid (internal) DNS server entries configured in it's TCPIP connection settings, and the DNS server it points to should know about the domains you are hosting.

You could also try running an application called ShellExView (http://www.nirsoft.net/utils/shexview.html) - disable all non-MS extensions (they should be listed in pink or red) and reboot, and see if the problem persists. If it's an extension handler causing this, disabling via ShellExView should fix it.

Maybe I'm misunderstanding, but why would one buy an x64 version of Windows, only to run it with less than 4GB of RAM? One of the main benefits of 64bit is the ability to address large amounts of RAM...

I'd suggest doing the following at this point: http://www.msexchange.org/tutorials/SMTPDI...3-SMTP-DNS.html http://www.msexchange.org/tutorials/Diagnostics-Logging.html One (or both) should help assist you in determining why mail is not flowing at your organization.

If you're using group policy, most settings can be locked down at the GPO level, but still locking the machine down entirely will be an ordeal. Something 3rd party can help, but it might be costly per seat to license for a large enterprise. This will probably end up being a cost vs benefit thing, ultimately.

If they are WHQL drivers for XP, they'll usually work on 2K3 machines. If the drivers for XP are not WHQL, it's a crapshoot if they'll work or not (but you can always try ).

If you want to have a primary, localized internet cache that all clients will hit, you will need your clients to go through a proxy - any proxy that caches will work here, such as Squid on *nix or ISA on Windows. Do a google search for caching proxy if you want other alternatives - I'm sure there are a lot out there.

I'm not certain this is really doable - what kind of modifications do you find happen often that would bother your SOE?

If you reboot in safe mode with networking, does https work as a regular user? Also, if you disable HTTP 1.1 settings in IE tools / advanced, does the issue persist?

On both the firewall and the Linksys WAP, are you forwarding port 1723 to the RRAS server?

It's an OEM 3-pack, not retail, but it's legit. You get no (free) support from MS other than hotfixes and service packs (no phone / email support), but that's the only difference between OEM and Retail software. The three-pack is legit, and it's cheaper because it's OEM.

A little, although usually the Windows update installation is usually a red herring (it's the act of shutting down/rebooting that triggers it, not the installation of the patch - it's just that the patch was installed requiring the reboot). Why does the Windows XP CD not boot?

5.0.0 SMTP 500 reply code Most likely, a routing group error, no routing connector, or no suitable address space in the connector. (Try adding * in the address space) Perhaps posting the source output from a bounced message will give us more data to help you with? It is basically complaining that it cannot deliver for that domain, so it has to be a configuration error...

I was confused by your statement - it sounded like you were asking why profiles were not created when accounts were created. If no profiles are being created during logon, what happens when a user logs on? If you check the event viewer, what errors are you seeing after a new user logs on?

The service either detects that you do not have a burner, or that it has nothing to do. If either is the case, this is normal and not to be worried about.

It also depends on the process (game) itself - after loading the game run performance monitor and see what the process' virtual size and private bytes are - I'll bet it's rather large, and thus only active code is running in RAM, while the rest is paged out. Remember, there's more to a process than just RAM usage, and how the memory manager allocates RAM and paging space to a process depends on a lot of things. Again, short of disabling the page file altogether, your only real option is to add more RAM (or perhaps disable most other running processes, but there's no guarantee there).

I would contact the vendor of the application to see if there are any known issues - it seems like perhaps the program is making a call to a function or a device that the onboard Intel lacks, that the ATI product has (depending on which onboard intel video chip you have, it may not support DX9).

I'm assuming that you're forwarding both the PPTP port (1723) and the GRE protocol to the server running RRAS? PPTP works OK with NAT, but you must connect to the public IP address of your cable modem, and the firewall/router/whatever on the network must be passing the PPTP packets to the destination device on the network, or it won't work.

What program? The error means that the CoCreateInstance function of whatever program you're using is making a call to either a non-working device, or a device that doesn't exist. If it's happening in an application outside of Windows, then that application is to blame, not Windows. Contact the vendor of the application for a patch or update to resolve the issue, or report it as a bug.

Add more RAM? The games go through the NT memory manager, which determines where a process' virtual address space is allocated. If you're finding that the memory manager is paging out large portions of a process' virtual address space, there's likely a good reason for it. If you were to add more RAM to your machine, the games would likely have more of their allocated address space run in RAM.

Can you boot to the Windows XP CD and do a repair installation?

Is your installation CD at the same service pack level as the installed version of Windows you are trying to repair? If not, this can (and does) happen - you'll have to slipstream the disk to get it to (possibly) work, because at this point you may be screwed permanently. For reference, if the system boots in safe mode, you do NOT have to repair - a system that boots in safe mode but not regular mode has an issue with a 3rd party driver, service, or startup item, but Windows itself is fine. You could've resolved most likely by using msconfig or autoruns to disable everything and reboot.

Since Home and Pro are essentially the same OS, I'd say you at least have a good chance of it working properly in XP Home.

Profiles are created at logon, not account creation.