Search

Ads

Wednesday, May 26, 2010

Mobile Code

BenQ-Siemens Secret Codes

Software version:
*#06#
to see more info, press softkey again
English menu:
*#0001#
Deutsch menu:
*#0049#

LG Secret Codes

LG all models test mode: Type 2945#*# on the main screen.
2945*#01*# Secret menu for LG
IMEI (ALL): *#06#
IMEI and SW (LG 510): *#07#
Software version (LG B1200): *8375#
Recount cheksum (LG B1200): *6861#
Factory test (B1200): #PWR 668
Simlock menu (LG B1200): 1945#*5101#
Simlock menu (LG 510W, 5200): 2945#*5101#
Simlock menu (LG 7020, 7010): 2945#*70001#

Samsung Secret Codes

Software version: *#9999#
IMEI number: *#06#
Serial number: *#0001#
Battery status- Memory capacity : *#9998*246#
Debug screen: *#9998*324# - *#8999*324#
LCD kontrast: *#9998*523#

Motorola Secret Codes

IMEI number:
*#06#
Code to lock keys. Press together *7
Note: [] (pause) means the * key held in until box appears.
Select phone line - (use this to write things below the provider name):
[] [] [] 0 0 8 [] 1 []
Add phonebook to main menu:
[] [] [] 1 0 5 [] 1 []
Add messages to main menu:
[] […]

Sony Ericsson Secret Codes

Sony Ericsson Secret Menu: -> * <-> means press joystick, arrow keys or jogdial to the right and <- -="" 04="" 1.="" 12345="" 2.="" 3.="" 30="" 3="" 4.="" 5.="" 8810="" __________________="" a="" activation.="" adapter.="" address.="" address="" again="" allowed="" also="" and="" arrow="" ask="" automatically="" available="" battery="" be="" because="" below:="" better="" bluetooth="" by="" c="" call="" caller="" can="" change="" checking="" clear="" clock="" closed="" code.="" code="" codec="" codes="" configuration="" contents="" cool="" customer="" data="" date="" deactivation.="" default="" delete="" device="" devices="" display="" displays="" drain="" enhanced="" equipment="" erased.="" factory="" faster="" find="" flash="" for="" forgot="" found="" from="" full="" general="" get="" gprs="" group="" half="" hardware="" have="" help="" identity="" if="" imei="" in="" increase="" info="" information="" insert="" is:="" is="" it="" keys="" kinda="" labels.="" last="" lcd="" left.="" less="" life="" like="" ll="" lock="" logo="" mac="" main="" manufacture="" may="" means="" menu="" message="" mobile="" model="" month="" more="" n80="" network.="" newer="" nokia="" not="" note="" nternational="" number.="" number="" of="" on="" only="" operator="" or="" out="" passes="" phone="" phones="" pin="" press="" provider:="" purchased="" pw="" rate="" real="" receives="" reception.="" repair="" reset:="" reset="" resets="" responding="" restart.="" restart="" restrictions.="" s60="" say="" screen="" seconds="" secret="" secrets="" security="" see="" serial="" service="" services="" settings.="" settings="" should="" shows="" signal="" sim="" since="" slow.="" software="" some="" spelling="" start="" status.="" status="" strength="" supports="" takes="" test="" text="" that="" the="" then="" there="" this="" though.="" time="" timer="" to="" too="" total="" turn="" type="" u="" unlock="" up="" use="" version.="" version="" view="" vol="" wallet.="" wallet="" want="" was="" where="" will="" wlan="" word="" year="" you="" your="">security settings>user groups) to 00000 and ure phone will sound the message tone when you are near a radar speed trap. Setting it to 500 will cause your phone 2 set off security alarms at shop exits, gr8 for practical jokes! (works with some of the Nokia phones.)

Press and hold "0″ on the main screen to open wap browser.

Mobile Code Series No 2

More Benq stuff

*12022243121 is code for old Siemens model, like C35, M35 , S35 etc.
That code not working with BenQ-Siemens model.
Also you can change language in Siemens and BenQ-Siemens to any language( if you have that language support in mobile phone, of course) if you put between *# and # your country code with zeros before country code (zeros and counry code must have together four digits).
When you use code for language that not support language in mobile phones turn to automatic.
Examples:
*#0033# french
*#0385# croatian
*#0030# greek
*#0039# italien etc.

Here's a couple of extras for you - apologies for any reposts

Alcatel

IMEI number: * # 0 6 #
Software version: * # 0 6 #
Net Monitor: 0 0 0 0 0 0 *

Bosch

IMEI number: * # 0 6 #
Default Language: * # 0 0 0 0 #
Net Monitor: * # 3 2 6 2 2 5 5 * 8 3 7 8 # #

Dancall

IMEI number: * # 0 6 #
Software version: * # 9 9 9 9 #
SIM card serial number: * # 9 9 9 4 #
Information about battery status: * # 9 9 9 0 #
Selftest (only Dancall HP2731): * # 9 9 9 7 #
Show version configuration: * # 9 9 9 8 #
Net Monitor: * # 9 9 9 3 #

Sony Ericsson

IMEI number: * # 0 6 #
Software version: > * < < * < *
Default Language: <>
Enter to phone menu without SimCard - after Wrong PIN: press NO: * * 0 4 * 0 0 0 0 * 0 0 0 0 * 0 0 0 0 #
Information about SIMLOCK: < * * <

Motorola

IMEI number: * # 0 6 #
Net Monitor ON: * * * 1 1 3 * 1 * [OK]
Net Monitor OFF: * * * 1 1 3 * 1 * [OK] * - press this until box shown up

Nokia

IMEI number
: * # 0 6 #
Software version: * # 0 0 0 0 #
Lub * # 9 9 9 9 #
Simlock info: * # 9 2 7 0 2 6 8 9 #
Enhanced Full Rate: * 3 3 7 0 # [ # 3 3 7 0 # off]
Half Rate: * 4 7 2 0 #
Provider lock status: # p w + 1 2 3 4 5 6 7 8 9 0 + 1
Network lock status: # p w + 1 2 3 4 5 6 7 8 9 0 + 2
Provider lock status: # p w + 1 2 3 4 5 6 7 8 9 0 + 3
SimCard lock status: # p w + 1 2 3 4 5 6 7 8 9 0 + 4 1234567890 -
MasterCode which is generated from IMEI *#92702689# [*#war0anty#] Warranty code.

Philips

IMEI number: * # 0 6 #
Simlock info: * # 8 3 7 7 #
Security code: * # 1 2 3 4 # (Fizz) or * # 7 4 8 9 #

Samsung (Most models)

IMEI number: * # 0 6 #
Software version: * # 9 9 9 9 #
Albo* # 0 8 3 7 #
Net Monitor: * # 0 3 2 4 #
Changing LCD contrast: * # 0 5 2 3 #
Memory info: * # 0 3 7 7 #
Albo * # 0 2 4 6 #
Reset CUSTOM memory: * 2 7 6 7 * 2 8 7 8 #
Battery state: * # 9 9 9 8 * 2 2 8 #
Alarm beeper: * # 9 9 9 8 * 2 8 9 #
Vibra test: * # 9 9 9 8 * 8 4 2 #

Samsung (T100 Specific Codes)

