Tuesday, April 17, 2018

Lenovo Laptop Brightness Issue

Today I faced a very peculiar issue, we had a display driver update for our Lenovo Laptops Z500 and suddenly the brightness went to 0 no matter what we did, nor even the reboot resolved the issue.

finally this registry setting did the trick.


[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000]

"FeatureTestControl"=dword:0000f048


Changed the dword from f048 to ffff

or whatever the value just change it to ffff

rebooted the laptop and all was fine and functional again. lot of Lenovo laptops of even different models are facing this brightness issue.

just open regedit and find FeatureTestControl

take the backup of the registry settings before making these changes. always do a backup. one day you will thank for this advice.

maybe this helps someone somewhere.

Monday, April 16, 2018

Outlook keeps prompting for password Exchange 2013 / 2016

Like any Exchange admin I too came accross connectivity issues from Outlook client to Exchange

The issues which I faced with both Exchange 2013 & 2016, with Outlook 2013 & 2016, it kept on asking the users for password, no matter what I did, the issue could not be resolved.

Finally the following steps resolved this issue and all users are now happy.

lets us assume we have mail domain as mymaildomain, your External hostname &  Certificate name is mail.mydomain.com

open exchange management shell and run the following commands

first we set Outlook certificate name

Set-outlookprovider expr -certprincipalname: "msstd:mail.mymaildomain.com"
Set-outlookprovider exch -certprincipalname: "msstd:mail.mymaildomain.com"

then we set outlook authentication & the way outlook should treat the connection settings

Set-outlookanywhere -InternalHostname mail.mymaildomain.com -ExternalHostname mail.mymaildomain.com -identity "EXCSrv\Rpc (Default Web Site)" -InternalClientAuthenticationMethod ntlm -ExternalClientAuthenticationMethod ntlm -internalclientsrequiressl $true -Externalclientsrequiressl $true -IISAuthenticationMethods basic,ntlm,negotiate

Dont forget to change the mymaildomain name to reflect your mail domain.

FileZilla Error 425 Can't open data connection Failed to retrieve directory list

I was configuring a FileZilla FTP server on Azure windows VM, the client was able to connect & authorize but got error

Command: LIST
Response: 425 Can't open data connection.
Error: Failed to retrieve directory list

so to resolve this issue I did following

Open FileZilla settings

1) Select Passive mode settings
2) Select Use custom ports and enter range of ports what ever you like, I used 60800-60900
3) Select use following IP and Enter your Azure VM external IP Click save
4) Go to your Azure Portal under Network>> Firewall, Add the ports used in Step 3 in Allow range
5) Now connect with your FTP client and it will connect without any issues.

Worked like charm….

Tuesday, July 26, 2016

Exchange 2013 DAG Database SEED ERROR / ADD ERROR

Hi,

For some reason My DAG database copies started to FAIL,

Error: Failed to open a log truncation context to source server ‘Ex2013_01.Mail.Com’. Hresult: 0xc7ff1004. Error: Error returned from an ESE function call (-1305).

Resolution:

Source Server : Ex2013_01.Mail.Com
Target/failing server :  Ex2013_02.Mail.Com
Database name: DB2
DB location :  D:/Database
Logs Location: D:/Database/Logs

on the target Server where the Database is Failing/ or being Added to...

1) Delete the Failing Database
2) Add the database copy : Add-MailboxDatabaseCopy -Identity DB2 -MailboxServer Ex2013_02 -ActivationPreference 2
3) You will see same ERROR: no worries
4) Go to the Database Folder location :  D:/Database/Logs
5) Move all the log files to another location
6) Open Exchange Management shell and run: Update-MailboxDatabaseCopy "DB2\Ex2013_02" -SourceServer Ex2013_01  -Verbose

and your database will start seeding...

Remember not to Logoff or Close the Shell else it will stop seeding...

Thanks


Tuesday, March 18, 2014

Outlook 2007 keeps on disconnecting from Exchange


One of our user was having issue of frequent disconnection and reconnection to exchange server

Now... the issue is not with Exchange, Internet, VPN tunnel etc. etc.... as suggested all around the internet...

Its with regestry settings on Client side, for connection timeout... Dont know how it got messed up....

Following steps require you to edit registry. PLEASE TAKE A BACKUP BEFORE GOING AHEAD..

Right clkick on the Key and Select EXPORT.... Save it... as backup... Create a Double Backup Just In case.. (JIC)

