cluberti

It's a checkbox, I believe, in the Internet Connection Wizard. http://www.microsoft.com/technet/prodtechn...1.mspx?mfr=true

ICS cannot share a wireless connection, only wired. If you need to extend your WAP's range, consider Netgear's extender products, since you're already using a Netgear WAP: http://www.netgear.com/Products/PowerlineN...ts/WGXB102.aspx

How much free disk space do you have on the volumes system restore is protecting?

It should be, although power users are "almost admins", lacking only a few admin rights. If you're OK with it though, so are we .

If I wanted money, I'd be charging for this already . Keep it and spend it on a night out or something.

Either the driver isn't for your hardware, or the install was bad. I'd say it'd be better to know the exact chipset for your hardware and find the driver. Does the event log (system or application) say anything about the issue?

That's why you .zip it up - remember, all of that data is just text (the dump is binary text, but still text). It should compress at least 50%.

Are you sure you have 888111 installed?

You'll still be able to log in with a domain account, but you'll probably see trust errors if you're auditing on both the client and server, and in about 30 days it will (or at least should) stop working entirely (although the domain 'administrator' account will likely still be able to log in even after such time has passed, as it can ALWAYS log in once you've logged in once, regardless of machine state).

Very interesting indeed, although you'll want to be running SP2 on that WinXP install (and perhaps SP3 when it releases), so I'd still suggest a test with SP2 to see the differences vs SP0 on XP and SP4(5) on W2K, just in case. Your findings are about what I'd expect though, so I'm glad you did go through the test .

I meant you should be following the "Memory dump of the entire system:" section. What you did is a good first start though - we'll see what we can see from the application hang dump. Yes it is - you will need to zip everything in the "Hang Mode..." folder, as it all goes together (the log files, the dump files, and the config info in the folders).

No, you want to install updates automatically you'll have to download the update packages from microsoft and script their installation - or, configure automatic updates to download and install updates automatically (although that'll happen in the background, as will the installation).

Now it's saying it can't find a controller with a hard disk attached, so are you using a CD with the RAID controller driver integrated? If you have it in RAID, you can test this by setting the controller and drives back to standard IDE drives (no RAID arrays) and see if it picks them up - assuming it does, that's the problem.

In group policy, under Computer Configuration > Administrative Templates > Windows Components > Windows Update, there is a policy called "Allow non-administrators to receive update notifications". You have to have "Configure Automatic Updates" set to "Enabled" and have a policy set (I like to make sure that "4 - auto download and schedule the installation" is the choice for desktops set to install "0 - Every day" at "03:00"). This can be done via the registry if you don't use AD or have non-domain joined machines. The following registry modifications will configure the above settings: // Allow non-admins to see and interact with the Windows Update ballon/shield // notifications in the taskbar: Key: HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate Value: ElevateNonAdmins Type: REG_DWORD Data: 1 // Set to auto-download and install updates automatically if the user does not install // them manually before the specified time: Key: HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU Value: AUOptions Type: REG_DWORD Data: 4 // Silently install updates that do not need a reboot without prompting (install as soon // as patch installer is downloaded): Key: HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU Value: AutoInstallMinorUpdates Type: REG_DWORD Data: 1 // How frequently to check for updates in hours (the default is to set this to 0, which // checks every 22 hours): Key: HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU Value: DetectionFrequency Type: REG_DWORD Data: 1 // Enable usage of DetectionFrequency Value (above) - if set to 0, sets check for // every 22 hours no matter what DetectionFrequency is configured for: Key: HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU Value: DetectionFrequencyEnabled Type: REG_DWORD Data: 1 // Logged on user will get prompted to reboot - if set to 0, a 5 minute timer reboots // the machine once patches are installed: Key: HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU Value: NoAutoRebootWithLoggedOnUsers Type: REG_DWORD Data: 1 // Set to 1 to disable Automatic Updates Key: HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU Value: NoAutoUpdate Type: REG_DWORD Data: 0 // Time (in minutes, 1 - 60) AU should wait before installing downloaded updates after a // missed update schedule (when the machine is off or off of the network, for // example): Key: HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU Value: RescheduleWaitTime Type: REG_DWORD Data: 5 // Enable usage of the RescheduleWaitTime reg value (above). If not configured, // RescheduleWaitTime is set to 0 no matter what it is configured for: Key: HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU Value: RescheduleWaitTimeEnabled Type: REG_DWORD Data: 1 // Determines which day of the week to try and download/install automatic updates // (0 = every day, 1 = Sunday - 7 = Saturday, etc): Key: HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU Value: ScheduledInstallDay Type: REG_DWORD Data: 0 // Scheduled time of day to install updates if they are not installed manually (in 24 // hour format, 0 - 23): Key: HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU Value: ScheduledInstallTime Type: REG_DWORD Data: 3 // If UseWUServer is set to 1, the WUServer and WUStatusServer values // that point to a WSUS server are used. If set to 0, windowsupdate.microsoft.com // is used as the autoupdate point: Key: HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU Value: UseWUServer Type: REG_DWORD Data: 0 If you do set up your own WSUS server (and I would suggest you consider it), you can use the following two values to use the WSUS server instead of Wndows Update: // This value contains the http://server.domain.com FQDN for your WSUS // server: Key: HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate Value: WUServer Type: REG_SZ Data: http://<fqdn for your WSUS server> // This value contains the http://server.domain.com FQDN for your WSUS server // (same as WUServer value): Key: HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate Value: WUStatusServer Type: REG_SZ Data: http://<fqdn for your WSUS server>

