Archive

Archive for November 14, 2011

DIRECT RECRUITMENT FOR THE POST OF VILLAGE REVENUE OFFICERS (VRO) and VILLAGE REVENUE ASSISTANTS (VRA) THROUGH DISTRICT SELECTION COMMITTEE (DSE)

November 14, 2011 80 comments

More Latest Updates which includes VRO-VRA syllabus as well as Model Papers

 

Syllabus for VRO/VRA
Click Here Local Copy is

Model question paper for VRO
Click Here   Local Copy is

Model question paper for VRA
Click Here Local Copy is

Instructions Booklet
Click Here

 

Refer to: http://ccla.cgg.gov.in/

———————————————

Notification from Eenadu newspaper in district edition dated 7th Dec 2011.

image

image

image

 

Well, finally the notification is out today.  Refer to the below details from the official website of  GOVERNMENT OF ANDHRA PRADESH Chief Commissioner Of Land Administration (CCLA).

 

Application Submission Last Date

Written Exam Date

   

CircularNo:2(CCLA)
Dt.30/11/2011

VRO/VRA

07.12.2011

27.12.2011

29.12.2011

VRO-30.01.2012 FN (10 AM to 12 Noon)
VRA-30.01.2012 AN (3 PM to 5 PM)

Application Submission

 
 
               

CLICK HERE For VRA vacancies List

HELP DESK

For any problems in Online submission and download of hall-tickets
call Ph: +91 9246572520
(Call Time : 10.30 A.M to 1.00 P.M & 1.30 P.M to 5 P.M on working days)

Notifications download

Srikakulam

Kurnool

Vizianagaram

Mahabubnagar

Visakhapatnam

Ranga Reddy

East Godavari

Hyderabad

West Godavari

Medak

Krishna

Nizamabad

Guntur

Adilabad

Prakasam

Karimnagar

Nellore

Warangal

Chittoor

Khammam

Cuddapah

Nalgonda

Anantapur

 

APOnline Centres List

CLICK HERE

ESeva Centres List

ClickHere

   
   

 

Update on 29th November 2011:

 

AP VRO & VRA Recruitment Notification Release Date: 07.12.2011

Written Test: 30.01.2012

 

For Detailed text in Telugu refer to the below article from todays Eenadu news paper

 

Source: VRO VRA Recruitment Notification on 7th December

Update on 15th November 2011:

Andhra Pradesh Village Revenue Officer (VRO) & Village Revenue Assistant (VRA) Recruitment 2011

Government of Andhra Pradesh going to release the Notification on 30.11.2011 for the recruitment to the posts of Village Revenue Officers (VRO – 1172 Posts)& Village Revenue Assistant (VRA – 6063 Posts) in Andhra Pradesh. AP VRO & VRA recruitment written exam 2011 will be conducted by APPSC/ JNTU.

Selection Process: Andhra Pradesh VRO & VRA selection Procedure is based on Marks obtained in Written Test. The Written Test Paper is Objective type & Consists of 100 Marks. There will be No Interview after Written Test for the recruitment of AP VRO & VRA. Reservation is applicable as per the rules.

Andhra Pradesh AP Village Revenue Officer (VRO) Recruitment 2011

No. of Posts: 1172

Age Limit: 34 years

Educational Qualification: Intermediate

Andhra Pradesh AP Village Revenue Assistant (VRA) Recruitment 2011

No. of Posts: 6063

Age Limit: 34 years

Educational Qualification: 10TH Class/ SSC

Eligibility: Local village Candidates only eligible to apply for Village Revenue Assistants (VRA).

Important Dates:

AP VRO & VRA Recruitment Notification Release Date: 30.11.2011

Submission of Applications: 31.12.2011 onwards

Issue of Call Letters for AP VRO & VRA Written Test –

AP VRO & VRA Recruitment Results Date -

Click here for AP Village Revenue Officers (VRO) & Village Revenue Assistants (VRA) Recruitment

Source: Andhra Pradesh (AP) VRO & VRA Recruitment 2011| Selection Procedure

Update on 14th November 2011: The Government of Andhra Pradesh has announced notification details for the recruitment of VROs and VRAs in Andhra Pradesh. The Cabinet Sub-Committee headed by N.Raghuveera Reddy has announced the notification details. Selection will be based on the interviews to conducted by District Selection Committees (DSCs) headed by the respective District Collector. There is no entrance test or written test for VRO and VRA vacancies. Reservations will be followed as per the rules. Weightage of 85 marks will be allotted for marks in the qualifying exam, reservation, local status and other standards. Remaining 15 marks will be for performance in interviews. Following are the important dates for the recruitment:
1) VRO (Village Revenue Officers): 1175 posts; Pay Scale : Rs. 7740 – 23040. Eligibility is pass in Intermediate in any group. Those selected for VRO posts can reside in any area of the concerned district. Selection will be through Interviews which contains questions on general knowledge.
2) VRA (Village Revenue Assistants) : 6063 posts; Eligibility: Applicants should have passed in 10th Class / SSC. Local candidates only can apply for the concerned villages. Selection will be throuhg performance in interviews to be conducted by DSC chaired by respective District Collctors.
Important Dates:
1) Release of Notification: 26th November 2011
2) Start of Sale of Applications: 26th November 2011
3) Last date for the submission of filled in applications: 17th December 2011
4) Schedule of Interviews: January 2012
5) Completion of recruitment and posting: 31st January 2012.