1) Click Start, click Run, type regedit and then click OK.
2) Browse to following registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
3) In the right side pane, Select "autodisconnect", Right click and select "Modify"
4) Now what ever the value is there type "fffffff" click OK


If the "autodisconnect" entry is not there then follow the below steps to create one

1) Browse to the folowing regestry location : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
2) In the right side pane, Right click and select "New" and then click DWORD (32 Bit for 64 Bit OS)
3) Type "autodisconnect", and press ENTER. (without the " ")
4) Select "autodisconnect", Right click and select "Modify"
5) Click Hexadecimal.
6) And type "ffffffff" (8 times f), and click OK. (without the " ")

Next

1) Now browse to following Registry location : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Service\lanmanworkstation\parameters
2) In the right side pane, Right click and select "New" and then click DWORD (32 Bit for 64 Bit OS)
3) Type "KeepConn" (without the " ")
4) Select "KeepConn", Right click and select "Modify"
5) Type : 1 to 65535 (time in sec) so if you wish to keep the connection for 20 min type in (1200), I used 1800 (30 Min) 60*Minutes are seconds which you would like to enter so 60*30 = 1800

Next

1) Now browse to following Registry location : HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\RPC
2) In the right side pane, Right click and select "New" and then click DWORD (32 Bit for 64 Bit OS)
3) Type "DefConnectOpts" and press ENTER. (without the " ")
4) Select "DefConnectOpts", Right click and select "Modify"
5) And type "0", and click OK.

If the RPC key is missing no issues, create it by follow the steps to create it

1) Browse to following Registry location : HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\
2) In the right side pane, Right click and select "New" and then click "Key"
3) Type in RPC and press Enter



Now Reboot the PC and check... No more Outlook Disconnections..

Location for Different office version.

office 2007 : HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\RPC
office 2010 : HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\RPC
office 2013 : HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\RPC

hummm.... HKEY_CURRENT_USER\Software\Microsoft\Office\13.0\Outlook\RPC the 13 doesnot exist... seems Microsoft too thinks its JINXED

Friday, February 28, 2014

Intel Pro 1000 LAN Drivers for Server 2003/2008/2008 R2

Today I had a wearied problem...

Was installing Server 2008 R2 on Intel 61WW... all got installed well... but was not able to install LAN drivers..

No matter from where ever I download it from... didnt installed.. I tried on different Motherboard suspecting that the NIC might have got faulty...  even tried with Intel 61CR motherboard... Nope it refused to install

Tried Windows 7 64 bit drivers... hummm... nope that to didn't work... 

Because...  Intel & ofcourse Micro$oft thought that no one should be allowed to install Server class OS on Desktop Systems... Bad business Ethics... MONOPOLY.... again happy to SAY I LOVE... AMD and LINUX...  therefore they omitted the settings from where Server OS will not be able to recognize the Hardware and will not install the drivers..... and they never realized that some people who have test labs and dont have server class machines at their disposal to do R&D and testing.... will be using desktops as servers for testing so don't be greedy and release for all...

So finally I did what I use to do when Windows 7 came and  again manufacturers & Micro$oft refused to provide XP drivers with Laptops... Tweak driver Inf files with respective Hardware ID's and create a INF file which is recognized by the OS... here is what I did and it worked...

Download Intel 1000 Pro LAN drivers and Extract it...

Go to drictory where you extracted it... PRO1000\Winx64\NDIS62\  directory

make a copy of e1c62x64.inf file to any other folder.... In case you want to revert back to original state.

Open the following INF file in Notepad... and you will see....



[Intel]

[Intel.NTamd64.6.1.1]
; DisplayName                   Section              DeviceID
; -----------                   -------              --------
%E1502NC.DeviceDesc%            = E1502.6.1.1,       PCI\VEN_8086&DEV_1502
%E1502NC.DeviceDesc%            = E1502.6.1.1,       PCI\VEN_8086&DEV_1502&SUBSYS_00011179
%E1502NC.DeviceDesc%            = E1502.6.1.1,       PCI\VEN_8086&DEV_1502&SUBSYS_00021179
%E1502NC.DeviceDesc%            = E1502.6.1.1,       PCI\VEN_8086&DEV_1502&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00011179
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00021179
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_04911025

[Intel.NTamd64.6.1]
; DisplayName                   Section        DeviceID
; -----------                   -------        --------
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00011179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00021179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_80001025