Battery status (capacity, voltage, temperature): * # 8 9 9 9 * 2 2 8 #
Program status: * # 8 9 9 9 * 2 4 6 #
Change Alarm Buzzer Frequency: * # 8 9 9 9 * 2 8 9 #
Debug screens: * # 8 9 9 9 * 3 2 4 #
Watchdog: * # 8 9 9 9 * 3 6 4 #
EEPROM Error Stack: * # 8 9 9 9 * 3 7 7 #
Trace Watchdog: * # 8 9 9 9 * 4 2 7 #
Change LCD contrast: * # 8 9 9 9 * 5 2 3 #
Jig detect: * # 8 9 9 9 * 5 4 4 #
Memory status: * # 8 9 9 9 * 6 3 6 #
SIM File Size: * # 8 9 9 9 * 7 4 6 #
SIM Service Table: * # 8 9 9 9 * 7 7 8 #
RTK (Run Time Kernel) errors: * # 8 9 9 9 * 7 8 5 #
Run, Last UP, Last DOWN: * # 8 9 9 9 * 7 8 6 #
Software Version: * # 8 9 9 9 * 8 3 7 #
Test Vibrator: * # 8 9 9 9 * 8 4 2 #
Vocoder Reg: * # 8 9 9 9 * 8 6 2 #
Diag: * # 8 9 9 9 * 8 7 2 #
Reset On Fatal Error: * # 8 9 9 9 * 9 4 7 #
Last/Chk: * # 8 9 9 9 * 9 9 9 #9 9 * 9 9 9 #

Sagem

IMEI number: * # 0 6 #
Service Menu access: MENU 5 1 1 #

Siemens

IMEI number: * # 0 6 #
Software version: Take out SIM & enter: * # 0 6 # (& press LONG KEY)
Bonus screen: in phone book: + 1 2 0 2 2 2 4 3 1 2 1
Net Monitor (S4 Power):
Menu 9 8, left SoftKey, 7 6 8 4 6 6 6, Read phone, Menu 5 6

Sony

IMEI number: * # 0 6 #
Software version: * # 8 3 7 7 4 6 6 #
Show list of product creator names: + 1 2 0 2 2 2 4 3 1 2 1

SonyEricsson

IMEI number: * # 0 6 #
Software version: > * < < * < *
Default Language: <>
Enter to phone menu without SimCard - after Wrong PIN: press NO: * * 0 4 * 0 0 0 0 * 0 0 0 0 * 0 0 0 0 #
Information about SIMLOCK: < * * <

Code Description
*#06# Display the IMEI (GSM standard)
*#0000# Display the firmware version and date
*#bta0# Display the Bluetooth MAC address (models with build-in Bluetooth radio, activate first to show address)
*#mac0wlan# Display the WLAN MAC address (models with build-in Wi-fi radio)
*#opr0logo# Clear the operator logo (3310 and 3330 only)
*#pca0# Activate the GPRS PCCCH support (early GPRS models)
*#pcd0# Deactivate the GPRS PCCCH support (early GPRS models)
*#res0wallet# Reset the mobile wallet (models with mobile wallet)
*#res0# Soft-format the memory (Symbian models only)
*#rst0# Reset to factory defaults, confirmation required (DCT4 or newer)
*#sim0clock# Display the SIM clock status (DCT3 only)
*#ssn0# Display the manufacturing serial number (mid-range and premium, non-Symbian models, and those devired from them)
*#war0anty# Display the manufacturing and repair info (no exit on DCT3)
*efr0# Enable EFR encoding (pre-2003 models)
#efr0# Disable EFR encoding (pre-2003 models)
*hra0# Enable HR encoding (pre-2003 models)
#hra0# Disable HR encoding (pre-2003 models)
#pw+1234567890+n# Display the SIM lock status: (pre-2003 models)
n = 1: provider lock
n = 2: network lock
n = 3: country lock
n = 4: SIM lock
phannhatnghi is offline Add to phannhatnghi's Reputation Report Post Reply With Quote

MOBILE UNLOCK CHEAT CODE

>>>>>>>>>> MOBILE UNLOCK CHEAT CODE <<<<<<<<<<
==============================================

Nokia

Code:

*#06# IMEI (International Mobile Equipment Identity) information
*#0000# 1st Line: software version. 2nd line: date of software release. 3rd line: phone type
*#746025625# Checks if the SIM clock can be stopped. It is a kind of standby mode that will save battery. However,

the clock automatically gets activated when the phone is switched off and on
*#92702689# Here is a big one! A menu will come up with six choices. First, it'll display the serial number. Second,

the month and year of manufacture. Third, the date of purchase. Fourth, the last repair date. Fifth, the option to

transfer user data if you have the hardware for it. Sixth, the number of hours the phone has been on. Some of these

dates might not be displayed if the information doesn't exist
*3370# Enhanced Full Rate (EFR) codec activation
#3370# EFR codec deactivation
*4370# Half Rate codec activation
#4730# Half Rate codec deactivation

EFR gives better voice quality compared to the half rate codec, but can cut down on the battery life. Your phone

will automatically restart after you feed in any of the above codecs

xx# Here is a harmless little one. This will automatically display the number at the `xx' position in your phone book

Motorola

Code:

*#06# Displays IMEI
[][][] 119 [] 1 [] OK Enable EFR
[][][] 119 [] 0 [] OK Disable EFR

Samsung SGH-2100/600

Code:

*#06# Displays IMEI
*#9999# Software version
*#0324# Technical menu
*#0523# Lets you adjust the screen contrast
*#0228# Battery status (capacity, voltage, temperature

Sharp Secret Codes

*01763*8371# (*01763*VER0#) — Firmware Version.
*01763*3641# (*01763*ENG1#) — Enable Engineer Mode hold pwr key to leave then disable.
*01763*3640# (*01763*ENG0#) — Disable Engineer Mode.
*01763*8781# (*01763*TST1#) — Test #1 (test early wdt looping to dump, need to remove battery from phone)
*01763*8782# (*01763*TST2#) — Test #2 (test irq dis looping to switch, resets itself)

Tuesday, May 25, 2010

Step By Step Email Server Setup in Windows Server 2003

Step By Step Email Server Setup in Windows Server 2003


Start->Programs->Administrative Tools->Manage Your Server once it opens you should see similar to the following screen here Click on Add or remove a role

1

This will start the Configure Your Server Wizard. Read the text and make sure you have connected all the necessary cables and all the other things it says you should do before continuing.Click on Next

2

We now come to the step where we add and remove roles for our server. Select Mail Server (POP3,SMTP) click Next

3

You will now specify the type of authentication and type the email domain name. In this tutorial we will use Windows Authentication, and we will use our domain name, windowsreference. com. You should of course use your domain name.click next

4

Next step shows summary of our selection click on next

5

Mail server is in progress

6

When you get prompted to insert your Windows Server 2003 CD-ROM into your CD-ROM drive, do so and click ok. If you didn’t get prompted to do that, you maybe already have it in the drive.

7

Copying files in progress

8

After completing installation you should see similar to the following screen click Finish

9

Configuring Email Server

Click Start—>run type server.msc click ok this will open up the POP3 Service. This is where you configure and manage the POP3 part of the mail server.Click on in the left pane and Click on Server Properties in the right pane

11

This brings up the Properties for our Mail Server.I will explain each setting as follows

12

Authentication Method

Local Windows Accounts