Well, first is you're running the SP3 beta. Second, your video driver is making a call to dxg.sys (directx graphics driver) with what appears to be a bad parameter, causing win32k.sys to crash and the machine to bugcheck. I'd say your video driver doesn't work properly with SP3 . 1: kd> vertarget Windows XP Kernel Version 2600 (Service Pack 3.3264) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 Debug session time: Thu Jan 17 16:06:23.015 2008 (GMT-5) System Uptime: 0 days 0:32:19.730 1: kd> kb ChildEBP RetAddr Args to Child WARNING: Stack unwind information not available. Following frames may be wrong. ab6179c0 bf008af2 e1330080 e645b754 ab6179fc win32k+0xaf5d9 ab617a08 bf009033 00000001 e54e1008 ab617a90 dxg+0x8af2 ab617a24 bf892266 e645b008 00000001 e12f4008 dxg+0x9033 ab617a44 bf8acbeb 00000000 e1b94f80 00000000 win32k+0x92266 ab617a70 bf8ad5eb e1b94f80 e141c3b0 e608dd48 win32k+0xacbeb ab617be8 bf8b3f2e ab617cb0 e6363d40 00000001 win32k+0xad5eb ab617cdc bf8b6199 ab617cb0 e1a01008 00000000 win32k+0xb3f2e ab617d20 bf8b608c 07f1dbdc 04ddc720 00000000 win32k+0xb6199 ab617d48 8054161c 07f1dbdc 04ddc720 00000000 win32k+0xb608c ab617d64 7c90e4f4 badb0d00 07f1dbb8 ffffffff nt+0x6a61c ab617d68 badb0d00 07f1dbb8 ffffffff ab26cda0 0x7c90e4f4 ab617d6c 07f1dbb8 ffffffff ab26cda0 00000000 0xbadb0d00 ab617d70 ffffffff ab26cda0 00000000 00000000 0x7f1dbb8 ab617d74 ab26cda0 00000000 00000000 00000000 0xffffffff ab617d78 00000000 00000000 00000000 00000000 0xab26cda0 1: kd> dc bf16da40 bf16da40 21500d8b ec83bf45 56555330 f5aee857 ..P!E...0SUVW... bf16da50 2d8bffff bf452150 4010458b 83104589 ...-P!E..E.@.E.. bf16da60 c701107d 00641445 57750000 33104d8b }...E.d...uW.M.3 bf16da70 7d8d41f6 104d8920 f0bdc0bb 8b11ebff .A.} .M......... bf16da80 4521502d 8d09ebbf 000024a4 ff8b0000 -P!E.....$...... bf16da90 1024548d 10245c89 142444c7 ffffffff .T$..\$..D$..... bf16daa0 5218458b 4855ff50 86a0c681 fe810001 .E.RP.UH........ bf16dab0 004c4b40 078b0777 7504470b 502d8bc2 @KL.w....G.u..-P 1: kd> dc e1aa4304 e1aa4304 ???????? ???????? ???????? ???????? ???????????????? e1aa4314 ???????? ???????? ???????? ???????? ???????????????? e1aa4324 ???????? ???????? ???????? ???????? ???????????????? e1aa4334 ???????? ???????? ???????? ???????? ???????????????? e1aa4344 ???????? ???????? ???????? ???????? ???????????????? e1aa4354 ???????? ???????? ???????? ???????? ???????????????? e1aa4364 ???????? ???????? ???????? ???????? ???????????????? e1aa4374 ???????? ???????? ???????? ???????? ???????????????? 1: kd> u bf16da40 *** WARNING: Unable to verify timestamp for ati3duag.dll *** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll ati3duag+0x2a40: bf16da40 8b0d502145bf mov ecx,dword ptr [ati3duag+0x2e7150 (bf452150)] bf16da46 83ec30 sub esp,30h bf16da49 53 push ebx bf16da4a 55 push ebp bf16da4b 56 push esi bf16da4c 57 push edi bf16da4d e8aef5ffff call ati3duag+0x2000 (bf16d000) bf16da52 8b2d502145bf mov ebp,dword ptr [ati3duag+0x2e7150 (bf452150)] 1: kd> lmvm ati3duag start end module name bf16b000 bf464e00 ati3duag T (no symbols) Loaded symbol image file: ati3duag.dll Image path: ati3duag.dll Image name: ati3duag.dll Timestamp: Thu Dec 20 21:47:34 2007 (476B2946) CheckSum: 002FB345 ImageSize: 002F9E00 Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0