Following are details of some of the upcoming recruitment notifications to be released by the UPSC and State Governments during 2011- 2012. Details such as eligibility, application procedure, Examination pattern etc will be provided after the release of respective notifications. The Government of Andhra Pradesh is gearing up for massive recruitments in various departments. The Government is gearing up to fill about 1,16,000 vacancies in Education, Police, Health, Excise, Revenue and Engineering Departments. Here are latest updates of these recruitments:
Village Revenue Assistant (VRA) recruitment: The Govt. of Andhra Pradesh will fill up 6063 Village Revenur Assistants posts very soon. Details of posts, district wise vacancies, eligibility and selection procedure are also available for these posts. Scroll down below for latest update on 2nd August 2011.
Village Revenue Officers (VRO) : The Government of AP is likely to recruit 1564 Village Revenue Officers (VROs) in the pay scale of Rs. 7740 – 23040. Eligibility is pass in 10th Class. Selection will be through written examination which contains questions on general knowledge. Update is available at the end of this post.
Degree College Lecturers on Contract Basis: Collegiate Education, Govt. of Andhra Pradesh has issued orders to renew the appointment / recruitment of Contract Lecturers in Degree Colleges in the state of Andhra Pradesh. The Depart of Higher Education will recruit 1766 posts on contract basis through this orders. New candidates will be recruited for the new vacancies.
Posts in BC Welfare Department: The Government of Andhra Pradesh has sanctioned 154 additions posts to supervise the activities of various post metric scholarships for BC students in the state. Vacancies are available in the levels of director, district and field workers. Details of new posts are Additional Director – 1 post; Joint Directors – 3 posts; Deputy Directors – 11 posts; Assistant BC Welfate Officers – 35 posts; Superintendents – 26 posts; Senior Assistants – 29 posts and Junior Assistants – 49 posts. Notification for the recruitment of these posts will be released soon.
1. Hostel Welfare Officers Grade 2: The Govt. of Andhra Pradesh will release notification to fill up 300 posts of Hostel Welfare Officers in BC Social Welfare Hostels located in the state of Andhra Pradesh. Eligibility for these posts is Graduation along with B.Ed. Selection will be through Written Examination. Pay Scale for these jobs in Rs. 10900 – 31550.
2. Village Revenue Officers (VRO) : The Government of AP is likely to recruit 1564 Village Revenue Officers (VROs) in the pay scale of Rs. 7740 – 23040. Eligibility is pass in 10th Class. Selection will be through written examination which contains questions on general knowledge.
3. Police Constables (PC): AP State Police Recruitment Board is proposed to recruit 15000 police constables for the requirements in Ministry of Home Affairs, Govt. of AP. Intermediate qualified candidates are eligible for these jobs. Selection will be based on physical test, written test and medical examination. Pay Scale for Police Constables is Rs. 8440 – 24950.
4. Vacancies in Village Panchayat Services: The government is contemplating to recruit 40000 candidates for various vacancies available in Andhra Pradesh Village Panchayat Services. Vacancies are available in the positions of Panchayat Development Officers, Junior Engineers, Accountants cum Data Entry Operators, Assistant Extension Officers etc. It is estimated that there are 250 vacancies in the Extension Officers posts. Eligibility: Graduation / Intermediate / SSC.
5. Excise Constables: The Govt. of AP will be recruiting Excise Constables after a long time. There will be about 1500 posts for which notification is likely to be announced very soon. Tenth Class passed candidates are eligible for these jobs. Selection will be through Physical Test and Written Examination.
6. Junior Assistants and Computer Operators: There are about 1000 vacancies of Junior Assistants, Typist cum Computer Operators in the Department of Revenue, Govt. of AP, for which notification is yet to be released. Qualification for these posts is pass in Intermediate / 10th class.
7. Municipal Jobs: About 4500 posts are lying vacant in Municipalities in the state of Andhra Pradesh. These posts will be filled very soon as the Govt. has to release schedule of elections for Municipalities. Vacancies are available in the positions of Assistant Executive Engineers, Accountants, Junior Assistants etc. Eligibility is Engineering Degree / Commerce Graduates / Pass in 10th Class (Based on the post).
8. UPSC Central Police Forces (AC) Examination 2011: UPSC will release this notification on 18th June 2011 and exam will be conducted on 9th October 2011. The Official notification has come out and details are available in another post .
9. UPSC Civil Services Main Examination 2011: This will be conducted from 29th October 2011.
10. UPSC – IES / ISS Examination 2011: Notification will be released on 30th July 2011. Last date for the receipt of applications is 29th August 2011 and exam will be held on 3rd December 2011.
11. UPSC Geologists Examination 2011: Notification will come out on 13th August 2011 and applications will be received till 19th September 2011. Examination will be conducted on 3rd December 2011.
Update on 12th November 2011: The Govt. of AP has finalised the educational qualifications required for VRO and VRA posts as prescribed by Cabinet Sub-Committee. For VRO jobs, candidates should have qualified in Intermediate. Pass in 10th class / SSC is the minimum qualification / eligibility for VRA posts. Mandal will be taken as a criteria for the selection of candidates. Gazette notification will be releasled on 15th Novemner 2011 with all these details and recruitment notification may be announced in due course of time. The Governmet is yet to take decision on conducting interviews for these posts.

12. Latest Update on VRO and VRA Recruitment (2nd August 2011):

The Government of Andhra Pradesh has formed a sub- committee with a group of ministers under the chairmanship of N. Raghuveera Reddy to oversee the recruitment process of Village Revenue Officers and Village Revenue Assistants. The sub committee has decided to complete the recruitment process for all the 9000 vacant posts by the end of August 2011. They have also recommended Collectors and RDOs of all the districts in the state to speed up the recruitment process.
The sub committee has disclosed that the education qualification for the VRO posts will be pass in Intermediate Examination and the qualification for VRA posts will be SSC / Tenth Class. There will be no written examination for any posts. Selection of the candiddtes will be based on marks in the qualifying examinations (Inter / 10th Class). Reservations will be followed as per the rules. Weightage of 85 marks will be allotted for marks in the qualifying exam, reservation, local status and other standards. Remaining 15 marks will be for performance in interviews. The entire recruitment process will be conducted at the district level only and district collector will act as Chairan of the District Selection Committee.

Source: Upcoming Recruitment Notifications During 2011 – 2012 | VRO, VRA, UPSC, APPSC Jobs ~ College 2 Job

About these ads
Categories: Careers

APSRTC JUNIOR ASSISTANT Notifications

November 14, 2011 2 comments

 

 

Current Notifications :

   

Notification No.

Post

Payments Start Date

Application Submission Start Date

Payments Last Date

Application Submission Last Date

Date Of Written Exam

   

Notification No:
R2/684(22)/2011-HRD
1) Paper Notification
2) Instruction Boolet
3) FAQ’s

JUNIOR ASSISTANT FINANCE

10.11.2011

11.11.2011

28.11.2011 up to 5.00 P.M.

30.11.2011 up to 5.00 P.M

18.12.2011

Application Submission

 
   

Notification No.

Post

Payments Start Date

Application Submission Start Date

Payments Last Date

Application Submission Last Date

Date Of Written Exam

                   

Notification No:
R2/684(22)/2011-HRD
1) Paper Notification
2) Instruction Boolet
3) FAQ’s

JUNIOR ASSISTANT PERSONNEL

10.11.2011

11.11.2011

28.11.2011 up to 5.00 P.M.

30.11.2011 up to 5.00 P.M

22.01.2012

Application Submission

                 
   

Notification No.

Post

Payments Start Date

Application Submission Start Date

Payments Last Date

Application Submission Last Date

Date Of Written Exam

                   

Notification No:
R2/684(22)/2011-HRD
1) Paper Notification
2) Instruction Boolet
3) FAQ’s

JUNIOR ASSISTANT MATERIAL

10.11.2011

11.11.2011

28.11.2011 up to 5.00 P.M.

30.11.2011 up to 5.00 P.M

04.03.2012

Application Submission

                 
                 

HELP DESK

call Ph: +91 9246290436
For any Domain related issues contact the Helpline No. 9959223454 for any clarification
(Call Time : 10.30 A.M to 1.30 P.M & 2.00 P.M to 5 P.M on working days)

Check Application Status

CLICK HERE

Download the PDF Document of the Application which is Submitted Online.

CLICK HERE

APOnline Centres List

CLICK HERE

   
   
   
   

Source: APSRTC

Categories: Careers

Fix: PPTP VPN keeps on disconnecting after every minute

November 14, 2011 2 comments

Scenario:

When you connect to your office network via VPN tunnel from an outside Windows 7 x64 workstation, VPN successfully connects and then automatically disconnects after a minute with various error codes as shown below:

image

 

Troubleshooting:

In the logs you’ll see events like below:

Event Type:     Information                                                 
Event Source:   RasMan                                                 
Event Category: None                                                 
Event ID:       20268                                                 
Date:           6/30/2011                                                 
Time:           9:28:33 PM                                                 
User:           N/A                                                 
Computer:       TESTPC1                                                 
Description:
using device VPN3-1 was disconnected.                                                    
                                                                    

Event Type:     Information                                                 
Event Source:   RasMan                                                 
Event Category: None                                                 
Event ID:       20267                                                 
Date:           6/30/2011                                                 
Time:           9:28:04 PM                                                 
User:           N/A                                                 
Computer:       TESTPC1                                                 
Description:
using the device VPN3-1.                                                    
                                                                    

Event Type:     Information
Event Source:   Microsoft-Windows-UserPnp
Event Category: None
Event ID:       20010
Date:           6/30/2011
Time:           7:15:38 AM
User:           NT AUTHORITY\SYSTEM
Computer:       TESTPC1
Description:
The user connected to port true has been disconnected due to a system error. 
                                                                    

Event Type:     Information
Event Source:   Microsoft-Windows-UserPnp
Event Category: None
Event ID:       20010
Date:           6/30/2011
Time:           12:08:27 AM
User:           NT AUTHORITY\SYSTEM
Computer:       TESTPC1
Description:
The user connected to port false has been disconnected due to a system error. 

 

