Well, in windows 2008, the application does not do this. Instead, you need to set this up manually. In earlier versions of windows, windows authentication is added as a feature automatically. In windows 2008, it is an installable module. I had to go into the IIS roles and check windows authentication. Once this was done, it required a restart of the IIS services. I then went into the website instance and enabled windows authentication. Once done, the web application worked as expected.

I wonder why this option is no longer installed automatically by windows. I understand that Microsoft is continually trying to make IIS more secure, but I’m not entirely sure that this was a good move. By default, website instances are setup as anonymous access and you need to allow other authentication methods. If anonymous access and another authentication method is checked, the website breaks. Therefore, I just don’t understand why windows authentication is not installed as a default installation.

6-24: 07:18:55.296 My Connections\wvenezia@bitxbit.com – Initiating IKE Phase 1 (IP ADDR=160.79.51.201)
6-24: 07:18:56.108 My Connections\wvenezia@bitxbit.com – SENDING>>>> ISAKMP OAK AG (SA, KE, NON, ID, VID 6x)
6-24: 07:19:11.239 My Connections\wvenezia@bitxbit.com – message not received! Retransmitting!
6-24: 07:19:11.239 My Connections\wvenezia@bitxbit.com – SENDING>>>> ISAKMP OAK AG (Retransmission)
6-24: 07:19:26.261 My Connections\wvenezia@bitxbit.com – message not received! Retransmitting!
6-24: 07:19:26.261 My Connections\wvenezia@bitxbit.com – SENDING>>>> ISAKMP OAK AG (Retransmission)
6-24: 07:19:41.283 My Connections\wvenezia@bitxbit.com – message not received! Retransmitting!
6-24: 07:19:41.283 My Connections\wvenezia@bitxbit.com – SENDING>>>> ISAKMP OAK AG (Retransmission)
6-24: 07:19:56.303 My Connections\wvenezia@bitxbit.com – Exceeded 3 IKE SA negotiation attempts

I had initially thought it was due to the virtualbox blocking the IKE packets from reaching the gateway, but then decided to take virtualbox out of the picture and troubleshoot this like a normal computer.  Once I did this, it only took me 10 minutes to figure out what is wrong.  The message not received means that the remote host did not get the packet and the retransmission means that the remote host is not responding.  Well, that would indicate that the netscreen software is sending out the packets right but the gateway is a no show.  I thought, maybe I used an old Security Policy.  I opened up my working laptop and compared it to the virtualbox pc, and sure enough, the gateway ip addresses are different.  Once I changed this, it started working without a charm!

This makes me very happy as I am tired of carting my laptop with me to use my vpn!

Today, it was outlook that was the memory leak, but due to Outlook and its need to consume more ram than the computerh as, I noticed this funny process – gtbe12.tmp.exe.  I thought for sure that I picked myself up a bug until I did a bit of research and it seems that it is hooked into google’s toolbar.

Sure enough, I had used IE7 the last time I had the computer open and google toolbar was installed on it.  As part of my initial process to get my computer working again, I did close down IE7.  While researching the issue, the process ended shortly after IE closed.  This corresponds with the internet’s account that the process is associated with IE + google toolbar.

The end result?  While I vote for spyware (and depending on how you view Google’s actions with their toolbar, you can more legitimately say that it is spyware) this process is ok to leave alone.  I would definitely keep my eye on it, but it appears to be temp executable files pertaining to updating the toolbar’s files.  After letting it run (once my computer stabilized from outlook), it did stop appearing…

NETEXPRO3.EXE has been seen to perform the following behavior:

• Enables an In Process Object/Server – Common with DLL Injections
• Can communicate with other computer systems using HTTP protocols
• Executes a Process
• This Process Deletes Other Processes From Disk
• This process creates other processes on disk
• The Process is packed and/or encrypted using a software packing process
• The process hooks code into all running processes which could allow it to take control of the system or record keyboard input, mouse activity and screen contents
• Registers a Dynamic Link Library File
• Adds products to the system registry
• Reads your outlook address book
• Enables a COM Object/Server on the Local Machine
• Communicates with other computers using FTP connections

NETEXPRO3.EXE has been the subject of the following behavior:

• Created as a process on disk
• Executed as a Process
• Deleted as a process from disk
• Terminated as a Process
• Has code inserted into its Virtual Memory space by other programs
• Enabled as a COM Object/Server on the Local Machine