The problem with disabling the pagefile on a system with a large amount of RAM is that in general, the memory manager will try to keep pages in memory for running applications - with 8GB of RAM, that's a lot of memory to commit to running apps, and as such the pagefile doesn't get used much anyway (this isn't always the case, but it usually is). Thus, it would probably be better (and safer) to create a really small pagefile, say 512MB min and max, that way you can still page out most or all of kernel paged pool and executive if need be, and the bias for the memory manager will be weighted almost entirely to putting pages in RAM, as your commit limit is RAM+512MB, rather than RAM+a few GB.

The whole box would be better - just let us know once you get the dump which application hung, and approximately how long you noticed it was hung before you took the memory dump.

In general, if a drive is reported as removable XP will not let you have the pagefile on that drive. It'll look like it worked, but as you've already found out, when you reboot the pagefile on C: will come back.

Get a dump of the box next time something hangs, noting what process is hung and for how long, and then compress and upload it somewhere we can all get to it to download and analyze .

Actually, if the x64 CPU has support for hardware virtualization, and you're using VMWare, you can actually run 64bit guests on the VMWare server 32bit host. However, your CPU usage on the host from that guest VM will be much higher than if the host was 64bit. So yes, it can be done, but it's not recommended.

What about from machine to machine inside one of the sites? Besides, 256Kb is a normal speed for a slow ATM WAN link, so if you're capping at that speed I'd have to doubt your claims of T1 3MB service (or I'd be contacting your ISP right now!).

Internet Explorer hangs and crashes are almost always caused by something 3rd party added in, just like most any application hang or crash. If running with the -extoff command line parameter doesn't work (iexplore.exe -extoff), then consider getting a dump of it when it's hung and seeing what you've got loaded. Also, IE could actually be running fine otherwise, but thread 0 in the process could be blocked on something - thread 0 is the UI thread (amongst other things) for most apps, so when thread 0 gets blocked waiting for something else in-process to complete, the app will appear to "hang" (because the UI thread is stuck), but it's still running. I know it's not much help to you now without a dump, but that is very likely what is happening.

Silly question, but have you tried a different switch, or perhaps a hub instead? Remove some of the "switch smarts" and see what happens with a hub, would actually be my first test (I always keep a 4port hub with me for just this purpose). If it works fine with the hub, it doesn't mean the switch is bad, either - it could be the NIC driver or the card itself, or bum NEGO code.

Yes, but actually, they usually aren't - either the NIC driver is poorly written, or the switch doesn't like the flood of NEGO requests, etc. Don't ever assume the driver or hardware is working properly .

Well, first thing to do is to remove all drivers in spoolsv.exe on the term services server via Printers and Faxes > File > Server Properties > Drivers tab. Second, make sure you uninstall from add/remove programs any crap the driver installed that isn't removed by uninstalling the driver from the server properties in printers and faxes. Next, download and run cleanspl.exe (windows 2003 reskit) on the terminal server, making sure not to delete any inbox print monitors (like standard tcp/ip print monitor, local port, lpr, usb port, etc), but deleting any other non-inbox print monitors. You will have to reboot once this is finished. Next, reinstall ONLY the driver files (if the driver for your model didn't ship with the Windows CD, and you can't use a driver that's "compatible" or similar from the list on the Windows CD, you will have to download the driver package from the vendor and extract it to disk to do this) via Printers and Faxes > File > Server Properties > Drivers tab. Just point the installer to the driver you need (either from the Windows list or the folder on disk). Now, the TS is "clean", or as clean as you'll get it if you install OEM print drivers. One more thing is to make sure administrators don't have print redirection functionality on the server - admins who connect and use a driver not already on the TS will INSTALL A NEW DRIVER, so watch out. Admin access should never be for everyday usage anyway, only patching/config changes/etc, and as such admins do not need to be redirecting printers. Lastly, make sure you enable and use the TS print fallback driver functionality if you allow redirection of printers, so that if a user has a queue that doesn't have a driver already installed, that he/she will be forced to use the "fallback" driver for the queue rather than the driver on their machine - this should keep you as clean as possible. If you are so inclined, doing the exact same thing on your print servers and clients is another great way to "clean up" your print environment overall. Oh, and yes - PCL drivers are evil. PS drivers are the most stable (although perhaps least functionality comparatively), PCL5, then PCL6. 6 may be most functional, but they create HUGE spool files and are just not as stable or supportable as PS drivers. If your users can use postscript, use ALL postscript drivers - once you start mixing and matching, you cause the spooler service to be compromised stability-wise, which you've all already found out, it seems, the hard way .