If your server is stand alone (not member of an Active Directory domain), and you want to have the user accounts on the same local computer as the POP3 service, this is the best option. By using this option, you will use the SAM (Security Accounts Manager) for both the email user accounts, and the user accounts on the local computer. This means that a user can use the same user name and password to be authenticated for both the POP3 service and Windows on the local computer. But there is a limitation, although you can host multiple domains on the server, there must be unique user names for all domains. So, let us say you have two users named Sandra. One working at company1.com and another one working at company2.com. Their user name used will be sachin@company1. com and sachin@company2. com. But in SAM, they will both have the same user name, sandra, so one of them must be renamed to something else (if we don’t want them to read each other’s emails).

If you create the user account when you create the mail box (by using the POP3 interface), the user will be added to the POP3 user group. Members of this group are not allowed to logon locally. The fact that the users are added to the POP3 group does not mean that you must be a member of this group to have a mailbox. You should however be careful adding mailboxes to users that are not member of the POP3 group, because the password used for email can for example be sniffed (if you are not using SPA), or someone can brute force the password and gain access to the server.

Server Port

We strongly recommend that you use port 110 because this is the standard port for the POP3 protocol. If you change this, make sure you notify all users so they can configure their email clients to use this other port. Also make sure you restart the POP3 service if you change this.

Logging Level

Four options to choose between. If you change this, remember that you must restart the POP3 service.

None – Nothing is logged.

Low – Only critical events are logged.

Medium – Both critical and warning events are logged.

High – Critical, warning and informational events are logged.

Root Mail Directory

If you don’t want to use the default Mail Directory, you can choose another one. Make sure the path is not more than 260 characters and you can also not store to the root of a partition (i.e. C:). It is strongly recommended that you use a NTFS formatted partition. You can’t use a mapped drive, but the UNC name (\\servername\ share) can be used. If you later change the store, and there are still emails in one or more boxes, you must manually move the folders in which there are emails to the new location. You must also reset the permissions on the directory by using winpop set mailroot.

SPA

Enable SPA if you want to have a secure communication between your email sever and email clients. This will send both the user name and password encrypted from the client to the server, instead of sending it in clear text. SPA supports only Local Windows Accounts and Active Directory Integrated Authentication. It is recommended to use this. Remember to restart the POP3 service if you change this.

Create a mailbox

The Setup Wizard created a domain to us, so we do not need to create this manually. If you did not use Manage Your Server to install, add the domain manually be clicking the server name in the left pane and then click New domain in the right pane.

Remember to set the properties before you add the domain.(We have completed in the above step)

Click on your domain (windowsreference. com in my case) in the left pane.Click Add Mailbox in the right pane.

13

This will open up the Add Mailbox window here you need to enter name and password click ok

14

A message will pop-up and tell you how to configure the email clients. Read this, and notice the difference when using SPA or not. click ok

15

After creating user you should see similar to the following screen

16

What we just did was not only creating a mailbox named admin, but we also created a user admin.

Configure the SMTP Server

We have to configure the SMTP part to be able to receive and send emails. A common mistake is to think that the POP3 server receives the emails. But that is not true, all the POP3 is doing is ‘pop’ the emails out to the clients. It’s the SMTP server that is communicating with other SMTP servers and receives and sends emails.

17

Open Computer Management,Expand Services and Applications, expand Internet Information Service
Right click Default SMTP Virtual Server and click Properties

18

Once it opens properties tab you should see similar to the following screen here you need to Click the Access tab Click the Authentication button

19

Here you need to make sure Anonymous Access and Integrated Windows Authentication is enabled.

20

Click the Relay button from the properties windows and make sure Allow all computers which successfully… is enabled and Only the list below is selected.

21

First of all, Authentication and Relay is not the same thing. We use the Authentication button to specify which authentications methods are allowed for users and other SMTP servers. So enabling Anonymous here is not a security issue, in fact, it’s required if we want our server to be able to receive emails from other servers on Internet . We also need Windows Authentication so the email clients can authenticate to the server and be able to relay (send emails).

That’s it for server side now you need to configure your email clients.

If you want users to only be allowed to relay if they are on a private network, then you can uncheck Windows Authentication as allowed authentication method, and specify the IP range for your network in the Relay Restrictions window.

Enable SPA (Secure Password Authentication)

You need to configure your network network as secure as possible, so we prefer to use SPA (Secure Password Authentication) . This will, as stated before, send the user name and password from the client encrypted, instead of clear text.

Click Start, then Run ype p3server.msc

In the right pane, right click your computer’s name and click Properties

Check the box Require Secure Password Authentication… and Click OK

22

You will be prompted to restart the Microsoft POP3 Service, click Yes

23

Installing ISA Server 2004 on Windows Server 2003

Installing ISA Server 2004 on Windows Server 2003

In this ISA Server 2004 Configuration Guide document we will install the ISA Server 2004 software onto the Windows Server 2003 computer we installed and configured in Chapter 1. Installing ISA Server 2004 is straightforward as there are only a few decisions that need to be made during installation.

The most important configuration made during installation is the Internal network IP address range(s). Unlike ISA Server 2000, ISA Server 2004 does not use a Local Address Table (LAT) to define trusted and untrusted networks. Instead, the ISA Server 2004 firewall asks for the IP addresses defining a network entity known as the Internal network. The internal network contains important network servers and services such as Active Directory domain controllers, DNS, WINS, RADIUS, DHCP, firewall management stations, and others. These are services the ISA Server 2004 firewall needs to communicate with immediately after installation is complete.

Communications between the Internal network and the ISA Server 2004 firewall are controlled by the firewall’s System Policy. The System Policy is a collection of predefined Access Rules that determine the type of traffic allowed inbound and outbound to and from the firewall immediately after installation. The System Policy is configurable, which enables you can tighten or loosen the default System Policy Access Rules.

In the document we will discuss the following procedures:

  • Installing ISA Server 2004 on Windows Server 2003
  • Reviewing the Default System Policy

Installing ISA Server 2004 on Windows Server 2003 is relatively straightforward. The major decision you make during setup is what IP addresses should be part of the Internal network. The Internal network address configuration is important because the firewall’s System Policy uses the Internal network addresses to define a set of Access Rules.