My personal experiance is actually pretty close to what this website has to say.  I had a user complain that outlook was freezing up and when I reviewed task manager, I noticed netexpro3.exe taking up 100% of the CPU.  Once I killed the task, outlook started to respond and the CPU went back down to normal.  I am running a malwarebytes scan, and I am hoping that this will find whatever it is and kill it.  If I continue to have issues with it, I’ll let you know how I resolved the issue

If push comes to shove, it is better to remove this than to have your C drive run out of space.

Click on Start and then Run.

In the text box in the Run window, type msconfig and click OK. This will open the System Configuration Utility program.

Note: Do not make changes in the System Configuration Utility other than those outlined here to avoid causing serious system issues. This utility controls a number of startup activities other than those involved with Safe Mode.

Click on the BOOT.INI tab located at the top of the System Configuration Utility window.

Check the checkbox next to /SAFEBOOT and click OK.

You will then be prompted to either Restart, which will restart the PC immediately, or Exit Without Restart, which will close the window and allow you to restart the PC manually.

After the restart, the PC will automatically boot into Windows XP Safe Mode.

Note: Windows XP will continue to boot into Safe Mode until the System Configuration Utility is configured to again boot normally.

When your work in Safe Mode is complete, click on Start and then Run. Type msconfig in the text box and click OK.

This will again open the System Configuration Utility program.

Choose the Normal Startup radio button and click OK.

You will then be prompted to either Restart, which will restart the PC immediately, or Exit Without Restart, which will close the window and allow you to restart the PC manually.

After the restart, the PC will boot into Windows XP normally and will continue to do so

For information about this can be found here.

Why?

I’m glad you asked.  The reason being is that SearchIndexer is Windows Desktop Search utility that is supposed to perform better than Google Desktop.  Due to my huge email size and amount of emails I receive, it takes up a lot of resources to index it and perform faster searches.

Lets think about that for a second.  The Windows Desktop Search is supposed to make my searches and windows experience better, by making my computer run slower?  This just cannot be the Microsoft way.  Once I realized what this utility does and how it is not appropriate for my usage (I may use the search utility 1 or 2 times a year, if I’m lucky) I decided to give it the axe.

Here are the directions on how to remove the Windows Desktop Search

Go to add/remove utilities

Remove Windows Desktop Search

The end…simple right?  Oh Microsoft and their silly ways.  To be fair, I hate google desktop too.  I don’t know why people can’t just remember where they put their documents or emails…

http://forums.ipswitch.com/Topic49616-14-1.aspx

This details a script workaround on how to resolve this.

http://support.microsoft.com/kb/949701

This is the link that microsoft admits that they broke something that used to work correctly…

You need to poke a hole through the firewall at port 445.  Once completed, you should be able to access your windows network share, assuming that this is configured properly.  If the firewall still rejects the traffic, poke a real hole in it and watch it suffer the fate that all firewalls should.

Perhaps this is why my specialty is not in firewalls/routers….NAH!

“Naming information cannot be located because: no authority could be contacted for authenication.”

I found the following microsoft KB which helped me see that there was little to be done:

http://support.microsoft.com/kb/284929

This behavior can occur when Domain Name Service (DNS) is not correctly configured.

To resolve this behavior, make sure that the zones on your DNS server are configured correctly and that your DNS server is authoritative for the zone that contains the Active Directory domain name.

Try again to start the Active Directory Users and Computers snap-in. If you receive the same error message, use the DCPROMO utility to remove Active Directory, restart your computer, and then use DCPROMO to reinstall Active Directory. Verify that Active Directory has been installed successfully.

Before you install Active Directory, you must install and configure a DNS server that is authoritative for your Active Directory domain name. Active Directory depends on DNS to function correctly and requires the creation of the SYSVOL share.

NOTE: The SYSVOL share must be installed on an NTFS partition. At least one NTFS partition must be present on your domain controller in order to install Active Directory.

To verify that Active Directory has been installed successfully:

1. Start DNS Manager, and then verify that the correct DNS entries have been created, by comparing the entries in DNS Manager with the entries in the Netlogon.dns file, which is located in the %SystemRoot%\System32\Config directory.
2. Verify that the SYSVOL share has been created, and that it contains the NETLOGON share and the Policy and Script folders.
3. Start the Active Directory Users and Computers snap-in, and make sure that your domain controller appears in the Domain Controllers container for the domain you specified.
4. Open Event Viewer, and then review the entries in the File Replication Service Log, the DNS Server Log, and the System Log to make sure that Active Directory has been successfully installed.