cluberti

OK, before jumping to hardware conclusions, let's find out EXACTLY what happens. When you go to shut down or reboot the machine and it stops, can you still use the machine? Can you move the mouse, press ctrl+alt+del and get the winlogon screen, or open/close running applications? When did this start happening? Does this happen when you boot into safe mode and reboot or shut down?

The easiest way is to modify the group policy object that applies to the users you want to redirect (at least the root folders on the sbs2003 server or file server where these folders are being redirected must already exist). The policy setting is located in User Configuration > Windows Settings > Folder Redirection.

It depends on what type of image you are attempting. Since it isn't platform-specific, most likely we're talking about a "flat-file" image, not a riprep image. To create a flat image in RIS, go to the server and type risetup - it'll bring up a wizard and ask you for the location of the installation folder for the version of Windows you'd like to use RIS to install (\i386 for x86 or \amd64 for x64). This creates a basic RIS install of that version of Windows, and places it in the OSChooser list. There are lots of things you can do to automate RIS, including modifying the OSChooser screens themselves - remember that a RIS install is close to an unattended CD install, but not quite. Almost everything you can do in an unattended CD install you can do via RIS, and sometimes more. I strongly suggest customizing an unattended CD installation the way you'd like first, and then start "grafting" that into a flat-file RIS installation. This is a huge topic, and one not easily covered in a post on a message board .

Well, since all of your shares and share security are stored here: HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares A simple registry file import may suffice?

Or perhaps read the unattended guide, linked at the top of EACH page. Please do not cross-post, it'll get you in trouble.

Well, unless you actually are trying to do this with a 2000 server - the guide is for 2003 server. It's basically the same, but obviously there are differences (mostly components from XP that are installed on 2003 but not enabled - 2000 would not have those components installed).

Steve Gibson is that guy you work with that harkens back to the days of DOS as Microsoft's best OS and is afraid of relational databases. He's THAT guy, and he hasn't done anything of relevance in many years.

I love the internet

LOL - glad to hear things worked as they're supposed to .

As I posted in the closed thread, you need to make sure Shareza is running when you make the exception for the port, because the Firewall will not open the port for listening unless the backing program is running. This is why you should use program exceptions rather than port exceptions, unless the program is an always-on service (in which case port-based exceptions are fine). Is there a particular reason you need to open the port, and not except the application? It seems silly to me to possibly open a port wide open on a machine at all times, rather than just when the app that's using the ports is running. Just questioning - maybe there is a good reason.

I had my post ready to go and say "It's probably an INACCESSIBLE_BOOT_DEVICE bugcheck", but you beat me to it. I'm guessing you're gonna need to sacrifice a drive with 2k3 unless you have a current backup of the system state (you really SHOULD back that up when you're using Windows to do your RAID).

Open a command prompt and telnet to your machine on port 6346 - do you connect to yourself? Also be aware that you need a program actually listening on that port to get the port opened. Meaning if Shareza is the only program using the port, it needs to be running (and listening) for the port to be opened. Another reason why opening PROGRAMS rather than PORTS is a good idea. If there's no backing program, the firewall doesn't open the port for listening.

Gotta agree with the others here - I've not seen Vista's install crash like that since a Beta2 install on a Thinkpad laptop (and it was the keyboard driver on the laptop that actually caused it to crap out - imagine that). You said you tried it on multiple PC's, but after d/l the .iso again and mounting it in a VM, did the error occur there?

There are 3rd party applications that you can purchase to allow recovery, but you'll need to boot to another hard disk that is set as the primary and install Server 2003 on it. Attach the other drives, hopefully it won't bugcheck, and you'll get to run utilities that should see the dynamic volumes. I've heard some decent things about this utility before, but I've never had to recover a dynamic volume myself. Make sure you back things up in the future . To that note, I recommend something small, like a set of USB 2.0 drives and a Linksys NSLU2 or a D-Link DSM-G600 network storage unit.

If you download autoruns and shellexview, run them in safe mode, disable all non-Microsoft items in both tools, and reboot, does the problem recur?

From the forum rules: 1. This is not a warez site! Links/Requests to warez and/or illegal material (porn, cracks, serials, etc..) will not be tolerated. Discussion of circumventing WGA/activation/timebombs/keygens or any other illegal activity will also not be tolerated. You will be banned without notice.

Something you can try to see if it's the driver causing this (it usually is, but it doesn't hurt to check): 1. Completely uninstall the driver (and any other software that was installed with the printer) and remove the print queue - once done, reboot the machine and make sure it's all removed 2. Install the printer again, but this time do not install any software - simply use the add/remove printers wizard, and choose the generic HP Laserjet 4 driver built into the OS as the driver 3. Print a test page If you are able to print a test page to your printer over the LPT1 port, you need to consider using a different driver. HP isn't known for their great drivers (at least not the low-end, home user stuff - the high-end business stuff is *usually* OK).