Perform the following steps to install the ISA Server 2004 software on the dual-homed Windows Server 2003 machine:

  1. Insert the ISA Server 2004 CD-ROM into the CD drive. The autorun menu will appear.
  2. On the Microsoft Internet Security and Acceleration Server 2004 page, click the link for Review Release Notes and read the release notes. The release notes contain useful information about important issues and configuration options. After reading the release notes, close the release notes window and then click the Read Setup and Feature Guide link. You don’t need to read the entire guide right now, but you may want to print it out to read later. Close the Setup and Feature Guide window. Click the Install ISA Server 2004 link.
  3. Click Next on the Welcome to the Installation Wizard for Microsoft ISA Server 2004 page.
  4. Select the I accept the terms in the license agreement option on the License Agreement page. Click Next.
  5. On the Customer Information page, enter your name and the name of your organization in the User Name and Organization text boxes. Enter Product Serial Number. Click Next.
  6. On the Setup Type page, select the Custom option. If you do not want to install the ISA Server 2004 software on the C: drive, then click the Change button to change the location of the program files on the hard disk. Click Next.
    Cc302599.8db93492-b8e6-476a-8da4-cafd656403ef(en-us,TechNet.10).gif
  7. On the Custom Setup page you can choose which components to install. By default, the Firewall Services and ISA Server Management options are installed. The Message Screener, which is used to help prevent spam and file attachments from entering and leaving the network, is not installed by default; neither is the Firewall Client Installation Share. You need to install the IIS 6.0 SMTP service on the ISA Server 2004 firewall computer before you install the Message Screener. Use the default settings and click Next.
    Cc302599.017fe27f-b956-44fc-af75-15576f793999(en-us,TechNet.10).gif
  8. On the Internal Network page, click the Add button. The Internal network is different from the LAT, which was used in ISA Server 2000. In the case of ISA Server 2004, the Internal network contains trusted network services the ISA Server 2004 firewall must be able to communicate. Examples of such services include Active Directory domain controllers, DNS, DHCP, terminal services client management workstations, and others. The firewall System Policy automatically uses the Internal network. We will look at the System Policy later in this document.
    Cc302599.2979dc0c-7b5e-4c0a-b3ad-b3a93a94d6d9(en-us,TechNet.10).gif
  9. In the Internal Network setup page, click the Select Network Adapter button.
    Cc302599.20987136-e97d-429a-8a0b-8b0d52d7a7c1(en-us,TechNet.10).gif
  10. In the Select Network Adapter dialog box, remove the check mark from the Add the following private ranges… check box. Leave the check mark in the Add address ranges based on the Windows Routing Table check box. Put a check mark in the check box next to the adapter connected to the Internal network. The reason why we remove the check mark from the add private address ranges check box is that you may want to use these private address ranges for perimeter networks. Click OK.
    Cc302599.87822586-72e6-48ea-b695-ce6201858a57(en-us,TechNet.10).gif
  11. Click OK in the Setup Message dialog box informing you that the Internal network was defined, based on the Windows routing table.
  12. Click OK on the Internal network address ranges dialog box.
    Cc302599.b3eb9607-b9c5-43ba-b113-f632d24434f3(en-us,TechNet.10).gif
  13. Click Next on the Internal Network page.
    Cc302599.abb769cd-e458-4f2b-92b2-3884ffefbc07(en-us,TechNet.10).gif
  14. On the Firewall Client Connection Settings page, place checkmarks in the Allow non-encrypted Firewall client connections and Allow Firewall clients running earlier versions of the Firewall client software to connect to ISA Server check boxes. These settings will allow you to connect to the ISA Server 2004 firewall using downlevel operating systems and from Windows 2000/Windows XP/Windows Server 2003 operating systems running the ISA Server 2000 version of the Firewall client. Click Next.
    Cc302599.0d888553-7b46-4023-9955-6b481d72753e(en-us,TechNet.10).gif
  15. On the Services page, click Next.
  16. Click Install on the Ready to Install the Program page.
  17. On the Installation Wizard Completed page, click Finish.
    Cc302599.d2a416e0-ccd5-4338-9c3d-0f04fc069147(en-us,TechNet.10).gif
  18. Click Yes in the Microsoft ISA Server dialog box informing you that the machine must be restarted.
  19. Log on as Administrator after the machine restarts

By default, ISA Server 2004 does not allow outbound access to the Internet from any protected network and it does not allow Internet hosts access the firewall or any networks protected by the firewall. However, a default firewall System Policy is installed that allows network management tasks to be completed.

Cc302599.note(en-us,TechNet.10).gifNote:
A protected network is any network defined by the ISA Server 2004 firewall that is not part of the default External network.

Perform the following steps to see the default firewall System Policy:

  1. Click Start and point to All Programs. Point to Microsoft ISA Server and click ISA Server Management.
  2. In the Microsoft Internet Security and Acceleration Server 2004 management console, expand the server node in the scope pane (left pane) and click the Firewall Policy node. Right-click the Firewall Policy node, point to View and click Show System Policy Rules.
    Cc302599.7410217a-a357-4b9c-bc32-dc49fb17860a(en-us,TechNet.10).gif
  3. Click the Show/Hide Console Tree button and then click the Open/Close Task Pane arrow (the little blue arrow on the left edge of the task pane on the right side of the console). Notice that the ISA Server 2004 Access Policy represents an ordered list. Policies are processed from top to bottom, which is a significant departure from how ISA Server 2000 processed Access Policy. The System Policy represents a default list of rules controlling access to and from the ISA Server 2004 firewall by default. Note that the System Policy Rules are ordered above any custom Access Policies you will create, and therefore are processed before them. Scroll down the list of System Policy Rules. Notice that the rules are defined by:
    Order number
    Name
    Action (Allow or Deny)
    Protocols
    From (source network or host)
    To (destination network or host)
    Condition (who or what the rule applies to)
    You may want to widen the Name column to get a quick view rule the rule descriptions. Notice that not all the rules are enabled. Disabled System Policy Rules have a tiny down-pointing red arrow in their lower right corner. Many of the disabled System Policy Rules will become automatically enabled when you make configuration changes to the ISA Server 2004 firewall, such as when you enable VPN access.
    Notice that one of the System Policy Rules allows the firewall to perform DNS queries to DNS servers on all networks.
    Cc302599.057ef17f-d82a-405d-881a-04451e0dba3a(en-us,TechNet.10).gif
  4. You can change the settings on a System Policy Rule by double-clicking the rule.
    Cc302599.e602bc83-041a-4129-84ba-388b80016246(en-us,TechNet.10).gif
  5. Review the System Policy Rules and then hide the rules by clicking the Show/Hide System Policy Rules button in the console’s button bar. This is the pressed (pushed in) button seen in the following figure.
    Cc302599.997c86c2-3cce-4796-b8d0-add77af9cbb9(en-us,TechNet.10).gif

The following table includes a complete list of the default, built-in System Policy:

Table 1: System Policy Rules

Order Name Action Protocols From To Condition

1

Allow access to directory services for authentication purposes

Allow

LDAP

LDAP(GC)

LDAP(UDP)

LDAPS

LDAPS(GC)

Local Host

Internal

All Users

2

Allow Remote Management using MMC

Allow

Microsoft Firewall Control

RPC(all interfaces)

NetBIOS Datagram

NetBIOS Name Service

NetBIOS Session

Remote Management Computers

Local Host

All Users

3

Allow Remote Management using Terminal Server

Allow

RDP(Terminal Services)

Remote Management Computers

Local Host

All Users

4

Allow remote logging to trusted servers using NetBIOS

Allow

NetBIOS Datagram

NetBIOS Name Service

NetBIOS Session

Local Host

Internal

All Users

5

Allow RADIUS authentication from ISA Server to trusted RADIUS servers

Allow

RADIUS

RADIUS Accounting

Local Host

Internal

All Users

6

Allow Kerberos authentication from ISA Server to trusted servers

Allow

Kerberos-Sec( TCP)

Kerberos-Sec( UDP)

Local Host

Internal

All Users

7

Allow DNS from ISA Server to selected servers

Allow

DNS

Local Host

All Networks

All Users

8

Allow DHCP requests from ISA Server to all networks

Allow

DHCP(request)

Local Host

Anywhere

All Users

9

Allow DHCP replies from DHCP servers to ISA Server

Allow

DHCP(reply)

Anywhere

Local Host

All Users

10

Allow ICMP (PING) requests from selected computers to ISA Server

Allow

Ping

Remote Management Computers

Local Host

All Users

11

Allow ICMP requests from ISA Server to selected servers

Allow

ICMP Information Request

ICMP Timestamp

Ping

Local Host

All Networks

All Users

121

Allow VPN client traffic to ISA Server

Allow

PPTP

External

Local Host

All Users

132

Allow VPN site-to-site to ISA Server

Allow

External

IPSec Remote Gateways

Local Host

All Users

142

Allow VPN site-to-site from ISA Server

