Category: work

Today is one of the reasons I walk to work when it’s nice out.  62 degrees out, mostly sunny, cool breeze coming from Lake Michigan.  How can you not want to be outside?  Actually, I walk to work even when it’s not so perfect.  Basically, anything above 45 degrees and I’m hiking it.  Granted, it is only a thirty minute walk.

I really hope that yesterday isn’t as awful as yesterday.  It wasn’t even like I was that busy, it’s just the things that I was tasked with took about 5 hours too long for various reasons (piss-poor documentation, machine slowness from misc crap installed [production mind you], etc)

I was getting so angry that I actually had to go out for a walk to blow off steam before 2 late afternoon meetings.

Well, Microsoft has finally bowed to VMWare’s free Server product.  You can finally download Virtual Server R2 Enterprise Edition for free.  It’s great that VMWare has forced this upon Microsoft.  However, there are still a few key differences.  The free version of VMWare Server is actually a “beta” version, while Microsoft’s Virtual Server is the final build, and safe for production use (unless it’s running on XP). 

This is great news for enterprise environments none-the-less, especially with the new licensing scheme for Windows 2003 products.  Basically, if you have enterprise resources, you’re incredibly stupid not to be running some sort of virtualization, be it in production or not.  You save too much money on the hardware (one machine now can host X number of virtual machines) and software end (one Windows 2003 license can be used on the host and up to four virtual machines, and the virtualizing software is free).

I personally can’t wait until hardware based virtualization technology becomes more main-stream, that’s when the huge performance increases will come.

The project server here at work hasn’t been connecting to our internal WSUS server, and I noticed that it was missing a few security patches.  Since WSUS wasn’t working, I decided to visit Windows Update.  HA, well that doesn’t work either.  So I open up the %systemroot%WindowsUpdate.log and find the following error.

WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190191
WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190191
WARNING: DownloadFileInternal failed for http://download.microsoft.com/v6/windowsupdate/redir/wuredir.cab: error 0x80190191
* WARNING: Failed to synchronize, error = 0x80244017
WARNING: WU client failed Searching for update with error 0x80244017
>>— RESUMED —COMAPI: Search [ClientId = WindowsUpdate]
– Updates found = 0
– WARNING: Exit code = 0x00000000, Result code = 0x80244017
————-
— END — COMAPI: Search [ClientId = WindowsUpdate]
——————-
WARNING: Operation failed due to earlier error, hr=80244017
FATAL: Unable to complete asynchronous search. (hr=80244017)

Doing a quick search on the error code on Google brings me to a lot of pages about proxy settings.  However, I’m not running a proxy server anywhere, and I’m not running ICF on the project server either.  What is going on?!

Then I see a link about project server with this error.

I now know that project server uses a proxy server with WSS.  How stupid can that be?  Well, basically, I added our local WSUS server to the bypass list.  I also did it for *.microsoft.com, but that still doesn’t seem to be allowing me to hit Windows Update.  Oh well, at least it can update from someplace.

 

Well, today I passed my last required MCSE test.  In three months, I’ve been able to complete the 7 required tests.  Unfortunately, I still have one more on my plate though, because I want to get the MCSE: Security certification.  Thankfully the remaining test is simply an elective exam, so I can probably kill that in a week.  Not having any of this pressure on me for the rest of the year will be nice too.  I’m definitely glad I got this out of the way before summer rolled around.

In fact, some days you learn two things!  Be warned, techno-speak is about to ensue.

Lately, I’ve been reading a lot about Windows sercurity.  Now, all the books I’ve read that have dealt with authentication bring up the differences between LM, NTLM, NTLMv2, and Kerberos.  The general idea that these books give you is that the Lan Manager and NT Lan Manager authentication methods use a hash or a challenge/response hash, while Kerberos uses time based tokens.  The key word being “time”.  Nowhere in my reading was it brought up that any versions of Lan Manager authentication had time involved. 

