cluberti

For all intents and purposes, yes. If you want the nitty-gritty, I'd suggest a quick google search on PS vs PCL drivers. Unless you've got high-end printers that are sensitive to color or font differences in your documents, your users won't notice the difference between PS and PCL drivers.

Has anyone here considered that he may be on a different subnet than other PC's (in which case, he can only see machines on his subnet), or that netbios requests are not being routed past other network equipment on the network? One test would be to see if you can ping the FQDN of a machine that you can't "see", but you know is there and is not firewalled.

Also, along the imaging vein, I've seen sysprep'ed and riprep'ed machines show up with the same SUSSID (WSUS assigns each PC a SID of it's own, and imaged machines have a habit of getting the same SID from the WSUS server). Deleting the SUSSID does help in a lot of cases with machines not showing up in the computer list in WSUS, so keep that in mind as well.

Actually, PS drivers are the most stable, with PCL6 drivers being the most problematic. Just an FYI - if you can use the PS driver, do so, as things generally work MUCH better in a TS environment.

So it appears that the 2Wire is acting as a DNS proxy - when you use IE, what happens? Also, make sure that IE is not configured to use a proxy! You could also try manually setting the proxy server for your network card's TCP/IP properties to something other than the 2Wire device, such as 4.2.2.1 or 4.2.2.2 (MCI's quasi-public DNS servers).

I would follow the instructions linked in your first post to install just the remote desktops console, but I would grab the actual adminpak.msi file from a Windows Server 2003 SP1 source (downloaded from microsoft.com, preferrably). That should work.

Does the other person use Outlook? If so, consider simply creating a new personal folders file (.pst) and copying the email messages into the .pst. Send that .pst file to your colleague, and he should have the email messages, unaltered, when he opens the .pst file.

If you could change your dump options to do a full dump and set your pagefile size to RAM+50MB, you'd get a full memory dump that I could debug for you. Would it be possible for you to post the (compressed) dump here, or PM or email it to me? That's usually a memory error, but it's now always a physical memory error - it could be a kernel pool memory error as well. I can tell for sure by looking at the dump...

Is your computer directly connected to the internet, or do you have a firewall or router in place between you and your broadband modem? I've seen hardware routers and firewalls mess with SSL connections because of packet size and signature issues...

Have you tried going into Tools > Options > Advanced, and unchecking "Enable third-party browser extensions"? If you do that (and close all IE windows before trying again), do the problems still exist?

Make sure you're pinging the IP address, but when using nslookup you use the actual domain name (nslookup www.google.com).

Have you tried removing the print monitors from your server (or changed the printer to use the Microsoft standard print monitor)? Print monitors are the devil on print servers, and especially so through Terminal Services (Citrix or RDP). Also, have you tried switching the clients from spooling to printing directly to the printer to see if things improve? Unless you use printer drivers (especially in TS) that come with the Windows CD, you will usuallly run into problems like this sooner or later. I'd try switching from spooling to printing directly to the printer first to see if that fixes things (almost always does), and if that does not work, try disabling or removing all print monitors from the print server in question. Note: There is a utility in the 2003 resource kit called cleanspl.exe for cleaning out your printer keys in the registry - use printmig to backup your printers, use cleanspl to clean out the print key, and then use printmig to import your printers again (this will have removed all third party print monitors, as printmig doesn't export anything but the standard port monitors and some legacy HP and Lexmark monitors if they exist). Make sure you have a good backup of the printer registry hives before doing this (just in case you need to re-import on some failure), but the above should clean out your printers keys very well and leave you with printers and drivers, but no other extraneous "fluff".

Is it listed in the Disk Management section of "Computer Management"? If it's listed there, you may just have to initialize the drive (or you won't see it). If it's not there, then some further troubleshooting needs to be done.

I've no experience with Kerio, but I've heard both good and bad things about their personal firewall product.

No problem - let me know what you come up with this weekend.