Allow

Local Host

External

IPSec Remote Gateways

All Users

15

Allow Microsoft CIFS protocol from ISA Server to trusted servers

Allow

Microsoft CIFS(TCP)

Microsoft CIFS(UDP)

Local Host

Internal

All Users

167

Allow Remote logging using Microsoft SQL protocol from firewall to trusted servers

Allow

Microsoft SQL(TCP)

Microsoft SQL(UDP)

Local Host

Internal

All Users

17

Allow HTTP/HTTPS requests from ISA Server to specified sites

Allow

HTTP

HTTPS

Local Host

System Policy Allowed Sites

All Users

183

Allow HTTP/HTTPS requests from ISA Server to selected servers for HTTP connectivity verifiers

Allow

HTTP

HTTPS

Local Host

All Networks

All Users

198

Allow access from trusted computers to the Firewall Client installation share on ISA Server

Allow

Microsoft CIFS(TCP)

Microsoft CIFS(UDP)

NetBIOS Datagram

NetBIOS Name Service

NetBIOS Session

Internal

Local Host

All Users

209

Allow remote performance monitoring of ISA Server from trusted servers

Allow

NetBIOS Datagram

NetBIOS Name Service

NetBIOS Session

Remote Management Computers

Local Host

All Users

21

Allow NetBIOS from ISA Server to trusted servers

Allow

NetBIOS Datagram

NetBIOS Name Service

NetBIOS Session

Local Host

Internal

All Users

22

Allow RPC from ISA Server to trusted servers

Allow

RPC(all interfaces)

Local Host

Internal

All Users

23

Allow HTTP/HTTPS from ISA Server to specified Microsoft Error Reporting sites

Allow

HTTP

HTTPS

Local Host

Microsoft Error Reporting sites

All Users

244

Allow SecurID protocol from ISA Server to trusted servers

Allow

SecurID

Local Host

Internal

All Users

255

Allow remote monitoring from ISA Server to trusted servers, using Microsoft Operations Manager (MOM) Agent

Allow

Microsoft Operations Manager Agent

Local Host

Internal

All Users

266

Allow HTTP from ISA Server to all networks for CRL downloads

Allow

HTTP

Local Host

All Networks

All Users

27

Allow NTP from ISA Server to trusted NTP servers

Allow

NTP(UDP)

Local Host

Internal

All Users

28

Allow SMTP from ISA Server to trusted servers

Allow

SMTP

Local Host

Internal

All Users

29

Allow HTTP from ISA Server to selected computers for Content Download Jobs

Allow

HTTP

Local Host

All Networks

System and Network Service

1 This policy is disabled until the VPN Server component is activated

2 These two policies are disabled until a site to site VPN connection is configured

3 This policy is disabled until a connectivity verifier that uses HTTP/HTTPS is configured

4 This policy is disabled until the SecureID filter is enabled

5 This policy must be manually enabled

6 This policy is disabled by default

7 This policy is disabled by default

8 This policy is automatically enabled when the Firewall client share is installed

9 This policy is disabled by default

At this point, the ISA Server 2004 firewall is ready to be configured to allow inbound and outbound access through the firewall. However, before you start creating Access Policies, you should back up the default configuration. This allows you to restore the ISA Server 2004 firewall to its post-installation state. This is useful for future troubleshooting and testing.

Perform the following steps to back up the post installation configuration:

  1. Open the Microsoft Internet Security and Acceleration Server 2004 management console and right-click the server name in the left pane of the console. Click the Back Up command.
  2. In the Backup Configuration dialog box, enter a name for the backup file in the File name text box. Be sure to note where you are saving the file by checking the entry in the Save in drop-down list. In this example we will call the backup file backup1. Click the Backup button.
    Cc302599.61a0d71c-8928-4357-a89b-7781e16be2c4(en-us,TechNet.10).gif
  3. In the Set Password dialog box, enter a password and confirm the password in the Password and Confirm password text boxes. The information in the backup file is encrypted because it can potentially contain passwords and other confidential information that you do not want others to access. Click OK.
    Cc302599.57e4f0ce-839f-4289-bb17-1a0b6ec531b9(en-us,TechNet.10).gif
  4. Click OK in the Exporting dialog box when you see the The configuration was successfully backed up message.

Make sure to copy the backup file to another location on the network after the backup is complete. The backup file should be stored offline on media that supported NTFS formatting so that you can encrypt the file

In this ISA Server 2004 Configuration Guide document we discussed the procedures required to install the ISA Server 2004 software on a Windows Server 2003 computer. We also examined the firewall System Policy that is created during installation. Finally, we finished up with step by step procedures required to back up the post-installation firewall configuration. In the next document in this ISA Server 2004 Configuration Guide series, we will enable the VPN remote access server.

Monday, May 17, 2010

How to Break a BIOS Password

How to Break a BIOS Password ?


Methods of breaking password for Desktop PC and for laptop is quite different. We would explain each.

Break BIOS Password for Desktop :
If it's a desktop PC, erasing the cmos memory will usually clear it.

Steps:

1. Power off the computer and make sure that it is unplugged.
2. Open up your computer case. You need physical access to the motherboard to complete this procedure.
3. Find a circular, (mostly) silver metallic object on the motherboard. This is the CMOS battery.
4. CAREFULLY remove the CMOS battery and leave it out for about 120- 180 seconds. This will flush the CMOS memory which stores the BIOS password and all other configuration. (See Warnings)
5. Set the battery back into place and power on the computer.
6. The computer should then warn you that the CMOS configuration could not be found. You can either reconfigure it yourself or restore defaults. Restoring the default configuration should be fine.
7. You will notice that the BIOS password has been cleared and you can boot without it. You may reset the BIOS password to something else by going into the BIOS configuration and setting a new User Password.

Alternate Methos: (More Dificult)

Remove a jumper: There's a jumper on your motherboard that you'll need to identify and remove. Most motherboards make your job easier by actually labeling the correct jumper as "BIOS config" or something similar. (it looks like a small plastic thingy on 2 pins with 1 pin beside it, within a 1" of the battery). If you're having trouble looking for it, look in the motherboard manual.After you have found it, carefuly pull straight up on it, and place it on the 2-3 pins(it was on the 1-2 pins). With the battery removed and the jumper moved, turn the computer on, and check to see if you can get into the bios. If you are able to, turn the computer off, put the jumper back on pins 1-2, and put the battery back in. Lastly put the case together and you are done.

Note: Don't forget to configure the BIOS (if you know how) after this process. If you you don't know how, just hold the "delete" button when starting your PC and when the blue screen appears, find the load safe defaults settings and press:

* ENTER button
* Y button
* F10 button

Break BIOS Password for Laptop :

Remember that laptops can be trickier, especially if it's a newer model. If it has a security chip on the motherboard forget about it. You either have to physically remove the chip or contact the mfg for the "master" password. If you can boot up off of a cd or floppy try any of these methods:

1. Create a Win98SE bootable media "or anything that lets you boot into MS-DOS" and boot off of it.
2. When the A:\> prompt appears type debug and press enter.
3. You will then only see a "-".
4. Type o 70 2E "include the spaces" and press Enter.
5. Type o 71 ff "include the spaces" and press Enter.
6. Type q and press Enter.
7. Here are a list of common mfg backdoor passwords
* AWARD BIOS
AWARD SW, AWARD_SW, Award SW, AWARD PW, _award, awkward, J64, j256, j262, j332, j322, 01322222, 589589, 589721, 595595, 598598, HLT, SER, SKY_FOX, aLLy, aLLY, Condo, CONCAT, TTPTHA, aPAf, HLT, KDD, ZBAAACA, ZAAADA, ZJAAADC,
* AMI BIOS
AMI, A.M.I., AMI SW, AMI_SW, BIOS, PASSWORD, HEWITT RAND, Oder

Softwares to Break BIOS Password:

If your system boots but the BIOS password is still in place, there are several programs you can load that are designed to crack the passwords or clear them altogether. The encryption on BIOS passwords is not very complex. Following are links to a few of these free programs:

1. CmosPwd 4.8

Wednesday, April 21, 2010

How to install and configure a Virtual Private Network server in Windows Server 2003

How to install and configure a Virtual Private Network server in Windows Server 2003

This step-by-step article describes how to install virtual private networking (VPN) and how to create a new VPN connection in servers that are running Windows Server 2003.

With a virtual private network, you can connect network components through another network, such as the Internet. You can make your Windows Server 2003-based computer a remote-access server so that other users can connect to it by using VPN, and then they can log on to the network and access shared resources. VPNs do this by "tunneling" through the Internet or through another public network in a manner that provides the same security and features as a private network. Data is sent across the public network by using its routing infrastructure, but to the user, it appears as if the data is sent over a dedicated private link.



Back to the top
Overview of VPN
A virtual private network is a means of connecting to a private network (such as your office network) by way of a public network (such as the Internet). A VPN combines the virtues of a dial-up connection to a dial-up server with the ease and flexibility of an Internet connection. By using an Internet connection, you can travel worldwide and still, in most places, connect to your office with a local call to the nearest Internet-access phone number. If you have a high-speed Internet connection (such as cable or DSL) at your computer and at your office, you can communicate with your office at full Internet speed, which is much faster than any dial-up connection that uses an analog modem. This technology allows an enterprise to connect to its branch offices or to other companies over a public network while maintaining secure communications. The VPN connection across the Internet logically operates as a dedicated wide area network (WAN) link.

Virtual private networks use authenticated links to make sure that only authorized users can connect to your network. To make sure data is secure as it travels over the public network, a VPN connection uses Point-to-Point Tunneling Protocol (PPTP) or Layer Two Tunneling Protocol (L2TP) to encrypt data.

Back to the top
Components of a VPN
A VPN in servers running Windows Server 2003 is made up of a VPN server, a VPN client, a VPN connection (that portion of the connection in which the data is encrypted), and the tunnel (that portion of the connection in which the data is encapsulated) . The tunneling is completed through one of the tunneling protocols included with servers running Windows Server 2003, both of which are installed with Routing and Remote Access. The Routing and Remote Access service is installed automatically during the installation of Windows Server 2003. By default, however, the Routing and Remote Access service is turned off.
The two tunneling protocols included with Windows are:

* Point-to-Point Tunneling Protocol (PPTP): Provides data encryption using Microsoft Point-to-Point Encryption.
* Layer Two Tunneling Protocol (L2TP): Provides data encryption, authentication, and integrity using IPSec.

Your connection to the Internet must use a dedicated line such as T1, Fractional T1, or Frame Relay. The WAN adapter must be configured with the IP address and subnet mask assigned for your domain or supplied by an Internet service provider (ISP). The WAN adapter must also be configured as the default gateway of the ISP router.

NOTE: To turn on VPN, you must be logged on using an account that has administrative rights.

Back to the top
How to install and Turn on a VPN Server
To install and turn on a VPN server, follow these steps:

1. Click Start, point to Administrative Tools, and then click Routing and Remote Access.
2. Click the server icon that matches the local server name in the left pane of the console. If the icon has a red circle in the lower-left corner, the Routing and Remote Access service has not been turned on. If the icon has a green arrow pointing up in the lower-left corner, the Routing and Remote Access service has been turned on. If the Routing and Remote Access service was previously turn on, you may want to reconfigure the server. To reconfigure the server:
1. Right-click the server object, and then click Disable Routing and Remote Access. Click Yes to continue when you are prompted with an informational message.
2. Right-click the server icon, and then click Configure and Enable Routing and Remote Access to start the Routing and Remote Access Server Setup Wizard. Click Next to continue.
3. Click Remote access (dial-up or VPN) to turn on remote computers to dial in or connect to this network through the Internet. Click Next to continue.
3. Click to select VPN or Dial-up depending on the role that you intend to assign to this server.
4. In the VPN Connection window, click the network interface which is connected to the Internet, and then click Next.
5. In the IP Address Assignment window, click Automatically if a DHCP server will be used to assign addresses to remote clients, or click From a specified range of addresses if remote clients must only be given an address from a pre-defined pool. In most cases, the DHCP option is simpler to administer. However, if DHCP is not available, you must specify a range of static addresses. Click Next to continue.
6. If you clicked From a specified range of addresses, the Address Range Assignment dialog box opens. Click New. Type the first IP address in the range of addresses that you want to use in the Start IP address box. Type the last IP address in the range in the End IP address box. Windows calculates the number of addresses automatically. Click OK to return to the Address Range Assignment window. Click Next to continue.
7. Accept the default setting of No, use Routing and Remote Access to authenticate connection requests, and then click Next to continue. Click Finish to turn on the Routing and Remote Access service and to configure the server as a Remote Access server.

Back to the top
How to Configure the VPN Server
To continue to configure the VPN server as required, follow these steps.
How to Configure the Remote Access Server as a Router
For the remote access server to forward traffic properly inside your network, you must configure it as a router with either static routes or routing protocols, so that all of the locations in the intranet are reachable from the remote access server.

To configure the server as a router:

1. Click Start, point to Administrative Tools, and then click Routing and Remote Access.
2. Right-click the server name, and then click Properties.
3. Click the General tab, and then click to select Router under Enable this computer as a.
4. Click LAN and demand-dial routing, and then click OK to close the Properties dialog box.

How to Modify the Number of Simultaneous Connections
The number of dial-up modem connections is dependent on the number of modems that are installed on the server. For example, if you have only one modem installed on the server, you can have only one modem connection at a time.

The number of dial-up VPN connections is dependent on the number of simultaneous users whom you want to permit. By default, when you run the procedure described in this article, you permit 128 connections. To change the number of simultaneous connections, follow these steps:

1. Click Start, point to Administrative Tools, and then click Routing and Remote Access.
2. Double-click the server object, right-click Ports, and then click Properties.
3. In the Ports Properties dialog box, click WAN Miniport (PPTP), and then click Configure.
4. In the Maximum ports box, type the number of VPN connections that you want to permit.
5. Click OK, click OK again, and then close Routing and Remote Access.

How to Manage Addresses and Name Servers
The VPN server must have IP addresses available to assign them to the VPN server's virtual interface and to VPN clients during the IP Control Protocol (IPCP) negotiation phase of the connection process. The IP address assigned to the VPN client is assigned to the virtual interface of the VPN client.

For Windows Server 2003-based VPN servers, the IP addresses assigned to VPN clients are obtained through DHCP by default. You can also configure a static IP address pool. The VPN server must also be configured with name resolution servers, typically DNS and WINS server addresses, to assign to the VPN client during IPCP negotiation.

How to Manage Access
Configure the dial-in properties on user accounts and remote access policies to manage access for dial-up networking and VPN connections.

NOTE: By default, users are denied access to dial-up networking.

Access by User Account
To grant dial-in access to a user account if you are managing remote access on a user basis, follow these steps:

1. Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
2. Right-click the user account, and then click Properties.
3. Click the Dial-in tab.
4. Click Allow access to grant the user permission to dial in. Click OK.

Access by Group Membership
If you manage remote access on a group basis, follow these steps:

1. Create a group with members who are permitted to create VPN connections.
2. Click Start, point to Administrative Tools, and then click Routing and Remote Access.
3. In the console tree, expand Routing and Remote Access, expand the server name, and then click Remote Access Policies.
4. Right-click anywhere in the right pane, point to New, and then click Remote Access Policy.
5. Click Next, type the policy name, and then click Next.
6. Click VPN for Virtual Private Access access method, or click Dial-up for dial-up access, and then click Next.
7. Click Add, type the name of the group that you created in step 1, and then click Next.
8. Follow the on-screen instructions to complete the wizard.



If the VPN server already permits dial-up networking remote access services, do not delete the default policy. Instead, move it so that it is the last policy to be evaluated.

Back to the top
How to Configure a VPN Connection from a Client Computer
To set up a connection to a VPN, follow these steps. To set up a client for virtual private network access, follow these steps on the client workstation:

NOTE: You must be logged on as a member of the Administrators group to follow these steps.

NOTE: Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

1. On the client computer, confirm that the connection to the Internet is correctly configured.
2. Click Start, click Control Panel, and then click Network Connections. Click Create a new connection under Network Tasks, and then click Next.
3. Click Connect to the network at my workplace to create the dial-up connection. Click Next to continue.
4. Click Virtual Private Network connection, and then click Next.
5. Type a descriptive name for this connection in the Company name dialog box, and then click Next.
6. Click Do not dial the initial connection if the computer is permanently connected to the Internet. If the computer connects to the Internet through an Internet Service Provider (ISP), click Automatically dial this initial connection, and then click the name of the connection to the ISP. Click Next.
7. Type the IP address or the host name of the VPN server computer (for example, VPNServer.SampleDom ain.com).
8. Click Anyone's use if you want to permit any user who logs on to the workstation to have access to this dial-up connection. Click My use only if you want this connection to be available only to the currently logged-on user. Click Next.
9. Click Finish to save the connection.
10. Click Start, click Control Panel, and then click Network Connections.
11. Double-click the new connection.
12. Click Properties to continue to configure options for the connection. To continue to configure options for the connection, follow these steps:
* If you are connecting to a domain, click the Options tab, and then click to select the Include Windows logon domain check box to specify whether to request Windows Server 2003 logon domain information before trying to connect.
* If you want the connection to be redialed if the line is dropped, click the Options tab, and then click to select the Redial if line is dropped check box.

To use the connection, follow these steps:

1. Click Start, point to Connect to, and then click the new connection.
2. If you do not currently have a connection to the Internet, Windows offers to connect to the Internet.
3. When the connection to the Internet is made, the VPN server prompts you for your user name and password. Type your user name and password, and then click Connect.
Your network resources must be available to you in the same way they are when you connect directly to the network.NOTE: To disconnect from the VPN, right-click the connection icon, and then click Disconnect.

Back to the top
Troubleshooting
Troubleshooting Remote Access VPNs
Cannot Establish a Remote Access VPN Connection

* Cause: The name of the client computer is the same as the name of another computer on the network.

Solution: Verify that the names of all computers on the network and computers connecting to the network are using unique computer names.
* Cause: The Routing and Remote Access service is not started on the VPN server.

Solution: Verify the state of the Routing and Remote Access service on the VPN server.

See Windows Server 2003 Help and Support Center for more information about how to monitor the Routing and Remote Access service, and how to start and stop the Routing and Remote Access service. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: Remote access is not turned on on the VPN server.

Solution: Turn on remote access on the VPN server.

See the Windows Server 2003 Help and Support Center for more information about how to turn on the remote access server. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: PPTP or L2TP ports are not turned on for inbound remote access requests.

Solution: Turn on PPTP or L2TP ports, or both, for inbound remote access requests.

See the Windows Server 2003 Help and Support Center for more information about how to configure ports for remote access. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: The LAN protocols used by the VPN clients are not turned on for remote access on the VPN server.

Solution: Turn on the LAN protocols used by the VPN clients for remote access on the VPN server.

See the Windows Server 2003 Help and Support Center for more information about how to view properties of the remote access server. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: All of the PPTP or L2TP ports on the VPN server are already being used by currently connected remote access clients or demand-dial routers.

Solution: Verify that all of the PPTP or L2TP ports on the VPN server are already being used. To do so, click Ports in Routing and Remote Access. If the number of PPTP or L2TP ports permitted is not high enough, change the number of PPTP or L2TP ports to permit more concurrent connections.

See the Windows Server 2003 Help and Support Center for more information about how to add PPTP or L2TP ports. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: The VPN server does not support the tunneling protocol of the VPN client.

By default, Windows Server 2003 remote access VPN clients use the Automatic server type option, which means that they try to establish an L2TP over IPSec-based VPN connection first, and then they try to establish a PPTP-based VPN connection. If VPN clients use either the Point-to-Point Tunneling Protocol (PPTP) or Layer-2 Tunneling Protocol (L2TP) server type option, verify that the selected tunneling protocol is supported by the VPN server.

By default, a computer running Windows Server 2003 Server and the Routing and Remote Access service is a PPTP and L2TP server with five L2TP ports and five PPTP ports. To create a PPTP-only server, set the number of L2TP ports to zero. To create an L2TP-only server, set the number of PPTP ports to zero.

Solution: Verify that the appropriate number of PPTP or L2TP ports is configured.

See the Windows Server 2003 Help and Support Center for more information about how to add PPTP or L2TP ports. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: The VPN client and the VPN server in conjunction with a remote access policy are not configured to use at least one common authentication method.

Solution: Configure the VPN client and the VPN server in conjunction with a remote access policy to use at least one common authentication method.

See the Windows Server 2003 Help and Support Center for more information about how to configure authentication. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: The VPN client and the VPN server in conjunction with a remote access policy are not configured to use at least one common encryption method.

Solution: Configure the VPN client and the VPN server in conjunction with a remote access policy to use at least one common encryption method.

See the Windows Server 2003 Help and Support Center for more information about how to configure encryption. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: The VPN connection does not have the appropriate permissions through dial-in properties of the user account and remote access policies.

Solution: Verify that the VPN connection has the appropriate permissions through dial-in properties of the user account and remote access policies. For the connection to be established, the settings of the connection attempt must:
o Match all of the conditions of at least one remote access policy.
o Be granted remote access permission through the user account (set to Allow access) or through the user account (set to Control access through Remote Access Policy) and the remote access permission of the matching remote access policy (set to Grant remote access permission).
o Match all the settings of the profile.
o Match all the settings of the dial-in properties of the user account.
See the Windows Server 2003 Help and Support Center for an introduction to remote access policies, and for more information about how to accept a connection attempt. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: The settings of the remote access policy profile are in conflict with properties of the VPN server.

The properties of the remote access policy profile and the properties of the VPN server both contain settings for:
o Multilink.
o Bandwidth allocation protocol (BAP).
o Authentication protocols.
If the settings of the profile of the matching remote access policy are in conflict with the settings of the VPN server, the connection attempt is rejected. For example, if the matching remote access policy profile specifies that the Extensible Authentication Protocol - Transport Level Security (EAP-TLS) authentication protocol must be used and EAP is not enabled on the VPN server, the connection attempt is rejected.

Solution: Verify that the settings of the remote access policy profile are not in conflict with properties of the VPN server.

See the Windows Server 2003 Help and Support Center for more information about additional information about multilink, BAP and authentication protocols. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: The answering router cannot validate the credentials of the calling router (user name, password, and domain name).

Solution: Verify that the credentials of the VPN client (user name, password, and domain name) are correct and can be validated by the VPN server.
* Cause: There are not enough addresses in the static IP address pool.

Solution: If the VPN server is configured with a static IP address pool, verify that there are enough addresses in the pool. If all of the addresses in the static pool have been allocated to connected VPN clients, the VPN server cannot allocate an IP address, and the connection attempt is rejected. If all of the addresses in the static pool have been allocated, modify the pool. See the Windows Server 2003 Help and Support Center for more information about TCP/IP and remote access, and how to create a static IP address pool. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: The VPN client is configured to request its own IPX node number and the VPN server is not configured to permit IPX clients to request their own IPX node number.

Solution: Configure the VPN server to permit IPX clients to request their own IPX node number.

See the Windows Server 2003 Help and Support Center for more information about IPX and remote access. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: The VPN server is configured with a range of IPX network numbers that are being used elsewhere on your IPX network.

Solution: Configure the VPN server with a range of IPX network numbers that is unique to your IPX network.

See the Windows Server 2003 Help and Support Center for more information about IPX and remote access. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: The authentication provider of the VPN server is improperly configured.

Solution: Verify the configuration of the authentication provider. You can configure the VPN server to use either Windows Server 2003 or Remote Authentication Dial-In User Service (RADIUS) to authenticate the credentials of the VPN client.

See the Windows Server 2003 Help and Support Center for more information about authentication and accounting providers, and how to use RADIUS authentication. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: The VPN server cannot access Active Directory.


Solution: For a VPN server that is a member server in a mixed-mode or native-mode Windows Server 2003 domain that is configured for Windows Server 2003 authentication, verify that:
o The RAS and IAS Servers security group exists. If not, create the group and set the group type to Security and the group scope to Domain local.
o The RAS and IAS Servers security group has Read permission to the RAS and IAS Servers Access Check object.
o The computer account of the VPN server computer is a member of the RAS and IAS Servers security group. You can use the netsh ras show registeredserver command to view the current registration. You can use the netsh ras add registeredserver command to register the server in a specified domain.

If you add (or remove) the VPN server computer to the RAS and IAS Servers security group, the change does not take effect immediately (because of the way that Windows Server 2003 caches Active Directory information) . To immediately effect this change, restart the VPN server computer.
o The VPN server is a member of the domain.
See the Windows Server 2003 Help and Support Center for more information about how to add a group, how to verify permissions for the RAS and IAS security group, and about netsh commands for remote access. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: A Windows NT 4.0-based VPN server cannot validate connection requests.

Solution: If VPN clients are dialing in to a VPN server running Windows NT 4.0 that is a member of a Windows Server 2003 mixed-mode domain, verify that the Everyone group is added to the Pre-Windows 2000 Compatible Access group with the following command:
"net localgroup "Pre-Windows 2000 Compatible Access""
If not, type the following command at a command prompt on a domain controller computer, and then restart the domain controller computer:
net localgroup "Pre-Windows 2000 Compatible Access" everyone /add
See the Windows Server 2003 Help and Support Center for more information about Windows NT 4.0 remote access server in a Windows Server 2003 domain. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: The VPN server cannot communicate with the configured RADIUS server.

Solution: If you can reach your RADIUS server only through your Internet interface, do one of the following:
o Add an input filter and an output filter to the Internet interface for UDP port 1812 (based on RFC 2138, "Remote Authentication Dial-In User Service (RADIUS)"). –or-
o Add an input filter and an output filter to the Internet interface for UDP port 1645 (for older RADIUS servers), for RADIUS authentication and UDP port 1813 (based on RFC 2139, "RADIUS Accounting") . -or-

o -or- Add an input filter and an output filter to the Internet interface for UDP port 1646 (for older RADIUS servers) for RADIUS accounting.
See the Windows Server 2003 Help and Support Center for more information about how to add a packet filter. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: Cannot connect to the VPN server over the Internet using the Ping.exe utility.

Solution: Because of the PPTP and L2TP over IPSec packet filtering that is configured on the Internet interface of the VPN server, Internet Control Message Protocol (ICMP) packets used by the ping command are filtered out. To turn on the VPN server to respond to ICMP (ping) packets, add an input filter and an output filter that permit traffic for IP protocol 1 (ICMP traffic).

See the Windows Server 2003 Help and Support Center for more information about how to add a packet filter. Click Start to access the Windows Server 2003 Help and Support Center.

Cannot Send and Receive Data

* Cause: The appropriate demand-dial interface has not been added to the protocol being routed.

Solution: Add the appropriate demand-dial interface to the protocol being routed.

See the Windows Server 2003 Help and Support Center for more information about how to add a routing interface. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: There are no routes on both sides of the router-to-router VPN connection that support the two-way exchange of traffic.

Solution: Unlike a remote access VPN connection, a router-to-router VPN connection does not automatically create a default route. Create routes on both sides of the router-to-router VPN connection so that traffic can be routed to and from the other side of the router-to-router VPN connection.

You can manually add static routes to the routing table, or you can add static routes through routing protocols. For persistent VPN connections, you can turn on Open Shortest Path First (OSPF) or Routing Information Protocol (RIP) across the VPN connection. For on-demand VPN connections, you can automatically update routes through an auto-static RIP update. See Windows Server 2003 online Help for more information about how to add an IP routing protocol, how to add a static route, and how to perform auto-static updates. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: A two-way initiated, the answering router as a remote access connection is interpreting router-to-router VPN connection.

Solution: If the user name in the credentials of the calling router appears under Dial-In Clients in Routing and Remote Access, the answering router may interpret the calling router as a remote access client. Verify that the user name in the credentials of the calling router matches the name of a demand-dial interface on the answering router. If the incoming caller is a router, the port on which the call was received shows a status of Active and the corresponding demand-dial interface is in a Connected state.

See Windows Server 2003 online Help for more information about how to check the status of the port on the answering router, and how to check the status of the demand-dial interface. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: Packet filters on the demand-dial interfaces of the calling router and answering router are preventing the flow of traffic.

Solution: Verify that there are no packet filters on the demand-dial interfaces of the calling router and answering router that prevent the sending or receiving of traffic. You can configure each demand-dial interface with IP and IPX input and output filters to control the exact nature of TCP/IP and IPX traffic that is permitted into and out of the demand-dial interface.

See Windows Server 2003 online Help for more information about how to manage packet filters. Click Start to access the Windows Server 2003 Help and Support Center.
* Cause: Packet filters on the remote access policy profile are preventing the flow of IP traffic.

Solution: Verify that there are no configured TCP/IP packet filters on the profile properties of the remote access policies on the VPN server (or the RADIUS server if Internet Authentication Service is used) that are preventing the sending or receiving of TCP/IP traffic. You can use remote access policies to configure TCP/IP input and output packet filters that control the exact nature of TCP/IP traffic permitted on the VPN connection. Verify that the profile TCP/IP packet filters are not preventing the flow of traffic.

See Windows Server 2003 online Help for more information about how to configure IP options. Click Start to access the Windows Server 2003 Help and Support Center.