Sandro Zamboni

In my case, I found the solution to this problem was to manually create the directories "auth \ ddm.box" into the directory "imbox" as shown in the image below:

I hope it's useful!

Thursday, October 21, 2010

Limiting the size of pst file

A critical point in the administration of any network is the file used to archive e-mail messages from Microsoft Outlook clients, the famous ´ s pst files.

Something critical in administering these important files is the administration of the same size, since a very large PST in addition to causing slowness in searches of messages, the large size can (and probably will) cause corruption of the file.

For Microsoft Outlook 2003 and 2007 (not yet tested in 2010 … .. but I believe that works well) we limit the size of PST by changing registry keys on the workstations.

Here's a link:

http://support.microsoft.com

Monday, August 16, 2010

Service overview and network port requirements for the Windows Server system

Staff,

Follow the link for a very important article that lists the ports required for miscellaneous services infrastructure provided by Windows Server. very useful!!

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

Friday, July 30, 2010

Blacklists

Ladies and gentlemen,

I'm posting link ´ s site to test if your IP is: blocklists

http://www.blacklistcheck.com

http://www.dnsbl.info/dnsbl-database-check.php

http://whatismyipaddress.com/blacklist-check

http://www.blacklistalert.org/

http://www.mxtoolbox.com/blacklists.aspx

I hope it is useful.

Windows Server 2008 R2 and Windows 7 Service Pack 1 BETA

The betatesters!! Here's a link to download the beta version of Service Pack 1 on Windows Server 2008 R2 and Windows 7 …
http://www.microsofttranslator.com/BV.aspx?ref=BVNav&from=&to=en&a=http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Fevalcenter%2Fff183870.aspx

Friday, July 23, 2010

POP3 in Windows Server 2008

Staff,

Follows a link to a cool tutorial for installing the SMTP and POP3 services in Windows Server 2008.

http://jebass.blogspot.com/2009/02/making-pop3-smtp-server-work-with.html

Att.

Wizard ´ s for creating records policy framework (SPF)

The SPF record is used as a form of control and authenticity of servers that are responsible for sending emails in a domain, so the SpamCheck ´ s …

To assist in creating these records in DNS, follows below two WIZARD ´ s:

http://www.microsoft.com/mscorp/safety/content/technologies/senderid/wizard/

http://old.openspf.org/wizard.html

I hope it's useful!

Sunday, June 27, 2010

GPO Search

Ladies and gentlemen!

I've been googling and found a very cool application provided by our Windows Azure … it is a website where we can search GPO and registry settings!! Pretty cool, what's more we have provider for IE 7 and 8.

http://gps.cloudapp.net/

Quick video showing the Following uses of the site ...

RPC integrity checking for DNS requests in Windows Server 2008 R2

Staff, a new security feature of Windows Server 2008 R2 must take our attention, which is the RPC integrity checking for DNS requests. This feature is not supported on Windows 2000 DNS and Windows Server 2003.

Because of this verification, in a mixed environment and migration where we will have the coexistence of servers and workstations running legacy systems, it may be necessary for disable this feature because it can cause failure in the external name resolution in DNS clients running Windows Server 2003, 2000 and XP do not have problems on clients running Windows 7.

Unfortunately discovered feature in the worst way (during a migration process, experiencing the symptoms mentioned above) and not by study … so I'm posting it because it is a resource which we have a few references and believe to be useful! below is the command to disable the security feature:

Dnscmd.exe /Config /RpcAuthLevel 0

…. to activate the feature, just change-mos value from 0 to 1 … as shown.

Dnscmd.exe /Config /RpcAuthLevel 1

For us to verify the current status of the configuration, we can use the parameter /info:

Dnscmd.exe /info /RpcAuthLevel

I hope it's useful!

Monday, May 3, 2010

Configuring IMAP4 and POP3 in MS Outlook 2007, 2010 with Exchange Server 2007.2010 published with ISA Server 2004, 2006 and Forefront TMG

Personnel, after catching a little error messages as 0x800CCC80, 0x800CCC6a, event ID 4625, etc… decided to post the required settings for configuring Microsoft Outlook 2007, 2010 for IMAP4 and POP3 connection with default settings for Exchange Server 2007, 2010 published with ISA Server 2004, 2006 and Forefront TMG. Do the settings for an account using the IMAP4 Protocol, however all settings apply POP3 accounts, exeto by the number of ports.