Change it to.....

[Intel.NTamd64.6.1.1]
; DisplayName                   Section              DeviceID
; -----------                   -------              --------
%E1502NC.DeviceDesc%            = E1502.6.1.1,       PCI\VEN_8086&DEV_1502
%E1502NC.DeviceDesc%            = E1502.6.1.1,       PCI\VEN_8086&DEV_1502&SUBSYS_00011179
%E1502NC.DeviceDesc%            = E1502.6.1.1,       PCI\VEN_8086&DEV_1502&SUBSYS_00021179
%E1502NC.DeviceDesc%            = E1502.6.1.1,       PCI\VEN_8086&DEV_1502&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00011179
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00021179
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_04911025

[Intel.NTamd64.6.1]
; DisplayName                   Section        DeviceID
; -----------                   -------        --------
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00011179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00021179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00011179
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00021179
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_04911025



What we just did is that... Under section [Intel.NTamd64.6.1] we added the Hardware ID of the NIC which Server 2008 R2 can compare to Installed NIC ID... and accordingly Install the drivers..



%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00011179
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00021179
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.1.1,       PCI\VEN_8086&DEV_1503&SUBSYS_04911025


No clich Update driver in Device manager and browse to the Extracted location where we have just updated the INF file and... See the magic... the drivers wil install... and you will have working Desktop and Server 2008 R2 .....

The same can be done dor Server 2003 and Server 2008..

For Server 2003

\NDIS5x\e1c51x64.inf


[Intel]

[Intel.NTamd64.5.2]
; DisplayName                   Section        DeviceID
; -----------                   -------        --------
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00011179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00021179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503&SUBSYS_00011179
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503&SUBSYS_00021179
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503&SUBSYS_04911025

[Intel.NTamd64.5.2.1]
; DisplayName                   Section        DeviceID
; -----------                   -------        --------
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00011179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00021179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503&SUBSYS_00011179
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503&SUBSYS_00021179
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503,       PCI\VEN_8086&DEV_1503&SUBSYS_04911025


For Server 2008

\NDIS61\e1c60x64.inf

[Intel]

[Intel.NTamd64.6.0.1]
; DisplayName                   Section              DeviceID
; -----------                   -------              --------
%E1502NC.DeviceDesc%            = E1502.6.0.1,       PCI\VEN_8086&DEV_1502
%E1502NC.DeviceDesc%            = E1502.6.0.1,       PCI\VEN_8086&DEV_1502&SUBSYS_00011179
%E1502NC.DeviceDesc%            = E1502.6.0.1,       PCI\VEN_8086&DEV_1502&SUBSYS_00021179
%E1502NC.DeviceDesc%            = E1502.6.0.1,       PCI\VEN_8086&DEV_1502&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00011179
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00021179
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503&SUBSYS_04911025

[Intel.NTamd64.6.0]
; DisplayName                   Section        DeviceID
; -----------                   -------        --------
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00011179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_00021179
%E1502NC.DeviceDesc%            = E1502,       PCI\VEN_8086&DEV_1502&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00011179
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503&SUBSYS_00021179
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503&SUBSYS_80001025
%E1503NC.DeviceDesc%            = E1503.6.0.1,       PCI\VEN_8086&DEV_1503&SUBSYS_04911025


Hope that These GIANTS one day learn to behave and value the needs of all not just their own.....




Tuesday, February 18, 2014

MySQL error mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

I recently upgraded MySQL 5.1 to 5.5.36 on CENTOS 6.5 64 bit

upgrade went well but MySQL won't start...

only one line logged under /var/log/mysqlerror.log

mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

hummm.... so PID error

tried many things... Google search for PID issues...but...

boy.... no matter what I tried...... I was not able to make mysql service start... then...


I ran command  mysql_safe ....

Voila... it gave me another log entry...

InnoDB: Error: log file ./ib_logfile0 is of different size 0 20356374 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!




the error was because the size of innoDB logfile mention didnt match the size of logfile on the server...


so the solution was...

moving the current ib_logfiles to another location

cd ..

mkdir innodblog

mv /var/lib/mysql/ib_logfile* /var/lib/innodblog

service mysqld start

and finally it started...


Thanks

Lenovo Laptop Brightness Issue

Today I faced a very peculiar issue, we had a display driver update for our Lenovo Laptops Z500 and suddenly the brightness went to 0 no mat...