Event ID 1003 Source DHCP

Source = DHCP
Type = Warning
Description = Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address . The following error occurred:
. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server."
----------------------------------------------------------------------------------------------------------------------------------
Adrian Grigorof (Last update 9/25/2008):
If the DHCP server works properly then this generally means a network or connectivity problem. Try to isolate the physical equipment that connects the workstation in question to the DHCP server.

Reported errors:
- The semaphore timeout period has expired.
- An operation was attempted on something that is not a socket.

As per Microsoft, these events may be recorded on ISA server that is using DHCP to obtain an address for the external network card. The suggested resolution is to uUse the System Policy Editor inside the ISA 2006 Management Console to enable DHCP from External networks.

These settings apply to the ISA server as a DHCP client only. All rules
governing DHCP service TO clients should be configured via normal firewall
policy rules.

1) Open the ISA Server Management console (msisa.msc)
2) Expand the ISA server object, right-click on Firewall Policy, and select
Edit System Policy.
3) Under Network Services, select DHCP. There are two configuration tabs for
DHCP: General and From.
4) On the General tab, check Enable to allow access between trusted DHCP
servers and the ISA server. This option is enabled by default.
5) On the From tab, click the Add button.
6) Expand Networks, select External and then click the Add button.
7) Click Close and OK to finish editing System Policy rules.
8) Click Apply to save changes and update the configuration.

information from >> http://www.eventid.net/display.asp?eventid=1003&eventno=1478&source=DHCP&phase=1

Network is not present or Network not started error while trying to connect to any network folder

Trouble:

When ever I try connect a any folder through Start >> Run and type file://192.168.xxx.xxx/foldername and error comes up: The Network is not present or not started in windows 2003

Service Overview:

This problem is quite unusual, as this problem basically occurs because of a windows network service is stopped.

How to fix it:
1.Open Start >> Run and type “Services.msc” ( without quotes ) and press OK
2. Locate the service named Workstation.
3. Right Click on the workstation service and select properties, you will see a window shown below.
4. Click on the Start button to start the service, starting this service will fix the trouble.


We hope solution provided above will help to fix the trouble, if you have any other solution regarding this problem please share it through comments.

Read more: http://www.troublefixers.com/network-is-not-present-or-not-started-error-while-trying-to-connect-to-any-network-folder/#ixzz0MjH6YvG5

how to change scan action for "Generic" virus

-------
Step I: Configure and deploy scan action for "Generic" virus type to OfficeScan clients, please do the following:
-------
1. Open the "ofcscan.ini" file in the "\PCCSRV\" folder on the OfficeScan installation directory.
2. Under the "[Global Setting]" section, add the following keys and assign the appropriate value to each key.
[Global Setting]
1stActForGenericVirus={x}
2ndActForGenericVirus={y}
Where:
{x} is the first action
{y} is the second action
Replace {x} and {y} with the value corresponding to the scan action you want to use:
0 - Pass (permanent)
1 - Rename
2 - Move
3 - Clean
4 - Delete
5 - Pass (temporary) - this is the default action in OfficeScan 8.0
Example:
[Global Setting]
1stActForGenericVirus=3
2ndActForGenericVirus=4
3. Save the file. Open the OfficeScan server Web console and go to "Networked Computers > Global client settings" screen.
4. Click "Save" to deploy the setting to clients.
--------
Step II. Set scan action not to use "ActiveAction"
--------
1. Networked Computers>Client Management>Settings>Realtime-Scan Settings>Action Tab
2.Then in Realtime-Scan Settings screen, ensure that the checkboxes for both virus/malware and spyware/grayware are enabled.
3.Go to the Action Tab and select " Use a specific action for each virus/malware type". For each threat, specify your prefered scan action(ei. First Action: Clean, Second Action: Quarantine/Delete).
Note: For "Other Threat" set First Action: Clean and Second Action: (Quarantine or Delete).
===

Command to check RAM in AIX UNIX

$ svmon -G

Count number of CPU socket in IBM AIX

$ lsconf grep proc command giving o/p as follow.

+ proc0 U0.1-P1-C1 Processor

+ proc1 U0.1-P1-C1 Processor

+ proc2 U0.1-P1-C2 Processor

+ proc3 U0.1-P1-C2 Processor
in above is each line shows chip or core ?
$lsdev -C -c processor
proc0 Available 00-00 Processor

proc1 Available 00-01 Processor

proc2 Available 00-02 Processor

proc3 Available 00-03 Processor

How can I move the Active Directory (AD) Global Catalog (GC) to another domain controller (DC)?

How can I move the Active Directory (AD) Global Catalog (GC) to another domain controller (DC)?
You don't actually move the GC between servers. Instead, you simply enable the GC on a new server, then disable the current GC. I explained how to configure a new server as a GC in the FAQ "How do I configure a server as a Global Catalog?".
Keep in mind that if you already have one GC in the domain, you won't want to disable that GC until after your new one has received all the existing GC content. You can check this progress by using Event Viewer to view the Directory Services log. Specifically, you'll want to look for event ID 1119, as this figure shows, which tells you that the new server is now advertising itself as a GC server. Before event ID 1119 appears, you should see event ID 1110, which is the new server advising you of a delay (typically 5 minutes) before the new server will start advertising.
In summary, enabling a new GC is a three-step process: 1. Enable the GC on the new server (open the Microsoft Management Console--MMC--Active Directory Sites and Services snap-in, navigate to Sites, select the name of the site that will contain the new GC server, navigate to Servers, select and expand the name of the new GC server, right-click NTDS Settings in the left-hand pane, select Properties, then select the Global Catalog check box).
2. Wait until event ID 1119 appears in the new GC Directory Services event log.
3. Disable the GC on the old server (in the Active Directory Sites and Services snap-in, navigate to Sites, select the name of the site containing the old GC server, select and expand the name of the old GC server, right-click NTDS Settings in the left-hand pane, select Properties, then clear the Global Catalog check box).
If you add or remove GCs and you use Exchange Server, you must reboot the Exchange servers to let them update the DSAccess topology report and begin using the new GCs--otherwise Exchange won't discover the GCs and use them for DSAccess. To create its AD topology view, DSAccess
1. calls the Directory Service (DS) Locator service
2. retrieves a list of all DCs and GCs from the local AD site
3. contacts each server in the list
4. caches as many as 10 active DCs and 10 active GCs
5. reorders the active-GC list so that domain-local GCs are at the top of the list
6. uses the cached DC and GC server list on a simple round-robin basis for global information lookups.

Thank you very much for your kindness

John Savill

John Savill is an advisory architect for EMC’s Microsoft consulting practice. He’s an MCITP: Enterprise Administrator for Windows Server 2008 and a nine-time MVP. His latest book is The Complete Guide to Windows Server 2008 (Addison-Wesley).Email address: john@savilltech.com

Access-based Enumeration

Abstract
Access-based Enumeration (ABE) has been included in Microsoft® Windows Server™ 2003 Service Pack 1 to a) increase folder level security, b) improve administrator productivity by reliably streamlining large directory structures for less-technically savvy users, and c) provide a more seamless migration experience for end-users migrating to Windows servers. ABE filters shared folders visible to a user based on that individual user’s access rights, preventing the display of folders or other shared resources that the user does not have rights to access. ABE can be accessed via graphical user interface (GUI), command-line executable tool, and a robust advanced programming interface (API).
Full Docutment

site reference
http://go.microsoft.com/fwlink/?linkid=5221