The first step is to configure the user information, server and log on as the image below. Recalling that we can inform the IP servers.

After filling out the fields with the required information, we must configure the connection information as follows:

On the tab "Outgoing server" option "my outgoing server (SMTP) requires authentication" should be unchecked.

And "Advanced" tab in the IMAP server must meet in 147 port (default) and the type of TLS, encryption of the connection to the SMTP server using the default port (25) Protocol and no encryption type for the connection.

Ready! after these settings are only test.

Note:-settings can vary according to the settings made on the CAS Server as well as in the firewall.

Tuesday, March 23, 2010

Level 300:-DNS – Flow of DNS name resolution for Microsoft clients

In this article we will tackle the flow of DNS name resolution from equipment running Windows 2000 and later is very important to know-mos this flow, primarily involves troubleshooting.

In pre-Windows 2000 clients, we primarily NetBIOS name resolution that does not necessarily need to be used in Windows 2000 and later systems, which use DNS name resolution as a primary method.

DNS names are divided into two parts as shown below:

WWW. Z1BR.com

ZAMBONIS.Spaces.live.com

COMPUTER01.LOCAL WOODGROVEBANK.

This structure consists of host name (in yellow) and DNS suffix (in red).The host name is associated with a record in DNS that points to an IP address and the DNS suffix associated DNS zone where registry.

Now that we are reminded of how the structure of DNS names, let's look at how the flow of name resolution.

Let's take as an example of a user who wants to access a network share; the user enters \\ServerFS01\SharedFolder

The first step is to complete the requested host name with the DNS suffix of agreement as specified in the network connection properties, clicking on properties of TCP-IP (in both IPv4 and IPv6) version click on the button "Advanced" and the DNS tab as shown in the image:

Is selected by default, the option "Append parent suffixes of the primary DNS Suffix", this option will add the suffix father of MACHINE names requested which was not specified the FQDN, as in our example. Note that below this option we choose in choose a suffix list; in the case of having multiple domains for example (the suffixes are added to the list, in order, until you found the host), with this procedure we can expedite workstation, in a large forest. Another option we configure statically would add a DNS suffix for the connection (this setting will not be changed automatically).

With regard to the primary suffix of the machine, we can find it in the "Advanced properties of the system" in the "computer name" tab, as shown in the picture on below (note that the suffix is by default changed automatically when the machine is joined to a new domain); for security reasons, some organizations desmarcam this checkbox, which can cause name resolution problems if the analyst update manually the primary suffix.

After completing the host name with the DNS suffix, the next system procedure is to check the machine's DNS CACHE function local DNS cache is to expedite the process of resolving names in addition to decrease network traffic; we can see this cache through ipconfig/displaydns command and erases it via ipconfig/flushdns command.

You can disable logging cache through the command net stop DNSCACHE or disabling the DNS Client service by service console (services.msc).