Environment: The most probable case that you’ll be running a standalone install of an Antivirus software on that PC.

 

Cause and Fix:

In my case, the cause was the standalone install of Symantec Endpoint Protection client version 11.0.62000.754. 

The fix is to stop “Symantec Management Client” (SmcService) service and then VPN to my work network. 

Note: You can still have the actual Antivisu scanning service “Symantec Endpoint Protection” (Symantec AntiVirus, "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\Rtvscan.exe") Running

Categories: Windows Technologies

Fix: PPTP VPN keeps on disconnecting after every minute

November 14, 2011 Leave a comment

Scenario:

When you connect to your office network via VPN tunnel from an outside Windows 7 x64 workstation, VPN successfully connects and then automatically disconnects after a minute with various error codes as shown below:

image

 

Troubleshooting:

In the logs you’ll see events like below:

Event Type:     Information                                                 
Event Source:   RasMan                                                 
Event Category: None                                                 
Event ID:       20268                                                 
Date:           6/30/2011                                                 
Time:           9:28:33 PM                                                 
User:           N/A                                                 
Computer:       TESTPC1                                                 
Description:
using device VPN3-1 was disconnected.                                                    
                                                                    

Event Type:     Information                                                 
Event Source:   RasMan                                                 
Event Category: None                                                 
Event ID:       20267                                                 
Date:           6/30/2011                                                 
Time:           9:28:04 PM                                                 
User:           N/A                                                 
Computer:       TESTPC1                                                 
Description:
using the device VPN3-1.                                                    
                                                                    

Event Type:     Information
Event Source:   Microsoft-Windows-UserPnp
Event Category: None
Event ID:       20010
Date:           6/30/2011
Time:           7:15:38 AM
User:           NT AUTHORITY\SYSTEM
Computer:       TESTPC1
Description:
The user connected to port true has been disconnected due to a system error. 
                                                                    

Event Type:     Information
Event Source:   Microsoft-Windows-UserPnp
Event Category: None
Event ID:       20010
Date:           6/30/2011
Time:           12:08:27 AM
User:           NT AUTHORITY\SYSTEM
Computer:       TESTPC1
Description:
The user connected to port false has been disconnected due to a system error. 

 

Environment: The most probable case that you’ll be running a standalone install of an Antivirus software on that PC.

 

Cause and Fix:

In my case, the cause was the standalone install of Symantec Endpoint Protection client version 11.0.62000.754. 

The fix is to stop “Symantec Management Client” (SmcService) service and then VPN to my work network. 

Note: You can still have the actual Antivisu scanning service “Symantec Endpoint Protection” (Symantec AntiVirus, "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\Rtvscan.exe") Running

Categories: Windows Technologies

Troubleshooting common VPN related errors – Routing and Remote Access Blog – Site Home – TechNet Blogs

November 14, 2011 Leave a comment

If you are seeing errors while establishing VPN connection using Windows in-built VPN client, you have reached the right place. This article will help you to easily troubleshoot some of the common VPN related errors.

1) Error Code: 800

Error Description: The remote connection was not made because the attempted VPN tunnels failed. The VPN server might be unreachable. If this connection is attempting to use an L2TP/IPsec tunnel, the security parameters required for IPsec negotiation might not be configured properly.

Possible Cause: This error comes when the VPN tunnel type is ‘Automatic’ and the connection establishment fails for all the VPN tunnels.

Possible Solutions:

a> If you know which tunnel should actually be used for your deployment, try to set the ‘Type of VPN’ to that particular tunnel type on the VPN client side. [This can be set by clicking the ‘Network Connections’ icon on the bottom right of the task bar, Select your Connection, Right Click -> Properties -> Securities Tab -> Under ‘Type of VPN’ select the interested VPN tunnel type ]

By making VPN connection with a particular tunnel type, your connection will still fail but it will give a more tunnel specific error (for example: GRE blocked for PPTP, Certificate error for L2TP, SSL negotiation errors for SSTP, etc.)

b> This error usually comes when the VPN server is not reachable or the tunnel establishment fails.

i. Make sure the VPN server is reachable (try to PING the server).

ii. If interested in PPTP, make sure PPTP port (TCP 1723) or GRE Port (47) is not blocked on in between firewalls.

iii. If interested in L2TP, make sure

1. Correct pre-shared key or machine certificate are present both on client and server.

2. L2TP port (UDP 1701) is not blocked on any of the firewalls.

iv. If interested in IKEv2 based VPN tunnel, make sure

1. IKE port (UDP port 500, UDP port 4500) is not blocked.

2. Correct machine certificate for IKE are present both on client and server.

v. If interested in SSTP, make sure correct machine certificate is installed on the server and correct trusted root certificate is installed on the client machine.

2) Error Code: 609, 633

Error Description:

609: A device type was specified that does not exist.

633: The modem (or other connecting device) is already in use or is not configured properly.

Possible Cause: This error usually comes when the connecting VPN device (aka miniport) is not configured properly.

To confirm the issue: From the elevated command prompt, type the following command to confirm the presence of miniport: -

netcfg.exe –q <miniport name>

Following is the Miniport Device name for different tunnels:

PPTP Tunnel: MS_PPTP

L2TP Tunnel: MS_L2TP

SSTP Tunnel: MS_SSTP

VPN Reconnect (IKEv2) Tunnel: MS_AGILEVPN

Possible Solution:

1. In Windows 7, a built-in diagnostic with repair is provided for the ‘miniport missing’ issue for locally created VPN connections. A ‘Diagnostic’ button is shown on the Error page of the VPN connection. By clicking this button, it will give a ‘repair’ option if it finds the issue to be miniport missing which if clicked will automatically try to fix the issue.

clip_image001

2. On Vista or below OS, if the miniport device is missing, you can run the following command from ‘elevated’ command prompt:

a> netcfg.exe -e -c p -i <miniport name>

Details of the <miniport name> is given above.

b> Stop and Start ‘rasman’ (‘Remote Access Connection Manager’) service.

3) Error Code: 732, 734, 812

Error Description:

732: Your computer and the remote computer could not agree on PPP control protocols.

734: The PPP link control protocol was terminated.

812: The connection was prevented because of a policy configured on your RAS/VPN server. Specifically, the authentication method used by the server to verify your username and password may not match the authentication method configured in your connection profile. Please contact the Administrator of the RAS server and notify them of this error.

Possible Causes: One of the prime causes for the above error is: when the *only* allowed authentication protocol configured on VPN server (or Radius server) is MS-CHAP and the VPN client is Vista or above OS platform (like Windows7). Note: due to security reasons MS-CHAP was removed from Vista and above OS platform and hence the connection fails.

Error 812 comes when Authentication protocol is set via NPS (Network Policy and Access Services) otherwise Error 732/734.

Event log 20276 is logged to the event viewer when RRAS based VPN server authentication protocol setting mismatches which that of the VPN client machine.

Possible Solution: Configure a more secured authentication protocol like MS-CHAPv2 or EAP based authentication on the server – which matches the settings on the client side.

4) Error Code: 806

Error Description: 806: The VPN connection between your computer and the VPN server could not be completed. The most common cause for this failure is that at least one Internet device (for example, a firewall or a router) between your computer and the VPN server is not configured to allow Generic Routing Encapsulation (GRE) protocol packets. If the problem persists, contact your network administrator or Internet Service Provider.

Possible Cause: PPTP uses GRE (Generic Route Encapsulation) protocol to encapsulate the VPN payload in a secure manner.This error generally comes when some firewall in path between client and server blocks GRE Protocol (i.e. IP protocol number 47).

Possible Solution: Allow both outgoing and incoming Protocol 47 (GRE) on any in between firewalls. If that is not possible, deploy SSTP based VPN tunnel on both VPN server and VPN client – that allows VPN connection across firewalls, web proxies and NAT.