Yeah, Intel is shipping the (yuck) Marvell NIC on some of their boards. It pays to go with an Intel board with an Intel NIC on it, I guess, even though it'll cost a bit more .

The i386 tree exists because NT originally ran on a 386, and the build tree was i386. It's a holdover from a previous time - it doesn't mean anything except to denote the x86 architecture, just as Windows x64 uses the AMD64 folder to hold the x64 files, regardless of whether you're using an AMD x64 processor or an Intel EM64T one. Sheesh .

If you can ping the modem from the computer, have you tried pinging an IP address outside of your network, such as 64.233.167.147 (www.google.com)? If the PC isn't working, we will need to know what isn't working - there's more to accessing the internet than being able to use a browser . Try using nslookup as well to see what www.google.com comes back as (if at all)...

Ok - here's what's happening on your HP (I'll try to keep it in layman's terms as much as possible): The stop 7a message in the blue screen indicates a kernel trap error - Windows went to load a memory page into physical memory (RAM) from the paging file (pagefile.sys) on the hard disk, but it was unable to access the page due to a failure (software or hardware). The second value of your stop error, 0xC400003C, returns as "STATUS_DATA_OVERRUN". It's a filesystem, disk, or disk controller error - there's no way exactly of knowing which, so you will need to troubleshoot all three to determine which is the root cause. The problem could be one of three areas: 1. It could be a problem with the filesystem, in which case running chkdsk /f should help (although you may just have to copy your data off and do a complete reformat and reinstall to be sure the problem is gone). 2. It could be a problem with the hard disk itself, in which case you should get your data off and replace the drive. 3. It could be a disk controller error, in which case you'll have to replace the motherboard (and in an OEM machine, good luck). If it's the controller, putting a different hard disk in this PC should give you the same errors with XP installed. My guess is that it's #1, but running a hardware test using a boot CD or floppy from the vendor of the hard disk in question should tell us if the problem is with the hard disk or disk controller. Most hard drive vendors have utilities you can download from their site to test the hard disk for errors. On to your tiny machine, it sounds like you're running out of space in your pagefile, but without knowing what is in the pagefile itself, and how much physical RAM is in the machine, it'd be just a guess. It's complaining about running out of memory, but most likely it's complaining about having a problem with creating enough *virtual address space* to run your system, which could mean that your disk is full, the page file is too small, or both. Have you been able to reboot this machine in safe mode? If so, consider moving your pagefile to another hard disk or partition, and making it's size at least 3x the amount of physical RAM in your box. If you can't boot into safe mode, perhaps you could attempt to repair the OS using a repair installation. If that fails, you're out of luck and you will likely have to do a complete reformat and reinstall. It wouldn't hurt to do a full hardware test on both of these machines as well, to see if you have any other hardware that may be failing. Windows 98 was much more forgiving with hardware errors than an NT-based system will be - the exact same error that 98 would happily ignore will cause a bluescreen in NT in most cases.

A new text document. I'd suggest notepad to create the new file, or right-click on your desktop and choose New > Text Document.

If you have no recovery CD, you're in some trouble. You'll need access to a Windows XP CD - it doesn't have to be your own, but it does have to be the same version as your installed OS (Home or Pro). You can run the repair installation from that CD, but you WILL need an XP CD in some form to fix your box (without losing your data, that is).

For Server > XP, you must add the "Administrator" account on the XP machine to the Telnet Users group on the XP machine. For XP > Server, you must run the "Telnet Server Administration", and set the NTLM to 1 or (better, in this case, for testing) 0.

Is this machine on a domain, or being affected by group policies? It looks like IE has been "locked down" by removing some of the tabs. If this isn't in group policy or a domain, you can check the IE settings yourself via gpedit.msc.

I still have the old XP powertoy with the fast user switching in it via the Win + Q key combo - PM me if you'd like it sent to you .

If you're unable to create a new file and rename it, or copy and paste, I'm not entirely sure you're going to find my advice helpful. I'm sorry.