In the local DNS CACHE can be stored records positive responses resolved successfully by the DNS server) and negative records (answers resolved by the DNS server on which the DNS client cannot connect to the host, such as the status of "host not found" when we access a URL. by default, the storage time for a record in the DNS cache is 86,400 seconds (1 day) and a negative record of 900 seconds (15 minutes). However we modify this period by editing the registry:

To define the period of storage of positive and negative records, overwhelmed by the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNSCache\Parameters
- For editing storage records POSITIVE we must create a new DWORD value with the name MaxCacheTtl (this value must be established in seconds; the default value is 86400).
- For editing storage records NEGATIVE we must create a new DWORD value with the name MaxNegativeCacheTtl (this value must be established in seconds; the default value is 900).

If the requested name is not resolved by the DNS cache, the next step would be to consult the hosts file located in the directory%windir%\System32\drivers\etc\. The hosts file contains static entries and is typically used to expedite the process of resolving names, pre-population of DNS cache, for environments in "workgroup" as in a DMZ or still to block sites. We use cautiously the hosts file, because it is a way to decentralise the resolution of names; what can cause problems for a resolution, if there are changes in settings of TCP-IP hosts mapped. Below is the video where I show an example of editing the hosts file:

The next step is to forward the request to the preferred DNS server configured on the properties of TCP-IP of the network interface. If the preferred DNS server is offline, or for any reason the DNS client does not have server connectivity, name resolution request is forwarded to the secondary DNS server, if the same is also without communication with the client, the request is forwarded to another DNS server that is listed at the top of the list of DNS servers in the DNS tab of the advanced settings of TCP-IP. The list is checked from top to bottom, what makes recommended placing at the top of the list, the same site and servers, or servers of sites where the link to connect to the DNS client has the highest bandwidth available.

When the request arrives at the DNS server, the server performs the following procedures to try to resolve the host:

1-server's cache (this is not the same DNS cache commented previously, and yes the cache of DNS service);

2 – DNS zones (… search server hosting areas …)

3 – search in the WINS database (if configured …with this feature server searches the database of the WINS servers listed to verify the existence of the requested record.)

4 – conditional forwarders (requisitions routing rules for a given domain DNS)

5 – Forwarders (… forwarding for any request that the server does not resolve)

6 – Root Hints (… servers responsible for the root domain (".") on the Internet)

Note: these DNS server resources will be covered in detail in the next articles in the series

Friday, March 12, 2010

RAID

As promised to students 6430, follows the link to Wikipedia for RAID … actually link is pretty cool:

http://en.wikipedia.org/wiki/raid

I hope that is useful!

Sunday, March 7, 2010

Windows Server 2008 R2 with Windows 7 theme

Ladies and gentlemen,

Just to relax a little, I am posting a video, where I show how to enable the theme of Windows 7 on Windows Server 2008 R2. This feature is used so that the terminal Service user, have an experience similar to the Windows environment 7 … requirements:

Windows Server 2008 R2
Video card is configured with the correct driver.

Monday, February 15, 2010

Configuring NLB Cluster in Windows Server 2008

In this article, I show how to set up an NLB cluster in Windows Server 2008.

I will create a cluster with only 2 nodes that are configured as follows:

Node 1:

IP : 192.168.0.1
Mask : 255.255.255.0
Node 2:
IP: 192.168.0.2
Mask: 255.255.255.0

The cluster is with IP 192.168.0.3

The first step is to install a feature of Network Load Balancing (NLB) on both nodes of the cluster, click Start, Server Manager, Features and Add Features.As the figure below:

In the Add Features Wizard check the Network Load Balancing, click NEXT and the INSTALL button to install the feature

Click CLOSE after the installation completes.

Click START, Administrative Tools, and Network Load Balancing Manager

Click Right-click Network Load Balancing Cluster and select New Cluster

In New Cluster: Connect, type the ip or name of a node in the cluster and click the Connect button.After the interface is connected, click NEXT

In the Host Parameters, select the priority of the IP addresses of the nodes and the state of initial activity of the node to join the cluster. ... And click NEXT

Click ADD and add the cluster IP address (this is the IP address to be accessed by customers) ... after completing the settings, click OK and NEXT button.

Choose the operating mode of the cluster ... will choose the unicast mode (which will cause the MAC address of network interfaces of the servers (we) are equal to the virtual MAC address of the cluster). Click NEXT

In the Port Rules by clicking the ADD have the option to create rules for the cluster to meet requests only on certain ports.Leave the default option (from 0 to 65535). Clique em FINISH… Click FINISH ...

... Our NLB cluster is almost ready, lack now add the second node to the cluster. To do this, click the right-click the cluster and select Add Host to Cluster as shown in the figure below ...

In the Add Host to Cluster: Connect, type the name or IP of the server that will be another cluster node and click the Connect button. After the interface is connected, click NEXT

In the Host Parameters, select the priority of the IP address of another node and the state of the initial activity even when entering the cluster. ... And click NEXT

Set again the port rules to the other node and click FINISH

We have our NLB cluster running.

Now, to test, I run the PING command (from a client station) while the dedicated IP's of the two nodes (192.168.0.1 and 192.168.0.2) and the cluster's IP (192.168.0.3) ...

... I will now disable the network interface of one of us. The expected result is that it does not lose connectivity with the cluster (192.168.0.3).

I hope it's useful!