5) Error Code: 789, 835

Error Description:

789: The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer.

835: The L2TP connection attempt failed because the security layer could not authenticate the remote computer. This could be because one or more fields of the certificate presented by the remote server could not be validated as belonging to the target destination.

Possible Causes: This is a generic error which is thrown when the IPSec negotiation fails for L2TP/IPSec connections.

Possible causes for this issue could be:

a> L2TP based VPN client (or VPN server) is behind NAT.

b> Wrong certificate or pre-shared key is set on the VPN server or client

c> Machine certificate or trusted root machine certificate is not present on the VPN server.

d> Machine Certificate on VPN Server does not have ‘Server Authentication’ as the EKU

Possible Solution: Make sure correct certificate is used both on client and server side – for further details refer to this blog. In case Pre Shared Key (PSK) is used, make sure the same PSK is configured on the client and the VPN server machine.

6) Error Code: 766

Error Description: 766: A certificate could not be found. Connections that use the L2TP protocol over IPSec require the installation of a machine certificate, also known as a computer certificate.

Possible Cause: This error usually comes when their is no valid machine certificate on your client machine.

Possible Solution: Make sure the correct machine certificate for L2TP validation is installed on your client machine – for further details refer to this blog.

7) Error Code: 691

Error Description: 691: The remote connection was denied because the user name and password combination you provided is not recognized, or the selected authentication protocol is not permitted on the remote access server.

Possible Cause: This error is given when the authentication phase erred out because of wrong credentials being passed.

Possible Solution:

a> Make sure correct username and password is typed.

b> Make sure ‘Caps Lock’ is not turned ON while typing credentials.

c> Make sure the authentication protocol as selected on the client is permitted on the server.

8) Error Code: 809

Error Description: 809: The network connection between your computer and the VPN server could not be established because the remote server is not responding. This could be because one of the network devices (e.g, firewalls, NAT, routers, etc) between your computer and the remote server is not configured to allow VPN connections. Please contact your Administrator or your service provider to determine which device may be causing the problem.

Possible Cause: This error usually comes when some firewall between client and server is blocking the ports used by VPN tunnel

a> PPTP port (TCP port 1723) is blocked by a firewall/router. [Applicable to tunnel type = PPTP]

b> L2TP or IKEv2 port (UDP port 500, UDP port 4500) is blocked by a firewall/router. [Applicable to tunnel type = L2TP or IKEv2]

Possible Solution: Enable the port (as mentioned above) on firewall/router. If that is not possible, deploy SSTP based VPN tunnel on both VPN server and VPN client – that allows VPN connection across firewalls, web proxies and NAT.

9) Error Code: 13806

Error Description: 13806: IKE failed to find valid machine certificate. Contact your Network Security Administrator about installing a valid certificate in the appropriate Certificate Store.

Possible Cause: This usually happens when there is no machine certificate or no root machine certificate present on the VPN Server.

Possible Solution: Please contact your VPN server administrator to verify and fix the issue – for further details refer to this blog.

10) Error Code: 13801

Error Description: 13801: IKE authentication credentials are unacceptable.

Possible Causes: This error usually comes in one of the following cases:

  1. The machine certificate used for IKEv2 validation on RAS Server does not have ‘Server Authentication’ as the EKU (Enhanced Key Usage).
  2. The machine certificate on RAS server has expired.
  3. The root certificate to validate the RAS server certificate is not present on the client.
  4. VPN Server Name as given on client doesn’t match with the subjectName of the server certificate.

Possible Solution: Please contact your VPN server administrator to verify and fix the above issue – for further details refer to this blog.

11) Error Code: 0x800704C9

Error Description:

Possible Cause: This issue may occur if no SSTP ports are available on the server.

Possible Solution: To troubleshoot this issue, verify that the RAS server has sufficient ports configured for remote access. To do this, follow these steps:

  1. Start the Routing and Remote Access MMC snap-in.
  2. Expand the server, right-click Ports, and then click Properties.
  3. In the Name list, click WAN Miniport (SSTP), and then click Configure.
  4. Modify the number that appears in the Maximum ports list, as appropriate for your requirements, and then click OK.
    Note By default, 128 ports are available for this device.
  5. In the Port Properties dialog box, click OK

12) Error Code: 0×80070040

Error Description:

Possible Cause: This issue may occur if a server authentication certificate is not installed on the RAS server.

Possible Solution: Make sure the machine certificate used by RAS server for SSL has ‘Server Authentication’ as one of the certificate usage entries. For further details refer to this blog. For changing the SSTP machine certificate, please refer to this blog if on VPN server is running Windows server 2008 R2, else refer to this blog

13) Error Code: 0x800B0101

Error Description: 0x800B0101: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

Possible Cause: This issue may occur if a server authentication certificate is not installed on the Routing and Remote Access server.

Possible Solution: Make sure the machine certificate used by RAS server for SSL has ‘Server Authentication’ as one of the certificate usage entries and the certificate is not expired. For further details refer to this blog. For changing the SSTP machine certificate, please refer to this blog if on VPN server is running Windows server 2008 R2, else refer to this blog

14) Error Code: 0x800B0109

Error Description: 0x800B0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.

Possible Cause: This issue may occur if the appropriate trusted root certification authority (CA) certificate is not installed in the Trusted Root Certification Authorities store on the client computer.

Note: Generally the VPN client machine is joined to the active directory based domain and if you use domain credentials to log on to the VPN server, the certificate is automatically installed in the Trusted Root Certification Authorities store. However, if the computer is not joined to the domain or if you use an alternative certificate chain, you may experience this issue.

Possible Solution: Make sure root certificate is installed on the client machine in the Trusted Root Certification Authorities store.

15) Error Code: 0x800B010F

Error Description: 0x800B010F: The certificate’s CN name does not match the passed value.

Possible Cause: This issue may occur if the host name of the server that is specified in the VPN connection does not match the subject name that is specified on the SSL certificate that the server submits to the client computer.

Possible Solution: Verify that the certificate which RAS server uses for SSL has the correct subject name. For example, if the VPN client is configured to use FQDN name to connect to the VPN server, the certificate used by VPN server must have FQDN in the subject name. Same thing if the client is configured to use IP address (IPv4 or IPv6) of VPN server. If the appropriately-named certificate is not present on the RAS server, you must obtain a new certificate for the RAS server.

For changing the SSTP machine certificate, please refer to this blog if on VPN server is running Windows server 2008 R2, else refer to this blog

16) Error Code: 0×80092013

Error Description: 0×80092013: The revocation function was unable to check revocation because the revocation server was offline.

Possible Cause: This issue may occur if the client computer fails the certificate revocation check for the SSL certificate that the client computer obtained from the VPN server.

Possible Solution: To troubleshoot this issue, verify that the server that hosts the Certificate Revocation List (CRL) is available to the client – before VPN tunnel is established. This means that the CRL server is available to the client over the Internet because the client computer runs the CRL check during the establishment of the SSL connection and the CRL check query is sent directly to the CRL server.

17) Error Code: 0x800704D4

Error Description: 0x800704D4: The network connection was aborted by the local system

Possible Cause: This error comes when the hostname of the VPN server is not resolved by the forward proxy in-front of the VPN client.

Possible Solution: Check your proxy settings inside the Internet explorer. If the settings are correct, please ensure you are able to access other web sites (e.g. www.microsoft.com) using the browser. If that also works through, try accessing the URI which SSTP uses internally i.e. https://vpn_server_name/sra_{BA195980-CD49-458b-9E23-C84EE0ADCD75}/ – please replace vpn_server_name with actual VPN server name. If you see error “the website cannot be found” inside your browser, that validates the hostname resolution failure. If you know the IP address of VPN server, try connecting with that. Else contact your network administrator (who is responsible for managing the web proxy – most probably your ISP) – giving them the details of the problem (i.e. hostname resolution is failing for that particular hostname).

18) Error Code: 0×80072746

Error Description: 0×80072746: An existing connection was forcibly closed by the remote host.

Possible Cause: This error comes when the server machine certificate binding to HTTPS is not done on the VPN server OR the server machine certificate is not installed on the VPN server.

Possible Solution: Please contact your VPN server administrator – to check whether relevant machine certificate is installed on the VPN server. If installed correctly, check the HTTPS binding by running following command at the VPN server command prompt – “netsh http show ssl”. For further details, please refer to this blog.

Further References:

Troubleshooting articles @ RRAS blog site

How to troubleshoot SSTP based connection failure in Windows

Source: Troubleshooting common VPN related errors – Routing and Remote Access Blog – Site Home – TechNet Blogs

Categories: Windows Technologies

List of Error Codes that you may receive when you try to make a dial-up connection or a VPN connection in Windows Vista

November 14, 2011 Leave a comment

This article lists the Error Codes that you may receive when you try to make a dial-up connection or a VPN connection on a computer that is running Microsoft Windows Vista.

MORE INFORMATION

The following list contains the Error Codes that you may receive when you try to…

The following list contains the Error Codes that you may receive when you try to make a dial-up connection or a VPN connection:
600
An operation is pending.
601
The port handle is invalid.
602
The port is already open.
603
Caller’s buffer is too small.
604
Wrong information specified.
606
The port is not connected.
608
The device does not exist.
609
The device type does not exist.
610
The buffer is invalid.
612
The route is not allocated.
615
The port was not found.
616
An asynchronous request is pending.
617
The port or device is already disconnecting.
618
The port is not open.
619
The port is disconnected.
621
Cannot open the phone book file.
622
Cannot load the phone book file.
623
Cannot find the phone book entry.
624
Cannot write the phone book file.
625
Invalid information found in the phone book.
627
Cannot find key.
628
The port was disconnected.
629
The port was disconnected by the remote machine.
630
The port was disconnected due to hardware failure.
631
The port was disconnected by the user.
632
The structure size is incorrect.
633
The port is already in use or is not configured for Remote Access dialout.
Note In this error message, the word "dialout" is a misspelling for the words "dial out."
635
Unknown error.
636
The wrong device is attached to the port.
638
The request has timed out.
645
Internal authentication error.
646
The account is not permitted to log on at this time of day.
647
The account is disabled.
648
The password has expired.
649
The account does not have Remote Access permission.
651
Your modem (or other connecting device) has reported an error.
652
Unrecognized response from the device.
653
A macro required by the device was not found in the device .INF file section.
654
A command or response in the device .INF file section refers to an undefined macro
655
The <message> macro was not found in the device .INF file section.
656
The <defaultoff> macro in the device .INF file section contains an undefined macro
657
The device .INF file could not be opened.
658
The device name in the device .INF or media .INI file is too long.
659
The media .INI file refers to an unknown device name.
660
The device .INF file contains no responses for the command.
661
The device .INF file is missing a command.
662
Attempted to set a macro not listed in device .INF file section.
663
The media .INI file refers to an unknown device type.
664
Cannot allocate memory.
665
The port is not configured for Remote Access.
666
Your modem (or other connecting device) is not functioning.
667
Cannot read the media .INI file.
668
The connection dropped.
669
The usage parameter in the media .INI file is invalid.
670
Cannot read the section name from the media .INI file.
671
Cannot read the device type from the media .INI file.
672
Cannot read the device name from the media .INI file.
673
Cannot read the usage from the media .INI file.
676
The phone line is busy.
677
A person answered instead of a modem.
678
There is no answer.
679
Cannot detect carrier.
680
There was no dial tone.
691
Access denied because username and/or password is invalid on the domain.
692
Hardware failure in port or attached device.
693
ERROR NOT BINARY MACRO
694
ERROR DCB NOT FOUND
695
ERROR STATE MACHINES NOT STARTED
696
ERROR STATE MACHINES ALREADY STARTED
697
ERROR PARTIAL RESPONSE LOOPING
698
A response keyname in the device .INF file is not in the expected format.
699
The device response caused buffer overflow.
700
The expanded command in the device .INF file is too long.
701
The device moved to a BPS rate not supported by the COM driver.
702
Device response received when none expected.
703
ERROR INTERACTIVE MODE
704
ERROR BAD CALLBACK NUMBER
705
ERROR INVALID AUTH STATE
707
X.25 diagnostic indication.
708
The account has expired.
709
Error changing password on domain.
710
Serial overrun errors were detected while communicating with your modem.
711
RasMan initialization failure. Check the event log.
713
No active ISDN lines are available.
716
The Remote Access IP configuration is unusable.
717
No IP addresses are available in the static pool of Remote Access IP addresses.
718
PPP timeout.
720
No PPP control protocols configured.
721
Remote PPP peer is not responding.
722
The PPP packet is invalid.
723
The phone number, including prefix and suffix, is too long.
726
The IPX protocol cannot be used for dial-out on more than one port at a time.
728
Cannot find an IP adapter bound to Remote Access.
729
SLIP cannot be used unless the IP protocol is installed.
730
Computer registration is not complete.
731
The protocol is not configured.
732
The PPP negotiation is not converging.
733
The PPP control protocol for this network protocol is not available on the server.
734
The PPP link control protocol terminated..
735
The requested address was rejected by the server.
736
The remote computer terminated the control protocol.
737
Loopback detected.
738
The server did not assign an address.
739
The remote server cannot use the Windows NT encrypted password.
740
The TAPI devices configured for Remote Access failed to initialize or were not installed correctly.
741
The local computer does not support encryption.
742
The remote server does not support encryption.
749
ERROR_BAD_PHONE_NUMBER
752
A syntax error was encountered while processing a script.
753
The connection could not be disconnected because it was created by the multi-protocol router.
754
The system could not find the multi-link bundle.
755
The system cannot perform automated dial because this connection has a custom dialer specified.
756
This connection is already being dialed.
757
Remote Access Services could not be started automatically. Additional information is provided in the event log.
764
No smart card reader is installed.
765
Internet Connection Sharing cannot be enabled. A LAN connection is already configured with the IP address that is required for automatic IP addressing.
766
A certificate could not be found. Connections that use the L2TP protocol over IPSec require the installation of a machine certificate, also known as a computer certificate.
767
Internet Connection Sharing cannot be enabled. The LAN connection selected as the private network has more than one IP address configured. Please reconfigure the LAN connection with a single IP address before enabling Internet Connection Sharing.
768
The connection attempt failed because of failure to encrypt data.
769
The specified destination is not reachable.
770
The remote computer rejected the connection attempt.
771
The connection attempt failed because the network is busy.
772
The remote computer’s network hardware is incompatible with the type of call requested.
773
The connection attempt failed because the destination number has changed.
774
The connection attempt failed because of a temporary failure. Try connecting again.
775
The call was blocked by the remote computer.
776
The call could not be connected because the remote computer has invoked the Do Not Disturb feature.
777
The connection attempt failed because the modem (or other connecting device on the remote computer is out of order.
778
It was not possible to verify the identity of the server.
780
An attempted function is not valid for this connection.
782
Internet Connection Sharing (ICS and Internet Connection Firewall (ICF cannot be enabled because Routing and Remote Access has been enabled on this computer. To enable ICS or ICF, first disable Routing and Remote Access. For more information about Routing and Remote Access, ICS, or ICF, see Help and Support.
783
Internet Connection Sharing cannot be enabled. The LAN connection selected as the private network is either not present, or is disconnected from the network. Please ensure that the LAN adapter is connected before enabling Internet Connection Sharing.
784
You cannot dial using this connection at logon time, because it is configured to use a user name different than the one on the smart card. If you want to use it at logon time, you must configure it to use the user name on the smart card.
785
You cannot dial using this connection at logon time, because it is not configured to use a smart card. If you want to use it at logon time, you must edit the properties of this connection so that it uses a smart card.
786
The L2TP connection attempt failed because there is no valid machine certificate on your computer for security authentication.
787
The L2TP connection attempt failed because the security layer could not authenticate the remote computer.
788
The L2TP connection attempt failed because the security layer could not negotiate compatible parameters with the remote computer.
789
The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer.
790
The L2TP connection attempt failed because certificate validation on the remote computer failed.
791
The L2TP connection attempt failed because security policy for the connection was not found.
792
The L2TP connection attempt failed because security negotiation timed out.
793
The L2TP connection attempt failed because an error occurred while negotiating security.
794
The Framed Protocol RADIUS attribute for this user is not PPP.
795
The Tunnel Type RADIUS attribute for this user is not correct.
796
The Service Type RADIUS attribute for this user is neither Framed nor Callback Framed.
797
A connection to the remote computer could not be established because the modem was not found or was busy. For further assistance, click More Info or search Help and Support Center for this error number.
798
A certificate could not be found that can be used with this Extensible Authentication Protocol.
799
Internet Connection Sharing (ICS cannot be enabled due to an IP address conflict on the network. ICS requires the host be configured to use 192.168.0.1. Please ensure that no other client on the network is configured to use 192.168.0.1.
800
Unable to establish the VPN connection. The VPN server may be unreachable, or security parameters may not be configured properly for this connection.
801
This connection is configured to validate the identity of the access server, but Windows cannot verify the digital certificate sent by the server.
802
The card supplied was not recognized. Please check that the card is inserted correctly, and fits tightly.
803
The PEAP configuration stored in the session cookie does not match the current session configuration.
804
The PEAP identity stored in the session cookie does not match the current identity.
805
You cannot dial using this connection at logon time, because it is configured to use logged on user’s credentials.
806
A connection between your computer and the VPN server has been started, but the VPN connection cannot be completed. The most common cause for this is that at least one Internet device (for example, a firewall or a router) between your computer and the VPN server is not configured to allow Generic Routing Encapsulation (GRE) protocol packets. If the problem persists, contact your network administrator or Internet service provider.
807
The network connection between your computer and the VPN server was interrupted. This can be caused by a problem in the VPN transmission and is commonly the result of internet latency or simply that your VPN server has reached capacity. Please try to reconnect to the VPN server. If this problem persists, contact the VPN administrator and analyze quality of network connectivity.
808
The network connection between your computer and the VPN server could not be established because the remote server refused the connection. This is typically caused by a mismatch between the server’s configuration and your connection settings. Please contact the remote server’s Administrator to verify the server configuration and your connection settings.
809
The network connection between your computer and the VPN server could not be established because the remote server is not responding. This could be because one of the network devices (e.g., firewalls, NAT, routers, etc.) between your computer and the remote server is not configured to allow VPN connections. Please contact your Administrator or your service provider to determine which device may be causing the problem.
810
A network connection between your computer and the VPN server was started, but the VPN connection was not completed. This is typically caused by the use of an incorrect or expired certificate for authentication between the client and the server. Please contact your Administrator to ensure that the certificate being used for authentication is valid.
811
The network connection between your computer and the VPN server could not be established because the remote server is not responding. This is typically caused by a pre-shared key problem between the client and server. A pre-shared key is used to guarantee you are who you say you are in an IP Security (IPSec) communication cycle. Please get the assistance of your administrator to determine where the pre-shared key problem is originating.
812
The connection was prevented because of a policy configured on your RAS/VPN server. Specifically, the authentication method used by the server to verify your username and password may not match the authentication method configured in your connection profile. Please contact the Administrator of the RAS server and notify them of this error.
813
You have attempted to establish a second broadband connection while a previous broadband connection is already established using the same device or port. Please disconnect the earlier connection and then re-establish the connection.
814
The underlying Ethernet connectivity required for the broadband connection was not found. Please install and enable the Ethernet adapter on your computer via the Network Connections folder before attempting this connection.
815
The broadband network connection could not be established on your computer because the remote server is not responding. This could be caused by an invalid value for the ‘Service Name’ field for this connection. Please contact your Internet Service Provider and inquire about the correct value for this field and update it in the Connection Properties.
816
A feature or setting you have tried to enable is no longer supported by the remote access service.
817
Cannot delete a connection while it is connected.
818
The Network Access Protection (NAP) enforcement client could not create system resources for remote access connections. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server.
819
The Network Access Protection Agent (NAP Agent) service has been disabled or is not installed on this computer. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server.
820
The Network Access Protection (NAP) enforcement client failed to register with the Network Access Protection Agent (NAP Agent) service. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server.
821
The Network Access Protection (NAP) enforcement client was unable to process the request because the remote access connection does not exist. Retry the remote access connection. If the problem persists, make sure that you can connect to the Internet, and then contact the administrator for the remote access server.
822
The Network Access Protection (NAP) enforcement client did not respond. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server.
823
Received Crypto-Binding TLV is invalid.
824
Crypto-Binding TLV is not received.
825
Point-to-Point Tunnelling Protocol (PPTP) is incompatible with IPv6. Change the type of virtual private network to Layer Two Tunnelling Protocol (L2TP)
Note In this 8255 error message, the word "Tunnelling" is a misspelling for the word "Tunneling."
826
EAPTLS validation of the cached credentials failed. Please discard cached credentials.
827
The L2TP/IPsec connection cannot be completed because the IKE and AuthIP IPSec Keying Modules service and/or the Base Filtering Engine service is not running. These services are required to establish an L2TP/IPSec connection. Please ensure that these services have been started before dialling the connection
Note In this 827 error message, the word "dialling" is a misspelling for the word "dialing."



APPLIES TO
  • Windows Vista Business
  • Windows Vista Enterprise
  • Windows Vista Home Basic
  • Windows Vista Home Premium
  • Windows Vista Ultimate

Source: List of Error Codes that you may receive when you try to make a dial-up connection or a VPN connection in Windows Vista

Categories: Windows Technologies

Grahak Seva: The Mental harassment of Indians

November 14, 2011 Leave a comment
The Mental harassment of Indians

One of the most commonly used terms in our users’ complaints is "Mental Harassment". Before launching the Jago Grahak Jago Initiative, we thought things doesn’t work only in government machinery, but the results and the complaints that started coming in were surprising. 80% of the complaints are against big companies, and we have so much data that it cannot be rejected considering it as just one off case.
Consider the following:
- Most of the movers and packers in India do mishandling and do not pay the damage even after customers insure the consignment.
- Delay in delivery and making false commitments is a common culture in Indian business, and nobody cares.
- Gas agencies never pick up the phone. Customers are clueless what is the status of their LPG supply. When they visit the agency offices, nobody is willing to answer. Did you ever go to your LPG agency and did you observe the chaos?
- Mobile companies have found a new way of making money. Activate services which customers do not want. 80% of the complaints against phone companies are related to activation of services without customers knowledge. Some companies send SMS that they are getting free service for 30 days, and then there is no way to deactivate after 30 days. Our customer care sucks. India supports the world in their world-class call centers, but there is no support for Indians.
- False ATM transactions are on the rise. Banks do not help. So please try to avoid withdrawing from different bank ATM, you will realize the pain when nothing comes out, but your account is debited. Trust me nobody will help.
- God save us from private banks. The minimum balance requirements, the annual account maintenance fees, huge penalties for small small things, again the price is paid by us.
- It seems whole India is going through this Insurance scam. We have seen several complaints about people paying their hard earned income to private insurance companies only to later realize that they cannot get their money back. Personal advice please go for LIC.
- We received a new complaint in its kind, exams getting postponed. Now it might be a good news for students, but no, these exams get postponed because professors (who by the way gets paid out of our taxes) didn’t set papers in time. The exam co-ordinator didn’t allot the roll numbers, organize exam venues and hence exam postponement. This is unacceptable, just because of the inefficiencies of our Govenment servants.
- Last but not the least, The survey companies. Are we crazy, did our mind stop thinking ? How can you make money by doing nothing and just participating in surveys. There is like flood of survey companies in India. Some of them already shut down and their founders absconding. An appeal GrahakSeva users, there is no such thing like work from home, earn part time income, refer people and earn, participate in survey and become lakpati. Please stay away from any such schemes, and spread the word to your friends and relatives.
As I write this post, I heard that AIEE paper is leaked in UP.
More information here.
Please share your thoughts, suggestions and requests at think@grahakseva.com
And yes, keep complaining.

Source: Grahak Seva: The Mental harassment of Indians

Categories: Legal

AxisBank: Fixed Deposits – Deposit Schemes,Withdrawals and Method of calculation of interest

November 14, 2011 Leave a comment

Fixed Deposits

Safety, Security and Growth

Axis Bank offers you simple reinvestment Fixed Deposits (at very competitive interest rates), which can be opened with a minimum investment of Rs 10,000. You can make additions to your deposit in multiples of Rs 1,000 each. The tenure of your deposit must be a minimum of 6 months.

Deposit Schemes

Reinvestment Deposits:
In a reinvestment deposit, the interest accrued to your deposit at the end of each quarter is invested along with the principal. The tenure of your deposit must be a minimum of 6 months. At the end of the quarter, the interest and the principal are both rolled over, and the interest is calculated on the total sum. Income tax is deducted at source.

Automatic Rollover:
As a Fixed Deposit holder, you can avail of the facility for automatic rollovers on maturity (for both the principal and interest). You can select this option in the Account Opening Document (AOD). The options available are:

  • Rollover only Principal:
    Only the principal amount will be rolled over. The interest will be either credited to your designated account or paid out.
  • Rollover Principal and Interest accrued in Reinvestment Deposit:
    This will rollover both the deposit and the interest accrued for the same tenure at the interest rate applicable on the maturity date.

On or before the maturity date, you can make the following changes in the rollover instructions of the deposit:

  • Change in tenure
  • Change in maturity instructions
  • Change in payment instructions
  • Change in principal (only reduced amount)
  • Change rollover of Principal to rollover of Principal + Interest, or vice versa.

Withdrawals

All encashments or withdrawals of Fixed Deposits can only be made at the branch where the deposit was booked.

Method of calculation of interest

  • For deposits with tenure of 6 months & above, interest is calculated on a quarterly basis.
  • Interest earned during the previous quarter is added to the Principal for calculation of interest. Interest on this amount is calculated every quarter.
  • For deposits with tenure of below 6 months, interest is calculated at Simple Interest. Please note that the period of Fixed Deposit is considered in number of days.
  • In the event the depositor chooses to receive the periodic interest payments on a quarterly basis, interested is calculated and paid on quarterly rests.
  • On premature withdrawal of the deposit, interest shall be paid only for the period for which the deposit is maintained with the Bank and at the rate applicable for such period.
  • Tax at source is deducted as per the Income Tax regulations prevalent from time to time.

Source: http://www.axisbank.com/personal/deposits/fixeddeposits/Fixed-Deposits.asp

Categories: Financial

Internet Explorer Group Policy Preferences do not apply to Internet Explorer 9 in a Windows Server 2008 R2 domain environment

November 14, 2011 Leave a comment

Consider the following scenario on a Windows 7-based or Windows Server 2008 R2-b…

Consider the following scenario on a Windows 7-based or Windows Server 2008 R2-based computer:

  • You have a domain server that is running Windows Server 2008 R2.
  • You use the Group Policy Administration Tools for Windows Server 2008 R2.

In this scenario, in the domain in which you are using Internet Explorer Group Policy Preferences, you encounter the following problems.

Problem 1

Microsoft Internet Explorer 6, Windows Internet Explorer 7, and Windows Internet Explorer 8 Group Policy Preference items do not apply to users who are running Windows Internet Explorer 9.
Group Policy Preferences logging shows the following.

Nonworking scenario

yyyy-mm-dd hh:mm:ss.ms [pid=0x3a0,tid=0xb18] {683F7AD7-E782-4232-8A6D-F22431F12DB5}
yyyy-mm-dd hh:mm:ss.ms [pid=0x3a0,tid=0xb18] Starting class <IE8> – Internet Explorer 8.
yyyy-mm-dd hh:mm:ss.ms [pid=0x3a0,tid=0xb18] Starting filter [AND FilterFile].
yyyy-mm-dd hh:mm:ss.ms [pid=0x3a0,tid=0xb18] Adding child elements to RSOP.
yyyy-mm-dd hh:mm:ss.ms [pid=0x3a0,tid=0xb18] Set user security context.
yyyy-mm-dd hh:mm:ss.ms [pid=0x3a0,tid=0xb18] C:\Program Files\Internet Explorer\iexplore.exe
yyyy-mm-dd hh:mm:ss.ms [pid=0x3a0,tid=0xb18] apmGetFileVersionEx
yyyy-mm-dd hh:mm:ss.ms [pid=0x3a0,tid=0xb18] apmCompareVersionTokens [SUCCEEDED(S_FALSE)]
yyyy-mm-dd hh:mm:ss.ms [pid=0x3a0,tid=0xb18] Set system security context.
yyyy-mm-dd hh:mm:ss.ms [pid=0x3a0,tid=0xb18] Failed hidden filter [FilterFile].
yyyy-mm-dd hh:mm:ss.ms [pid=0x3a0,tid=0xb18] Filters not passed.
yyyy-mm-dd hh:mm:ss.ms [pid=0x3a0,tid=0xb18] Completed class <IE8> – Internet Explorer 8.
yyyy-mm-dd hh:mm:ss.ms [pid=0x3a0,tid=0xb18] Completed class <InternetSettings>.

Working scenario

yyyy-mm-dd hh:mm:ss.ms [pid=0x398,tid=0x29c] {683F7AD7-E782-4232-8A6D-F22431F12DB5}
yyyy-mm-dd hh:mm:ss.ms [pid=0x398,tid=0x29c] Starting class <IE8> – Internet Explorer 8.
yyyy-mm-dd hh:mm:ss.ms [pid=0x398,tid=0x29c] Starting filter [AND FilterFile].
yyyy-mm-dd hh:mm:ss.ms [pid=0x398,tid=0x29c] Adding child elements to RSOP.
yyyy-mm-dd hh:mm:ss.ms [pid=0x398,tid=0x29c] Set user security context.
yyyy-mm-dd hh:mm:ss.ms [pid=0x398,tid=0x29c] C:\Program Files\Internet Explorer\iexplore.exe
yyyy-mm-dd hh:mm:ss.ms [pid=0x398,tid=0x29c] apmGetFileVersionEx
yyyy-mm-dd hh:mm:ss.ms [pid=0x398,tid=0x29c] apmCompareVersionTokens
yyyy-mm-dd hh:mm:ss.ms [pid=0x398,tid=0x29c] Set system security context.
yyyy-mm-dd hh:mm:ss.ms [pid=0x398,tid=0x29c] Passed hidden filter [FilterFile].
yyyy-mm-dd hh:mm:ss.ms [pid=0x398,tid=0x29c] Filters passed.

Problem 2

Group Policy Preferences for Internet Explorer policy only exposes options for Internet Explorer 5, for Internet Explorer 6, for Internet Explorer 7, and for Internet Explorer 8. For example, the following screen shot shows that no option appears for Internet Explorer 9 computers:

Collapse this imageExpand this image

No Internet Explorer 9 Options.

Back to the top

CAUSE

Problem 1 Internet Explorer 6, Internet Explorer 7, and Explorer 8 Group Policy…

Problem 1

Internet Explorer 6, Internet Explorer 7, and Explorer 8 Group Policy Preference items do not apply to users who are running Internet Explorer 9.
Internet Explorer Group Policy Preference items include a targeting item that is a hidden file. This targeting item checks the version of Internet Explorer that is running to make sure that this version matches the version that is selected in the Group Policy Management Editor. This means, for example, that Internet Explorer 8 preference items only apply to computers that use Internet Explorer 8.
The targeting item fails because the version number of Internet Explorer 9 is greater than minimum and maximum values that are selected in the preference item. Therefore, the preference item does not apply to Internet Explorer 9.

Problem 2

No Group Policy Preferences appear for Internet Explorer 9.
Internet Explorer settings in Group Policy Preferences are part of the Windows operating system. The general release dates for Windows Server 2008 and for Windows Server 2008 R2 pre-date the release of Internet Explorer 9. Internet Explorer 9 is precluded from shipping with updated Internet Explorer preferences. Therefore, Group Policy Preferences for Internet Explorer 9 are not supported in the release of Windows Server 2008 R2.

Back to the top

RESOLUTION

Hotfix information A supported hotfix is available from Microsoft. However, this…

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:

  • Windows 7
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 (http://support.microsoft.com/kb/976932/ ) Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information notes
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Collapse this tableExpand this table

    Version
    Product
    Milestone
    Service branch

    6.1.760 0.21xxx
    Windows 7 and Windows Server 2008 R2
    RTM
    LDR

    6.1.760 1.21xxx
    Windows 7 and Windows Server 2008 R2
    SP1
    LDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7

Collapse this tableExpand this table

File name
File version
File size
Date
Time
Platform

Gppref.dll
6.1.7600.21049
4,343,296
09-Sep-2011
04:31
x86

Gpprefbr.dll
6.1.7600.21049
627,712
09-Sep-2011
04:31
x86

Gpprefcn.dll
6.1.7600.21049
166,400
09-Sep-2011
04:31
x86

Propshts.dll
6.1.7600.21049
2,548,736
09-Sep-2011
04:31
x86

Gppref.dll
6.1.7601.21814
4,343,296
09-Sep-2011
06:18
x86

Gpprefbr.dll
6.1.7601.21814
627,712
09-Sep-2011
06:18
x86

Gpprefcn.dll
6.1.7601.21814
166,400
09-Sep-2011
06:18
x86

Propshts.dll
6.1.7601.21814
2,548,736
09-Sep-2011
06:18
x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

Collapse this tableExpand this table

File name
File version
File size
Date
Time
Platform

Gppref.dll
6.1.7600.21049
4,889,088
09-Sep-2011
05:18
x64

Gpprefbr.dll
6.1.7600.21049
901,632
09-Sep-2011
05:18
x64

Gpprefcn.dll
6.1.7600.21049
236,032
09-Sep-2011
05:18
x64

Propshts.dll
6.1.7600.21049
3,787,776
09-Sep-2011
05:18
x64

Gppref.dll
6.1.7601.21814
4,889,088
09-Sep-2011
06:22
x64

Gpprefbr.dll
6.1.7601.21814
901,632
09-Sep-2011
06:22
x64

Gpprefcn.dll
6.1.7601.21814
236,032
09-Sep-2011
06:22
x64

Propshts.dll
6.1.7601.21814
3,787,776
09-Sep-2011
06:22
x64

Gppref.dll
6.1.7600.21049
4,343,296
09-Sep-2011
04:31
x86

Gpprefbr.dll
6.1.7600.21049
627,712
09-Sep-2011
04:31
x86

Gpprefcn.dll
6.1.7600.21049
166,400
09-Sep-2011
04:31
x86

Propshts.dll
6.1.7600.21049
2,548,736
09-Sep-2011
04:31
x86

Gppref.dll
6.1.7601.21814
4,343,296
09-Sep-2011
06:18
x86

Gpprefbr.dll
6.1.7601.21814
627,712
09-Sep-2011
06:18
x86

Gpprefcn.dll
6.1.7601.21814
166,400
09-Sep-2011
06:18
x86

Propshts.dll
6.1.7601.21814
2,548,736
09-Sep-2011
06:18
x86

For all supported IA-64-based versions of Windows Server 2008 R2

Collapse this tableExpand this table

File name
File version
File size
Date
Time
Platform

Gppref.dll
6.1.7600.21049
6,577,664
09-Sep-2011
04:11
IA-64

Gpprefbr.dll
6.1.7600.21049
1,786,880
09-Sep-2011
04:11
IA-64

Gpprefcn.dll
6.1.7600.21049
463,360
09-Sep-2011
04:11
IA-64

Propshts.dll
6.1.7600.21049
7,068,160
09-Sep-2011
04:11
IA-64

Gppref.dll
6.1.7601.21814
6,577,664
09-Sep-2011
04:14
IA-64

Gpprefbr.dll
6.1.7601.21814
1,786,880
09-Sep-2011
04:14
IA-64

Gpprefcn.dll
6.1.7601.21814
463,360
09-Sep-2011
04:14
IA-64

Propshts.dll
6.1.7601.21814
7,068,160
09-Sep-2011
04:14
IA-64

Gppref.dll
6.1.7600.21049
4,343,296
09-Sep-2011
04:31
x86

Gpprefbr.dll
6.1.7600.21049
627,712
09-Sep-2011
04:31
x86

Gpprefcn.dll
6.1.7600.21049
166,400
09-Sep-2011
04:31
x86

Propshts.dll
6.1.7600.21049
2,548,736
09-Sep-2011
04:31
x86

Gppref.dll
6.1.7601.21814
4,343,296
09-Sep-2011
06:18
x86

Gpprefbr.dll
6.1.7601.21814
627,712
09-Sep-2011
06:18
x86

Gpprefcn.dll
6.1.7601.21814
166,400
09-Sep-2011
06:18
x86

Propshts.dll
6.1.7601.21814
2,548,736
09-Sep-2011
06:18
x86

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that ar…

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

MORE INFORMATION

The software update changes the values that are used for the internal filter for…

The software update changes the values that are used for the internal filter for Internet Explorer 8 so that the settings also apply to Internet Explorer 9. To do this, the update that is described in this KB article must be installed on the computer where you edit the policy settings.
Notes

  • This update does not re-write the version information for existing settings. Instead, you must define a new set of Internet Explorer settings in a new or existing Group Policy Object.
  • This update does not create a new Internet Explorer 9 UI item. However, when define new Group Policy Preferences settings, and you select the Internet Explorer 8 option, this setting now applies both to Internet Explorer 8 and to Internet Explorer 9.

After you install this update, the settings that are available for the Internet Explorer 8 option also apply to Internet Explorer 9. However, no new settings are available that are specific only to Internet Explorer 9.
The management of Internet Explorer 9 settings can also be controlled through ADMX or through Internet Explorer Maintenance. More information is available at these websites:

Using Administrative Templates (http://technet.microsoft.com/en-us/library/gg699412.aspx)
Using Internet Explorer Maintenance Extension (http://technet.microsoft.com/en-us/library/gg699413.aspx)

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates

 

APPLIES TO
  • Windows 7 Professional
  • Windows 7 Enterprise
  • Windows 7 Ultimate
  • Windows Web Server 2008 R2
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Foundation
  • Windows Vista Service Pack 2
  • Windows Server 2008 Service Pack 2

Source: Internet Explorer Group Policy Preferences do not apply to Internet Explorer 9 in a Windows Server 2008 R2 domain environment

Categories: Browsers, Server 2008 R2
Follow

Get every new post delivered to your Inbox.

Join 212 other followers