This leads me to my problem yesterday.  We have an NT4 domain setup to mirror a customer’s environment.  This NT4 domain contains many environments for various testing purposes.  One of these purposes is regression testing with date changes.  Prior to this week, changing the date on the machines has been fine.  However, this week we ran into problems.

Now, for those of you that aren’t familiar with NT4, it uses LM, NTLM, or NTLMv2 (SP4 or above) authentication, which according to everything I’ve read had no time restrictions, and everybody in the office was in the same boat as me.  In fact, these machines authenticated fine with date changes until this week.  The difference being a security template we had been applying to all machines that was given to us by the customer. 

To begin with, we knew that it was a problem with the security template because non-hardened machines would work fine with the date change still, while the hardened ones would throw errors.  Basically, critical application services couldn’t start after the hardening had happen.  Now, it was my job to figure out what the security template was doing to prevent these services from running.

First I went through the documentation that came with the security template to see what they changed, and tried to find the obvious answer.  Well, of course that didn’t work.  So, instead, I just started changing settings back to the original.  Thankfully I started at the bottom, and four changed settings later, I was at my solution: Network security: LAN Manager authentication level.  The security template was setting it to “Send NTLMv2 response onlyrefuse LM & NTLM”, while the default setting is Send NTLM response only.  The default setting worked, but I wanted to try the other two settings between the default and the hardened setting: Send NTLMv2 response only, and Send NTLMv2 response onlyrefulse LM.  Needless to say, neither of those settings worked either. 

Now, you may be thinking that we were having problems with NTLMv2 because our PDC and BDC on the NT4 domain aren’t at SP4 or above.  Bah, I say to that, we’re at SP6, so we can have NTLMv2 authentication on our domain.  So why was the hardened setting, or any NTLMv2 setting for that matter, not working?  Well, after much googling it appears that NTLMv2 is time dependent.  In fact, the NTLMv2 response contains a little-endian, 64-bit signed timestamp.

Let me tell you how assured I was in the books I was reading after that. 🙄  After reading about this timestamp, we wanted to figure out how much of a time delta NTLMv2 allowed (for purely scientific reasons).  After some testing with the hardened machine, it was concluded that the timestamp of the response cannot be greater than or less than 30 minutes from the challenge machine (in this case the PDC).  So, in our testing, setting the date back a month, obviously was outside of this delta.

Then, later that night I was playing with my ISA 2004 machine at home.  A little background first.  I’ve got multiple websites on multiple machines at the apartment that use port 80, so I’ve been using ISA to publish the websites.  Otherwise, all the sites would have to be on one machine, since the router only supports port forwarding, and not host header forwarding. 

So, I’ve been dealing with a problem where whenever I would set the firewall rule to “Requests appear to come from the original client”, my website wouldn’t load.  This is a nice feature for stats, so that you can actually see where visitors come from.  For the interim, I’ve had it set to “Requests appear to come from the ISA Server computer.”  So, everything from referrers to log files show the IP address of my ISA server, bleh.

Finally, last night, I had time to figure out the problem.  I knew I needed to head over to ISAserver.org, but I didn’t realize how fast it would be to find the answer.  Basically, since my ISA server, isn’t acting as a gateway on my network, it can’t be set to requests come from original IP.  However, by making the ISA server the gateway on my web server, everything works the way I want.  Unfortunately, this means that I can’t route outside of my network on the web server anymore, but since it’s just a virtual machine used to serve static webpages anyways, this isn’t a big deal.

So, to recap, NTLMv2 responses are time sensitive and ISA must be your webserver’s gateway if you want requests to appear to come from the original client.
 

 

Let me count the ways Project Server 2003 sucks.

1. The installation is crazy convoluted
2. When using the ad sync, first or last name cannot contain a “-”, “[”, “]”, or an extra space at the end
3. When using the ad sync, display name cannot contain an extra space at the end
4. There is absolutely no online documentation for problem solving

For those that may be having similar problems that I am, and can’t find a solution to save themselves, I was getting multiple errors while using the AD Sync tool in Project Server 2003.  Additionally, apparantely, you can’t just have it sync with Domain Users for some unknown reason, it just plain doesn’t work.  However, there are other undocumented “features” like the above. 

