cluberti

Do you need to edit the files, while open, on multiple machines, and have the changes saved in real time? If so, this cannot be done (within a Microsoft Office document of any kind, at least) unless you all connect to one shared LiveMeeting or GoToMeeting session and all use the same desktop session.

I'm not entirely sure what the problem is at the moment, but your problem as per the hex result is this: ERROR_INTERNET_NAME_NOT_RESOLVED You might try setting a policy on a test OU to point to a netbios or FQDN name (NOT an IP name), and see if those machines exhibit the issue.

If you allow svchost.exe access to the internet, WU should work.

If they forced v2, then yes, it'd fail . You would then need to do both changes - SMB signing and NTLM auth level.

Well, considering you don't even have a valid symbol path set, you aren't going to get far with this dump, and it tells me something about where you should start if this is a path you do really want to travel. Consider reading this post on the Ask the Performance Team blog on how to get started with understanding the innards of how Windows works, because without this knowledge your debugging skills will be lacking. Another thing you really need to know, even if just on a basic level, is the C programming language - the OS and almost all of the call stacks you'll see in a dump are C code, and if you don't understand C at a functional level, you'll be a poor debugger. The last suggestion would be to try and go to a user-mode or kernel-mode debugging class (or both) given by your local training center if possible, as this is a very good way to go from a basic debugger to one with some more-than-basic knowledge. Once you've done the above, you'll be ready to dive into some really interesting memory dumps and learn more, to become a fairly good debugger - and over the course of a few years, you'll get even better from there if you do it very regularly. Debugging does have some science, but there's also an art to it that just can't be easily taught in one or two threads on how to troubleshoot a STOP 0x1a, or any other crash or manually-generated dump. By the way, configure your machine for a full dump, as minidumps are pretty useless. If you do want to actually troubleshoot the STOP 0x1A you're seeing here, you'll need at least a kernel dump the next time it occurs, and if disk space isn't an issue, it never, ever hurts to get a complete dump of any issue just in case.

If it's not 2003 native, that shouldn't affect logons from downlevel DOS clients. A 2003 native domain would likely require LM Auth to be forced to NTLM v1.

Well, unless you enable it, on a default install of Vista the administrator account is disabled. That may affect your ability to use the administrator account via runas. If it is enabled but you have not configured a password, it would also not allow you to use the account as a runas target.

Let me get this straight - you want a user to disable a huge chunk of the OS security model, just so a command prompt can run elevated?

You have to disable SMB Signing to make this work: 1. Open the Default Domain Controllers Policy 2. Browse to Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options 3. Edit the "Microsoft network server: Digitally sign communications (always)" policy, configuring it to be "Disabled"

You can't activate it with that key - it's the 30day demo key (as others have said). You enter your own key (either during setup, or afterwards when prompted) and activate that.

Right-click on the icon in accessories for the command prompt and choose "Run as administrator".

Well, it sounds like you've done the basics, which means the project either requires something local to the machine, or IE zone settings are not working properly (and I think you'd know that if it was broken, so not likely). I hate .net for most things anyway - go with C and be done with it.

What exactly are you seeing? Vista uses a few different methods to determine the architecture of an application...

Since this was in his problem statement, I can't say with any conviction DNS is the issue - if it was, it should fail for all users, not just one.

Is there any reason you aren't running this from cmdlines.txt or [setupParams]? You are trying to do quite a few things near the end of that script (and perhaps even the beginning) that are going to require at least a somewhat functional OS, which does NOT exist at T-39. My suggestion would be to place it after the UserExecute= line in the [setupParams] section of winnt.sif and see if the problem still occurs.

What's the bugcheck code of the crash, and did the box generate any *.dmp files on crash?

Are you sure it's applying the domain policy, and not the standard policy?

Can you perhaps copy and paste all 3 types of events here, so we can review?

What kind of errors or roadblocks are you experiencing when running the application from a non-local location?

Well, if he is unable to log in and map the drive, but you are able to log in and map the drive on the same machine, it could be a host of things. You do say that he can map the drive by IP address rather than fqdn or netbios name as well, so it's not a permissions issue to the share itself per se. Have you considered running process monitor on the machine while the user maps the drive, or configuring his logon script to output everything to a log? Even userenv logging would be good in this scenario.

Note that if the indexer is enabled or antivirus is scanning, both of these things will change the "modified" date (indexer flips the "indexed" bit, and most antivirus load and check a file in process, causing the modified flag to get set).

Why... what?

You will need to delegate the users read/write permissions on the AD "phone number" property. http://www.microsoft.com/technet/prodtechn...rv/intro11.mspx

Boot from your Vista disc and repair it - you should get a system restore automatically.

In 2005, I think, it was changed (for XP and higher) - OEM reactivations now have no timeframe. You HAVE to contact MS via phone to reactivate (even 3 years later).