Intranet site is identified as an Internet site when you use an FQDN or an IP address

When you access a local area network (LAN), an intranet share, or an intranet Web site by using an Internet Protocol (IP) address or a fully qualified domain name (FQDN), the share or Web site may be identified as in the Internet zone instead of in the Local intranet zone. For example, this behavior may occur if you access shares or Web sites with Microsoft Internet Explorer or Windows Internet Explorer, with Microsoft Windows Explorer, with a command prompt, or with a Windows-based program when you use an address in any one of the following formats:

* \\Computer.childdomain.domain.com\Share
* http://computer.childdomain.domain.com
* \\157.54.100.101\share
* file://157.54.100.101/share
* http://157.54.100.101

This behavior can occur regardless of whether any or all of the following settings are configured:

* In Microsoft Internet Explorer or in Windows Internet Explorer, you have added the FQDN (or *.domain.com) or the IP address (or the address range) to the Do not use proxy server for addresses beginning with box under the Exceptions section in the Proxy Settings dialog box.

Note To locate the Proxy Settings dialog box in Internet Explorer, click Tools, click Internet Options, click Connections, and then click Proxy Settings.
* You have selected the Bypass proxy server for local addresses check box that is on the Local Area Network (LAN) Settings dialog box.

Note To locate the Local Area Network (LAN) Settings dialog box in Internet Explorer, click Tools, click Internet Options, click Connections, and then click Local Area Network (LAN) Settings.
* You have selected the Include all sites that bypass the proxy server and Include all network paths (UNCs) check boxes on the Local intranet dialog box.

To locate the Local intranet dialog box in Internet Explorer, click Tools, click Internet Options, click Security, and then click Local intranet.

This behavior can cause Internet Explorer to prompt you for credentials when you access the intranet Web sites that require authentication. Or you may be prompted or prevented from opening files on an intranet Web site or Universal Naming Convention (UNC) share in programs that use the Internet Explorer Security Manager to determine whether a file is located in a trusted security zone. For example, you may receive the following error message when you try to open a Microsoft Access database (.mdb) file on a local intranet share (by using the FQDN or IP address) with Microsoft Access 2002:

Reasons for System Crash

The different reasons for your system crash are described as follows:

1. Hardware conflict:
The number one reason why Windows crashes is hardware conflict. Each hardware device communicates to other devices through an interrupt request channel (IRQ). These are supposed to be unique for each device. If there are a lot of devices, or if they are not installed properly, two of them may end up sharing the same IRQ number. When the user tries to use both devices at the same time, a crash can happen.

2. Bad Ram:
Ram (random-access memory) problems might bring on the blue screen of death with a message saying Fatal Exception Error. A fatal error indicates a serioushardware problem. Sometimes it may mean a part is damaged and will need replacing.

But a fatal error caused by Ram might be caused by a mismatch of chips. For example, mixing 70-nanosecond (70ns) Ram with 60ns Ram will usually force thecomputer to run all the Ram at the slower speed. This will often crash the machine if the Ram is overworked.

3. BIOS settings:
Every motherboard is supplied with a range of chipset settings that are decided in the factory. A common way to access these settings is to press the F2 or delete button during the first few seconds of a boot-up.

Once inside the BIOS, great care should be taken. It is a good idea to write down on a piece of paper all the settings that appear on the screen. That way, if you change something and thecomputer becomes more unstable, you will know what settings to revert to.

A common BIOS error concerns the CAS latency. This refers to the Ram. Older EDO (extended data out) Ram has a CAS latency of 3. Newer SDRam has a CAS latency of 2. Setting the wrong figure can cause the Ram to lock up and freeze thecomputer’s display.

4. Hard disk drives:
After a few weeks, the information on a hard disk drive starts to become piecemeal or fragmented. It is a good idea to defragment the hard disk every week or so, to prevent the disk from causing a screen freeze. This will start the procedure. You will be unable to write data to the hard drive (to save it) while the disk is defragmenting, so it is a good idea to schedule the procedure for a period of inactivity using the Task Scheduler.

5. Fatal OE exceptions and VXD errors:
Fatal OE exception errors and VXD errors are often caused by video card problems. These can often be resolved easily by reducing the resolution of the video display. If you have video card hardware conflict, you will see it here. Be careful at this point and make a note of everything you do in case you make things worse. The way to resolve a hardware conflict is to uncheck the Use Automatic Settings box and hit the Change Settings button. You are searching for a setting that will display a No Conflicts message.

6. Viruses:
Often the first sign of a virus infection is instability. Some viruses erase the boot sector of a hard drive, making it impossible to start. This is why it is a good idea to create aWindows start-up disk. A virus scanner requires a list of virus signatures in order to be able to identify viruses. These signatures are stored in a DAT file. DAT files should be updated weekly from the website of your antivirus software manufacturer.

Remote Desktop Support

Remote Desktop is designed to allow users to remotely gain access to their Windows XP Professional desktop, applications, data, and network resources from another computer on the network. Users who have been granted permission can remotely connect.

After a connection is established, the local desktop is locked for security reasons, preventing anyone from viewing the tasks that are being performed remotely.

Remote Desktop support is designed to allow a user to have full control over his or her Windows XP Professional desktop from another computer on the network. This is useful when a user is working from home, another office, or another site and requires access to information from his or her primary office computer. While a user is remotely accessing his or her computer, local access by another user is not permitted. An exception to this is an administrator. Administrators are permitted to log on locally while another user is connected remotely, but the remote session is then terminated.

Remote Desktop requires the following:

* A remote computer that is running Microsoft Windows XP Professional and that is connected to a LAN or the Internet. This is the computer to which you want to gain access remotely.
* A client computer with access to the host computer through a LAN, dial-up, or VPN connection that has the Remote Desktop Connection program or the Terminal Services Client installed. A version of the Remote Desktop Connection program is available for most versions of Windows.
* A user account with appropriate permissions. The user must be an administrator or a member of the Remote Users group.