For example, you may get the error:

Component: AD Connector
File: AutoADProcess
Line: -1
Description: CDATA[AD Res Pool Sync – PDS ADD Res failed : USERNAME]

Followed by:

Component: AD Connector
File: AutoADProcess
Line: -1
Description: CDATA[AD Res Pool Sync – failed to issue the PDS Resource Add request]

This error is because of either problems number two or three listed above.  Be sure to run through all usernames that are giving errors and correct them, because it appears as if one error causes the whole AD Sync script to fail.  That’s some quality coding right there.  Good error catching there MS.  Talk about crazy fun to troubleshoot.

Update 2/21/2006—This post has been updated to NOT break the RSS feed.

Today marks the 4 completed test since starting in December. My re-evaluation of the situation has given me a goal of being done by the end of March. The way that I’ve been rolling through these last 2 weeks, I’m not really that worried either.

Unfortunately, because of ordering a book, this fourth test doesn’t mark me getting my MCSA. Instead, I’m not going to get my MCSA until I receive my MCSE. This doesn’t really matter, since my company only cares that I get my MCSE within a year of hire anyways. And since I’m not going to have a problem doing that, I figure that I’ll make my studying easier on me.

Basically, I’m going for my MCSE:Security, and from what I’ve heard, if you study and pass the 70-299 (elective), you shouldn’t have too much more studying for the 70-298 (required). So far I’ve completed the 70-270, 70-290, 70-291, and 70-293. I’ll study for the two security exams by reading a MS Press Book on the flight to and from Puerto Vallarta (not while I’m there though), which will give me a good running start.

I figure I can get the last test before the two security exams done before I even leave on the 24th, which would get me sitting pretty to have my goal of being done before the end of March.

Update 2/22/06—Only two left now!  :cheese:

Update 3/6/06—Only 1 left for MCSE, and 2 left for MCSE: Security!

I’m sure everyone remembers my praise of Microsoft Certification Tests from last time I talked about them, but now I come with new found knowledge and an external pressure (having to get it done fully certified in one year).  For those of you that don’t know, I’m now an MCP (yes Nick and Jason, I can do the dance/handshake now).  Actually, I’m closer to being an MCSA than MCP, but who’s counting. 

Now, this may come as a surprise to those that I have worked with before, as I don’t hold the tests in very high regards.  This is mostly due to the people were MCSE Certified, and the messes they left me to clean up.  Plus there was the horrible taste in my mouth after I took my first test under a year ago.  Not to give myself excuses, but looking back, that first test wasn’t as bad as I made it out to be.  Yes, I don’t doubt that I should’ve passed, but just reading the book without taking any sort of practice test probably wasn’t the smartest thing to do.  Granted, I did pretty much the exact same thing this time, with minimal (read about 30 mins before each test) review for both the Windows Server 2003 and Windows XP.  Honestly, I don’t think it has anything to do with the amount of review time I put towards it, and instead how much I’ve actually used the product. 

Now after I’ve completed both of those tests, looking back, I realize it is a fairly decent test.  It shows if you really know the material, I guess.  I think the last time I took it, I was just so nervous, and when I started seeing the complex questions I paniced more than anything.  This time around, I knew that I knew the material, so it was much easier, and quite painless.  However, at the end of the test it was still hard to push the completed button. 

I’m just hoping the other tests I have go just as easily.  I know, though, that I’m going to have to spend more time on each of them instead of just flying off the cuff, as I don’t know as much intricacies with AD, networking, etc.  Actually, I tried with the Networking I test, and amazingly didn’t do that bad.  Unfortunately, much like the first time I took the Windows 2003 test, though, I failed, but by such a small amount that I’m sure if I would’ve taken it the next day I would’ve passed.  Oh well, such is life.

Four more in 9 months.  It sounds like a long time, but going home and studying is not what I call a fun time.  Hopefully I can mash out a bunch within a week to keep me from spreading it out too much.