Then you're trying to do something that Windows 2003 cannot do natively - however, if you've got network equipment that supports it, setting up 802.1x via IAS (your switches need to support EAPOL and 802.1x for this to work) will keep people who do not have either a smartcard issued by you, or a certificate issued by you, off of your network. 802.1x is enforced at the switch level, and only allows EAPOL packets between the switch and your Server 2003 IAS server - once the smartcard or certificate from the machine is accepted via the Server 2003 IAS server, the switch port becomes active until the set time frame passes (configured by you) or the machine disconnects from the switch port (again, you will configure how a port becomes "active" and also how an active port becomes "inactive"). Again, if your switch hardware supports it, this is a relatively easy and quick way to lock down a network the way you are requesting.

If you've opened the ports, you should see them in a netstat -an on your IP address (probably in the istening state). If they're listed as open there (listening or established), then the firewall did it's job and opened the ports. If that is the case, it's likely that the application is using more than just those ports, or it uses those ports to connect and then dynamically acquires and uses other ports (which is highly possible). It's always better to exempt an .exe than just ports, mainly for this reason.

If, even after going through and specifying what program to use, it's not sticking, perhaps running regmon on the machine while making the change in IE will show you which key is (or is not) being updated. I can't think of any other reason than you're either not writing the data to the registry, or IE is unable to read it.

That's the reason I recommended making sure the machine is clean, because neither asappsrv.dll (spyware) or command.exe (trojan/worm virus!!!) are Microsoft files. That machine is (very much so) not clean, so cleaning it and running sfc is the best way to start.

Actually, the best thing to do first is to make sure you're clean from infection - that way when you replace those files with good ones from the CD, there's no chance they'll get overwritten with infected versions again. Second, pop in your Windows product CD and run the command "sfc /scannow" - this will check all binaries that are protected on your machine, and replace anything that doesn't checksum with the original version. The other thing that you can do, if that doesn't work, is find the compressed file on the Windows product CD in the i386 folder, and decmpress it (if compressed) and copy it over to the hard disk. I'd suggest doing this only if sfc doesn't work.

Well, first you need to know what kind of speeds you are getting - since that's a 10/100Mb switch, best thing to start with is to make sure that the network interface cards on all of the machines using the switch are of good quality (cheap-quality NICs make slow networks), and configured to be at 100Mb/Full (speed/duplex) rather than auto negotiate. After that, you need to start doing some network tracing (wireshark, netmon, whatever works for you) to start watching your network. That'll give you some idea of what your network traffic looks like, and what to do about it.

MicroSoft Employee

Other than stating the obvious of buying a valid license, I'll give you the benefit of the doubt that you actually have a valid license purchased from your server hardware vendor, from a reseller, or from Microsoft directly... If you've purchased a valid license, you should call Microsoft and get it resolved. If you are unsure of the validity of the server install, it does sound like you're being told that it is a priated version. Contacting the server vendor to get this resolved is also a good idea. If it's a copy you downloaded off of the internet, or "borrowed" from somewhere else, you won't find any help with your query here - just warning you ahead of time if this is the case - from the forum rules: