System.Security.SecurityException: Requested registry access is not allowed. when writing to event log

I got this error when I try to create an eventlog source and when I try to write to the new event log (after resorting to manually creating the event log source) with my ASP.NET application.
See the end of this post for the full error message and stack trace.
This seems to be a very commom problem - and not consistent either. My guess is that it's due to the tightening of security recently, ie XP SP2. Use of the Network Service account (on win2k3) or AD accounts can help.
To resolve you need to give the ASP.NET user permission to read from the event log registry entries. And here's how:
1. Select Start - Run, then enter: regedt32
2. Navigate/expand to the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Security
3. Right click on this entry and select Permissions
4. Add the ASPNET user
5. Give it Read permission

Error : ASP.NET Webservices: "The request failed with HTTP status 401: Access Denied." Error

We can resolve this issue by either of the following ways:
1. Enabling Anonymous Access in the IIS Directory Security
To do this, the following steps will help you.
1. Click "Start" - "Run" - Type "inetmgr" and press "Ok" or "Enter" Key
2. IIS Control panel opens.
3. Expand the appropriate nodes and navigate to the virtual directory of your Web Service Application.
4. Select the Virtual directory, Right Click and select "Properties"
5. Switch to the "Directory Security" Tab and then Click "Edit".
6. Check the "Anonymous Access" CheckBox.
7. Click "Ok" twice to exit.

This should solve the issue

Get IP Address of a HOST in VB.NET

The .Net DNS class can be used to get a host name or an IP of a given host name. To use DNS class in your project, you need to include System.Net.

Include System.Net Reference.

And say I want to get IP address if http://www.google.com The given code will do that for you.

Imports System
Imports System.Net
Namespace DNSName
'

' Summary description for Class1.
'
Class Class1
'Entry point which delegates to C-style main Private Function
Public Overloads Shared Sub Main()
Main(System.Environment.GetCommandLineArgs())
End Sub
Overloads Shared Sub Main(args() As String)
Dim ipEntry As IPHostEntry = Dns.GetHostByName(http://www.google.com/)
Dim IpAddr As IPAddress() = ipEntry.AddressList
Dim i As Integer
For i = 0 To IpAddr.Length - 1
Console.WriteLine("IP Address {0}: {1} ", i, IpAddr(i).ToString())
Next i
End Sub 'Main
End Class 'Class1
End Namespace 'DNSName

Error: Unable to Start Debugging on the Web Server

When you try to debug an application (ASP.Net 2) running on a Web server, you may sometimes get this error message:

Unable to start debugging on the Web server

If your message is longer than that, it is covered by a subtopic of this one.

1- Review the procedures for setting up ASP.NET or ATL Server. For more information see Getting Ready to Debug ASP.NET Applications.

2- Do you have the necessary access privileges for debugging? For more information see the Security Requirements section in

3- checking SSL (Security Socket layer) & Trying to open website again without SSL.

4- From a command prompt window, run the following command: systemroot\Microsoft.NET\Framework\ versionNumber \aspnet_regiis -i

Our Reference :

http://msdn.microsoft.com/en-us/library/dwesw3ee(VS.80).aspx

 Secure Sockets Layer :
SSL is cryptographic protocols that provide security and data integrity for communications over TCP/IP networks such as the Internet. TLS and SSL encrypt the segments of network connections at the Transport Layer end-to-end.

Several versions of the protocols are in wide-spread use in applications like web browsing, electronic mail, Internet faxing, instant messaging and voice-over-IP (VoIP).
 

SSL has a variety of security measures:

• The client may use the certificate authority's (CA's)
  public key to validate the CA's digital signature on the server certificate.
  If the digital signature can be verified, the client accepts the server
  certificate as a valid certificate issued by a trusted CA.
  
• The client verifies that the issuing CA is on its list of trusted CAs.
  
• The client checks the server's certificate validity period. The
  authentication process stops if the current date and time fall outside of the
  validity period.
  
• Protection against a downgrade of the protocol to a previous (less secure)
  version or a weaker cipher suite.
  
• Numbering all the Application records with a sequence number, and using this
  sequence number in the message authentication codes
  (MACs).
  
• Using a message digest enhanced with a key (so only a key-holder can check
  the MAC). This is specified in RFC 2104. TLS only.
  
• The message that ends the handshake ("Finished") sends a hash of all the
  exchanged handshake messages seen by both parties.
  
• The pseudorandom
  function splits the input data in half and processes each one with a different
  hashing algorithm (MD5 and SHA-1), then XORs them together to create
  the MAC. This provides protection even if one of these algorithms is found to be
  vulnerable. TLS only.
  
• SSL v3 improved upon SSL v2 by adding SHA-1 based ciphers, and support for
  certificate authentication. Additional improvements in SSL v3 include better
  handshake protocol flow and increased resistance to man-in-the-middle attacks.
  

SSL v2 is flawed in a variety of ways:

• Identical cryptographic keys are used for message authentication and
  encryption.
  
• MACs are unnecessarily weakened in the "export mode" required by U.S. export
  restrictions (symmetric key length was limited to 40 bits in Netscape and
  Internet Explorer).
  
• SSL v2 has a weak MAC construction and relies solely on the MD5 hash
  function.
  
• SSL v2 does not have any protection for the handshake, meaning a man-in-the-middle downgrade attack can
  go undetected.
  
• SSL v2 uses the TCP connection close to indicate the end of data. This means
  that truncation attacks are possible: the attacker simply forges a TCP FIN,
  leaving the recipient unaware of an illegitimate end of data message (SSL v3
  fixes this problem by having an explicit closure alert).
  
• SSL v2 assumes a single service, and a fixed domain certificate, which
  clashes with the standard feature of virtual hosting in webservers. This means
  that most websites are practically impaired from using SSL. TLS/SNI
  fixes this but is not deployed in webservers as yet.

SSL v2 is disabled by default in Internet Explorer 7, Mozilla Firefox  and Safari. After
it sends a TLS ClientHello, if Mozilla Firefox finds that the server is
unable to complete the handshake, it will attempt to fall back to using
SSL 3.0 with an SSL 3.0 ClientHello in SSL v2 format to maximize the
likelihood of successfully handshaking with older servers.Support for SSL v2
(and weak 40-bit
and 56-bit ciphers) has been removed completely from Opera .

Can't Login using new account on Active Directory on my Windows Server 2003

A.A

I had problem with Active directory. where i created a new DNS on my Windows2003
and trying to install active directory using command "DCPROMO.exe"

you can reed this article to install active directory on win2003
http://www.petri.co.il/how_to_install_active_directory_on_windows_2003.htm

after I finished from installation AD, i created new user on my new domain (active directory )

but i can't login on my machine using new user loginaName (must allow him to login local in server)

solution in steps ;

• Click Start --> Programs --> Administrative Tools, and then click Domain Controller Security Policy.

• Double-click the Security Settings folder, double-click Local Policies, and then click User Rights Assignment.
• Under the Policy column, double click “Allow Log on Locally”.
• Click “Add User or Group”, and then select the user to be added.
• Click OK, click OK, and then click OK.

Publish Post

• Thanks for every one help me