title: I am not behind a proxy but still getting error while installing packages using npm
body: <h2>here is the output from npm-debug.log</h2>
  
  <ol>
  <li>info it worked if it ends with ok</li>
  <li>verbose cli [ 'D:\Softwares and Codes\NodeJS\NodeJS\\node.exe',</li>
  <li>verbose cli   'D:\Softwares and Codes\NodeJS\NodeJS\node_modules\npm\bin\npm-cli.js',</li>
  <li>verbose cli   'install',</li>
  <li>verbose cli   'gulp',</li>
  <li>verbose cli   '--save' ]</li>
  <li>info using npm@2.11.3</li>
  <li>info using node@v0.12.7</li>
  <li>verbose install initial load of C:\Users\Mayur\Desktop\Node\package.json</li>
  <li>warn package.json sampleapp@1.0.0 No repository field.</li>
  <li>warn package.json sampleapp@1.0.0 No README data</li>
  <li>verbose readDependencies loading dependencies from C:\Users\Mayur\Desktop\Node\package.json</li>
  <li>silly cache add args [ 'gulp', null ]</li>
  <li>verbose cache add spec gulp</li>
  <li>silly cache add parsed spec { raw: 'gulp',</li>
  <li>silly cache add   scope: null,</li>
  <li>silly cache add   name: 'gulp',</li>
  <li>silly cache add   rawSpec: '',</li>
  <li>silly cache add   spec: '*',</li>
  <li>silly cache add   type: 'range' }</li>
  <li>silly addNamed gulp@*</li>
  <li>verbose addNamed "*" is a valid semver range for gulp</li>
  <li>silly addNameRange { name: 'gulp', range: '*', hasData: false }</li>
  <li>silly mapToRegistry name gulp</li>
  <li>silly mapToRegistry using default registry</li>
  <li>silly mapToRegistry registry <a href="http://registry.npmjs.org/" rel="nofollow">http://registry.npmjs.org/</a></li>
  <li>silly mapToRegistry uri <a href="http://registry.npmjs.org/gulp" rel="nofollow">http://registry.npmjs.org/gulp</a></li>
  <li>verbose addNameRange registry:<a href="http://registry.npmjs.org/gulp" rel="nofollow">http://registry.npmjs.org/gulp</a> not in flight; fetching</li>
  <li>verbose request uri <a href="http://registry.npmjs.org/gulp" rel="nofollow">http://registry.npmjs.org/gulp</a></li>
  <li>verbose request no auth needed</li>
  <li>info attempt registry request try #1 at 8:00:49 PM</li>
  <li>verbose request id 8da3a5a06ccf7a86</li>
  <li>http request GET <a href="http://registry.npmjs.org/gulp" rel="nofollow">http://registry.npmjs.org/gulp</a></li>
  <li>info retry will retry, error on last attempt: Error: connect ETIMEDOUT</li>
  <li>info attempt registry request try #2 at 8:01:20 PM</li>
  <li>http request GET <a href="http://registry.npmjs.org/gulp" rel="nofollow">http://registry.npmjs.org/gulp</a></li>
  <li>info retry will retry, error on last attempt: Error: connect ETIMEDOUT</li>
  <li>info attempt registry request try #3 at 8:02:41 PM</li>
  <li>http request GET <a href="http://registry.npmjs.org/gulp" rel="nofollow">http://registry.npmjs.org/gulp</a></li>
  <li>verbose stack Error: connect ETIMEDOUT</li>
  <li>verbose stack     at exports._errnoException (util.js:746:11)</li>
  <li>verbose stack     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1010:19)</li>
  <li>verbose cwd C:\Users\Mayur\Desktop\Node</li>
  <li>error Windows_NT 6.1.7601</li>
  <li>error argv "D:\Softwares and Codes\NodeJS\NodeJS\\node.exe" "D:\Softwares and Codes\NodeJS\NodeJS\node_modules\npm\bin\npm-cli.js" "install" "gulp" "--save"</li>
  <li>error node v0.12.7</li>
  <li>error npm  v2.11.3</li>
  <li>error code ETIMEDOUT</li>
  <li>error errno ETIMEDOUT</li>
  <li>error syscall connect</li>
  <li>error network connect ETIMEDOUT</li>
  <li>error network This is most likely not a problem with npm itself</li>
  <li>error network and is related to network connectivity.</li>
  <li>error network In most cases you are behind a proxy or have bad network settings.</li>
  <li>error network</li>
  <li>error network If you are behind a proxy, please make sure that the</li>
  <li>error network 'proxy' config is set properly.  See: 'npm help config'</li>
  <li>verbose exit [ 1, true ]</li>
  </ol>
  
  <h2>I have already tried</h2>
  
  <ol>
  <li>set registry to <a href="http://registry.npmjs.org/" rel="nofollow">http://registry.npmjs.org/</a></li>
  <li>set strict ssl to false</li>
  </ol>