cluberti

You might want to ping a host you're trying to hit with large packet sizes (again, 1024 is a good size, although 1492 is a bit better), and if you see slowness, do a tracert while doing a looping ping (ping -t) of large packets to see where the slowness occurs. Once you see the hop that's slowest, ping the hop before that, the slow hop, and the hop afterwards to verify that the slow hop and the one after it are indeed slow when pinged with large packet sizes. This can give you an idea of where the problem is if you can find out who owns the hop that's slow. If your gateway is fast to large pings, it's somewhere on your ISP's network, likely (especially if you're slow to multiple external hosts).

You've probably already found it, but here's the API documentation on KeBugCheck - note the only parameter you can pass is the bugcheck code you want to use. You can also try KeBugCheckEx, which gives you 5 parameters - first is code, next 4 are bugcheck parameters you can pass.

Also note that the vast majority of AD problems come down to DNS problems, so making sure your DNS is pristine (and you aren't using ANY public DNS servers on ANY of your boxes) is a good start as well.

Hm - all of the network switching gear I've used from Netgear had power on the back and ports on the front, which is exactly what you'd want for cable management. Maybe I misunderstand - no matter though, as higher-end devices from almost any vendor will be good enough for demanding home / small business users.

I've had bad luck with Netgear "consumer" gear as well, but their commercial and higher-end "prosumer" gear is rock-solid.

What rights does your user account have (do you have schema admin rights in the domain?), and what permissions does your account have against the sysvol folder and subfolders on the DC?

When the problem starts occurring, do you see the problems printing to all print queues on that server, or just some? Also, if restarting the print spooler resolves the issue, this is much more likely to be a driver (or driver interaction with another driver) problem that a spooler problem.

Try to avoid naming program files or batch files after files on the system that already exist, unless you're passing the entire path to the file when calling it .

Download and run ShellExView, and disable any extension listed that is not a Microsoft extension (there's a field for vendor, so you can tell a non-Microsoft extension from a Microsoft one). Once you've done that, restart and see if the problem continues.

You are correct - only 2003 server supports the /console switch.

That's an error message passed by a WatchGuard HTTP proxy box - contact whomever installed it on your network to give you access to the site. It's a transparent proxy, which means you don't get around it unless the Watchguard device at the egress point allows you.

Retail (and retail OEM) copies that are purchased from a retailer (not shipped with the PC) will generally come with one serial, but two DVDs - one x86 and one x64. The serial will work on either, although if you activate on one platform architecture (like x86) and then try to re-activate on another architecture (like x64), it may or may not work. If the hardware underneath is exactly the same, though, it should work just fine.

XP MCE 2005 is a product you have to acquire if the OEM that sold you the machine does not provide the updates (and if your hardware, especially your TV card, doesn't have the correct MPEG support, MCE 2005 will not easily run on your machine). It's not a free update unless the OEM provides it to you that way - otherwise, you have to buy a copy from a retailer and install it.

First obvious question - what software is this that requires the .naf file?

You'd have to boot with an ERD CD like BartPE or WinPE (or the Vista disc itself) and do a repair install, or reinstall, of Vista or XP.

If you can force the usage of IE, you can configure IE to use a proxy autoconfiguration script that does exactly this.

The only other thing that can cause a deaddead bugcheck is if a driver specifically calls KeBugCheck and passes it this code.

There are 11 channels, but only 3 are non-overlapping - 1, 6, and 11. For example, channel 3 is really part of channel 1's range, channel 5 is part of channel 6's range, and channel 9 is part of channel 11's range (etc).

Technically, no. You need to make a connection to the RPC epmapper first, and then the SMB connection is done on another dynamic port once the IPC$ connection is made and some other info is exchanged. I guess the next question is why would you want to do this?

Ah, I made the assumption you were a tester. Yes, SP1 can be acquired and if you can, you may want to test an SP1 build to see if it repros. Is it safe to assume that you simply install vista from the technet iso, add it to the domain, and do nothing else to repro this issue?

I believe I mentioned you were short two prisoners at the beginning of this charade lol

Well, yes, that's a lot of packets. Getting a network trace running via netmon or wireshark during this time would show you where those packets are going - and also, those counters are cumulative, so they'll keep increasing as you send/receive packets for the uptime of the machine, and only reset on reboot or removal of the network adapter from the machine.

Microwaves travel in the 2.4GHz range, so that means that yes, your Microwave oven can (and probably will) cause interference at possibly 50 feet (and even more depending on the age of the microwave and how many obstacles are between the oven and the WAP and laptop). In short, unless your WAP and wireless card are using the 5GHz spectrum (802.11a), then yes, this can actually happen because of a microwave oven. The device spec on a laptop's PCMCIA slot or MiniPCI slot is generally designed to output far less power than a desktop PCI card even on the max power configuration for the laptop, so it may not matter what 802.11b/g/n card you use. Again, if you can, try 802.11a for your WAP and wireless card in the laptop, as the 5GHz range is far less populated than the 2.4GHz range (almost all wireless devices you can think of use the 2.4GHz range unless otherwise specified ).

Because it only occurs with a beta server OS. If you can repro this with a Server 2003 server domain, then we can start blaming vista, but if server 2008 configurations are the catalyst, this probably belongs in beta. Does Vista SP1 repro the behavior, btw? You mentioned previously you hadn't tried it, but if you are able to acquire a server 2008 license, you should also be able to give Vista SP1 a try.

The drivers for that particular card and x64 vista don't get along well, so I'm not surprised here. The blue dump you posted seems to be removing a mapped view of a section in memory during a thread termination in kernel, which means it's likely this was a kernel mode driver thread. Hard to say without a dump, so if you can get one and post it somewhere I can get to it, I can help further.